Mail domain report: zendesk.com

SPF

pass

SPF record published

Found

Record: v=spf1 ip4:103.151.192.0/23 ip4:104.43.243.237 ip4:149.97.173.180 ip4:163.116.128.0/17 ip4:170.10.128.0/24 ip4:170.10.129.0/24 ip4:170.10.132.56/29 ip4:170.10.132.64/29 ip4:170.10.133.0/24 ip4:18.194.95.56 ip4:18.198.96.88 include:_spf1.zendesk.com ~all
DNS lookups: 6 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

No ptr mechanism found in SPF record.
✓ 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

warn

p=reject (_dmarc.zendesk.com)

Found

Record: v=DMARC1; p=reject
Found at: _dmarc.zendesk.com

Tag	Value	Meaning
v	DMARC1	Version
p	reject	Policy

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.
!

No aggregate reports (rua)

DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...

#19
✓ Subdomain policy: reject #20

Subdomains are covered by policy 'reject'.

DKIM

warn

Selectors: k1, s1, s2

Found

Selectors: k1, s1, s2
_domainkey: NOERROR

Selector	Key	Flags
k1	RSA 1024 bits
s1	RSA 2048 bits
s2	RSA 1024 bits

Checks

✓ Keys found: k1, s1, s2 #7

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

1024-bit DKIM key

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

6 mail servers

Found

Priority	Host	Records	Reverse DNS
0	us-smtp-inbound-1.mimecast.com	A 170.10.132.242 A 170.10.128.141 A 170.10.128.242 A 170.10.128.221 A 170.10.132.141 A 170.10.132.221	us-smtp-inbound-2.mimecast.com ✓ us-smtp-inbound-1.mimecast.com ✓ us-smtp-inbound-2.mimecast.com ✓ us-smtp-inbound-1.mimecast.com ✓ us-smtp-inbound-1.mimecast.com ✓ us-smtp-inbound-1.mimecast.com ✓
0	us-smtp-inbound-2.mimecast.com	A 170.10.128.221 A 170.10.132.141 A 170.10.128.141 A 170.10.132.221 A 170.10.128.242 A 170.10.132.242	us-smtp-inbound-1.mimecast.com ✓ us-smtp-inbound-1.mimecast.com ✓ us-smtp-inbound-1.mimecast.com ✓ us-smtp-inbound-1.mimecast.com ✓ us-smtp-inbound-2.mimecast.com ✓ us-smtp-inbound-1.mimecast.com ✓
110	aspmx.l.google.com	A 142.251.127.26 AAAA 2a00:1450:4001:c21::1b	lcfrai-in-f26.1e100.net ✓ lcfrai-in-f27.1e100.net ✓
120	alt1.aspmx.l.google.com	A 142.250.147.26 AAAA 2a00:1450:4025:c01::1a	rd-in-f26.1e100.net ✓ rd-in-f26.1e100.net ✓
120	alt2.aspmx.l.google.com	A 172.253.152.27 AAAA 2a00:1450:4010:c22::1a	yulpptr-in-f27.1e100.net ✓ yulpptr-in-f26.1e100.net ✓
130	aspmx2.googlemail.com	A 142.250.147.27 AAAA 2a00:1450:4025:c01::1b	rd-in-f27.1e100.net ✓ rd-in-f27.1e100.net ✓

Checks

✓ 6 MX records #9

Found 6 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: us-smtp-inbound-1.mimecast.com, us-smtp-inbound-2.mimecast.com

#11
✓ Redundant MX hosts #12

Found 6 MX records, which provides redundancy for email delivery.
!

More than 5 MX records

Found 6 MX records, which is more than the recommended maximum of 5. Too many MX records may indicate a misconfiguration.

#13
✓ 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 20 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
us-smtp-inbound-1.mimecast.com	none	-
us-smtp-inbound-2.mimecast.com	none	-
aspmx.l.google.com	none	-
alt1.aspmx.l.google.com	none	-
alt2.aspmx.l.google.com	none	-
aspmx2.googlemail.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