Mail domain report: shazam.com

SPF

pass

SPF record published

Found

Record: v=spf1 mx include:_spf.apple.com include:_spf.firebasemail.com include:_spf-txn.apple.com ~all
DNS lookups: 7 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

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

warn

p=quarantine (_dmarc.shazam.com)

Found

Record: v=DMARC1; p=quarantine; rua=mailto:d@rua.agari.com; ruf=mailto:d@ruf.agari.com;
Found at: _dmarc.shazam.com
External report address: mailto:d@rua.agari.com (authorized)
External report address: mailto:d@ruf.agari.com (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
rua	mailto:d@rua.agari.com	Aggregate report addresses
ruf	mailto:d@ruf.agari.com	Failure report addresses

Checks

!

Policy: quarantine

DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.

#4
✓ 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:d@rua.agari.com
✓ Subdomain policy: quarantine #20

Subdomains are covered by policy 'quarantine'.
✓ External report addresses authorized #29

Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: k1, google

Found

Selectors: k1, google
_domainkey: NXDOMAIN

Selector	Key	Flags
k1	RSA 1024 bits
google	RSA 1024 bits

Checks

✓ Keys found: k1, google #7

DKIM keys found for this domain with selectors: k1, google
!

1024-bit DKIM key

1024-bit RSA keys are the minimum and are considered weak today: k1 (1024 bits), google (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

5 mail servers

Found

Priority	Host	Records	Reverse DNS
10	mx-in.g.apple.com	A 17.57.165.2	mx-in-hfd.apple.com ✓
20	mx-in-hfd.apple.com	A 17.57.165.2	mx-in-hfd.apple.com ✓
20	mx-in-mdn.apple.com	(does not resolve)
20	mx-in-rno.apple.com	(does not resolve)
20	mx-in-vib.apple.com	A 17.57.170.2	mx-in-vib.apple.com ✓

Checks

✓ 5 MX records #9

Found 5 MX records for this domain.
!

Hosts without IP addresses

The following MX hosts could not be resolved to IP addresses: mx-in-mdn.apple.com, mx-in-rno.apple.com

#10
!

Hosts without IPv6

The following MX hosts could not be resolved to IPv6 addresses: mx-in.g.apple.com, mx-in-hfd.apple.com, mx-in-mdn.apple.com, mx-in-rno.apple.com, mx-in-vib.apple.com

#11
✓ Redundant MX hosts #12

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

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

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
mx-in.g.apple.com	none	-
mx-in-hfd.apple.com	none	-
mx-in-mdn.apple.com	none	-
mx-in-rno.apple.com	none	-
mx-in-vib.apple.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