Mail domain report: yahooinc.com

SPF

warn

SPF record published

Found

Record: v=spf1 include:_spf.google.com include:_spf.salesforce.com include:mktomail.com include:spf.dynect.net ip4:74.217.49.0/25 ip4:69.25.227.128/25 ip4:107.20.210.250 ip4:107.23.16.222 ip4:52.1.14.157 ip4:54.173.83.138 ip4:162.13.248.246 ip4:162.13.248.247 ip4:5.148.32.142 ptr:yahoo.com ip4:148.163.135.35 ip4:148.163.139.55 ip4:74.217.49.0/25 ip4:69.25.227.128/25 -all
DNS lookups: 6 of 10
Void lookups: 0 of 2

Checks

!

Uses deprecated ptr mechanism

The ptr mechanism in SPF records is deprecated due to performance issues and should be avoided.

#1
✓ 6 of 10 DNS lookups #2

SPF record needs 6 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

pass

p=reject (_dmarc.yahooinc.com)

Found

Record: v=DMARC1; p=reject; pct=100; rua=mailto:rua@yahooinc.com; ruf=mailto:ruf@yahooinc.com;
Found at: _dmarc.yahooinc.com

Tag	Value	Meaning
v	DMARC1	Version
p	reject	Policy
pct	100	Percentage of mail the policy applies to
rua	mailto:rua@yahooinc.com	Aggregate report addresses
ruf	mailto:ruf@yahooinc.com	Failure report addresses

Checks

✓ Policy: reject #4

DMARC policy is set to 'reject', which provides the strongest protection against email spoofing.
✓ Record published #5

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

DMARC record syntax is valid.
✓ Applies to 100% of mail #18

DMARC policy applies to all failing mail.
✓ Aggregate reports enabled #19

Aggregate reports are sent to: mailto:rua@yahooinc.com
✓ Subdomain policy: reject #20

Subdomains are covered by policy 'reject'.
✓ Report addresses in own domain #29

All report addresses are in your own organizational domain.

DKIM

warn

Selectors: selector1, selector2, google, s1, s2

Found

Selectors: selector1, selector2, google, s1, s2
_domainkey: NOERROR

Selector	Key	Flags
selector1	RSA 1024 bits
selector2	RSA 2048 bits
google	RSA 2048 bits
s1	RSA 2048 bits
s2	RSA 1024 bits

Checks

✓ Keys found: selector1, selector2, google, s1, s2 #7

DKIM keys found for this domain with selectors: selector1, selector2, google, s1, s2
!

1024-bit DKIM key

1024-bit RSA keys are the minimum and are considered weak today: selector1 (1024 bits), s2 (1024 bits). Rotate to a 2048-bit key.

#23
✓ No problematic flags #24

No keys in test mode, revoked, or limited to SHA-1.

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

2 mail servers

Found

Priority	Host	Records	Reverse DNS
10	mxa-00505701.gslb.pphosted.com	A 148.163.135.35	mx0a-00505701.pphosted.com ✓
10	mxb-00505701.gslb.pphosted.com	A 148.163.135.35	mx0a-00505701.pphosted.com ✓

Checks

✓ 2 MX records #9

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

All MX records resolve to valid IP addresses.
!

Hosts without IPv6

The following MX hosts could not be resolved to IPv6 addresses: mxa-00505701.gslb.pphosted.com, mxb-00505701.gslb.pphosted.com

#11
✓ Redundant MX hosts #12

Found 2 MX records, which provides redundancy for email delivery.
✓ At most 5 MX records #13

Found 2 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 2 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
mxa-00505701.gslb.pphosted.com	none	-
mxb-00505701.gslb.pphosted.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