Mail domain report: ipage.com

SPF

pass

SPF record published

Found

Record: v=spf1 ip4:38.113.1.0/24 ip4:38.113.20.0/24 ip4:12.45.243.128/26 ip4:65.254.224.0/19 ip4:66.96.128.0/18 include:spf.extole.io include:eig.spf.a.cloudfilter.net include:spf.protection.outlook.com include:registrarmail.net include:_spf.hostedemail.com include:spf.websitewelcome.com -all
DNS lookups: 9 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

No ptr mechanism found in SPF record.
✓ 9 of 10 DNS lookups #2

SPF record needs 9 DNS lookups (limit is 10).
✓ Ends with -all #3

SPF record properly uses -all to restrict unauthorized senders.
✓ Record published #6

SPF record exists for this domain.
✓ Single record #16

Exactly one SPF record is published.
✓ Valid syntax #25

All SPF mechanisms and modifiers are valid.
✓ No void lookups #26

All include/redirect targets exist.
✓ No overly broad IP ranges #27

All ip4/ip6 ranges are narrow enough.

DMARC

fail

p=none (_dmarc.ipage.com)

Found

Record: v=DMARC1; p=none; pct=100; rua=mailto:re+odxq6tvin92@dmarc.postmarkapp.com; sp=none; adkim=r; aspf=r; fo=1;
Found at: _dmarc.ipage.com
External report address: mailto:re+odxq6tvin92@dmarc.postmarkapp.com (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	none	Policy
sp	none	Subdomain policy
pct	100	Percentage of mail the policy applies to
rua	mailto:re+odxq6tvin92@dmarc.postmarkapp.com	Aggregate report addresses
adkim	r	DKIM alignment (r = relaxed, s = strict)
aspf	r	SPF alignment (r = relaxed, s = strict)
fo	1	Failure reporting options

Checks

✗

Policy: none (monitoring only)

DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.

#4
✓ Record published #5

DMARC record exists for this domain.
✓ Valid syntax #17

DMARC record syntax is valid.
✓ Aggregate reports enabled #19

Aggregate reports are sent to: mailto:re+odxq6tvin92@dmarc.postmarkapp.com
✓ External report addresses authorized #29

Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: dkim, google

Found

Selectors: dkim, google
_domainkey: NOERROR

Selector	Key	Flags
dkim	RSA 2048 bits	test mode (t=y)
google	RSA 2048 bits

Checks

✓ Keys found: dkim, google #7

DKIM keys found for this domain with selectors: dkim, google
✓ Strong keys #23

DKIM keys are strong enough: dkim: RSA 2048 bits; google: RSA 2048 bits.
!

Key in test mode

These keys have t=y, so receivers treat DKIM failures as a test: dkim. Remove t=y once DKIM works.

#24

DNSSEC

warn

Not signed

Found

DNSKEY records: No (0)
DS at parent: No

Checks

!

Not enabled

DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.

#8

MX

warn

1 mail server

Found

Priority	Host	Records	Reverse DNS
0	ipage-com.mail.protection.outlook.com	A 52.101.8.65 A 52.101.41.125 A 52.101.9.4 A 52.101.41.206 AAAA 2a01:111:f403:f909::6 AAAA 2a01:111:f403:c95d::4 AAAA 2a01:111:f403:c946::1 AAAA 2a01:111:f403:f804::7	mail-dm6pr04cu00201.inbound.protection.outlook.com ✓ mail-byapr05cu00605.inbound.protection.outlook.com ✓ mail-mn2pr05cu00304.inbound.protection.outlook.com ✓ mail-byapr05cu00806.inbound.protection.outlook.com ✓ mail-bn3pr04cu00106.inbound.protection.outlook.com ✓ mail-ph6pr04cu00104.inbound.protection.outlook.com ✓ mail-ch1pr04cu00101.inbound.protection.outlook.com ✓ mail-co2pr03cu00307.inbound.protection.outlook.com ✓

Checks

✓ 1 MX record #9

Found 1 MX records for this domain.
✓ All hosts resolve #10

All MX records resolve to valid IP addresses.
✓ All hosts have IPv6 #11

All MX records resolve to IPv6 addresses.
!

Single MX host, no backup

Only one MX record found. For better email reliability, consider adding at least one backup MX server.

#12
✓ At most 5 MX records #13

Found 1 MX records, which is within the recommended range (1-5).
✓ No localhost targets #14

No MX records pointing to localhost found.
✓ No private IP addresses #15

No MX records resolving to private IP addresses found.
✓ No CNAME targets #22

No MX records point to a CNAME.
✓ Reverse DNS confirmed #30

All 8 MX addresss have a PTR record that resolves back to them.

TLS

warn

no MTA-STS · no TLS-RPT · DANE on 0 of 1 MX hosts

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
ipage-com.mail.protection.outlook.com	none	-

Checks

!

Not configured

MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.

#32
i

Not configured

TLS-RPT lets senders report TLS delivery problems to you. It is most useful together with MTA-STS or DANE.

#35
i

Not used

No MX host publishes TLSA records. DANE lets senders verify your mail server's certificate through DNSSEC; it requires DNSSEC on the MX host's zone.

#36

BIMI

info

No BIMI record

Checks

i

Not configured

BIMI shows your logo next to your mail in supporting mail clients. It requires DMARC enforcement.

#38