Mail domain report: vultr.com

SPF

fail

SPF record published

Found

Record: v=spf1 ip4:108.61.13.174 ip4:107.191.35.128/29 ip4:208.167.225.32/28 ip4:208.167.225.253 ip4:66.42.112.23 ip4:108.61.150.28 ip4:64.237.34.251 ip4:192.254.117.0/24 include:_spf2.vultr.com include:_spf3.vultr.com include:_spf.google.com include:_spf4.vultr.com include:mg-spf.greenhouse.io include:usb._netblocks.mimecast.com -all
DNS lookups: 11 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

No ptr mechanism found in SPF record.
✗

11 DNS lookups, over the limit of 10

SPF record needs 11 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record.

#2
✓ 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.vultr.com)

Found

Record: v=DMARC1; p=reject; rua=mailto:noreply@vultr.com; ruf=mailto:noreply@vultr.com; pct=100; sp=reject; fo=1; ri=3600;
Found at: _dmarc.vultr.com

Tag	Value	Meaning
v	DMARC1	Version
p	reject	Policy
sp	reject	Subdomain policy
pct	100	Percentage of mail the policy applies to
rua	mailto:noreply@vultr.com	Aggregate report addresses
ruf	mailto:noreply@vultr.com	Failure report addresses
fo	1	Failure reporting options
ri	3600	Report interval (seconds)

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:noreply@vultr.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

pass

Selectors: google, s1, s2

Found

Selectors: google, s1, s2
_domainkey: NOERROR

Selector	Key	Flags
google	RSA 2048 bits
s1	RSA 2048 bits
s2	RSA 2048 bits

Checks

✓ Keys found: google, s1, s2 #7

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

DKIM keys are strong enough: google: RSA 2048 bits; s1: RSA 2048 bits; s2: RSA 2048 bits.
✓ 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

7 mail servers

Found

Priority	Host	Records	Reverse DNS
5	alt1.aspmx.l.google.com	A 142.250.147.27 AAAA 2a00:1450:4025:c01::1b	rd-in-f27.1e100.net ✓ rd-in-f27.1e100.net ✓
5	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 ✓
5	alt3.aspmx.l.google.com	A 192.179.20.27 AAAA 2404:6800:4000:1027::1a	ncboms-in-f27.1e100.net ✓ ncboms-in-f26.1e100.net ✓
5	alt4.aspmx.l.google.com	A 192.178.158.27 AAAA 2404:6800:4013:813::1b	lcdels-in-f27.1e100.net ✓ lcdels-in-f27.1e100.net ✓
5	aspmx.l.google.com	A 142.251.127.26 AAAA 2a00:1450:4001:c21::1a	lcfrai-in-f26.1e100.net ✓ lcfrai-in-f26.1e100.net ✓
15	usb-smtp-inbound-1.mimecast.com	A 170.10.152.242 A 170.10.150.242	usb-smtp-delivery-2.mimecast.com ✓ usb-smtp-delivery-2.mimecast.com ✓
15	usb-smtp-inbound-2.mimecast.com	A 170.10.150.242 A 170.10.152.242	usb-smtp-delivery-2.mimecast.com ✓ usb-smtp-delivery-2.mimecast.com ✓

Checks

✓ 7 MX records #9

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

#11
✓ Redundant MX hosts #12

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

More than 5 MX records

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

TLS

fail

MTA-STS record without policy · no TLS-RPT · DANE on 0 of 7 MX hosts

Found

MTA-STS record: v=STSv1; id=20240911T1200
Policy URL: https://mta-sts.vultr.com/.well-known/mta-sts.txt
Policy error: https://mta-sts.vultr.com/.well-known/mta-sts.txt returned HTTP 403

DANE (TLSA records)

MX host	TLSA	DNSSEC
alt1.aspmx.l.google.com	none	-
alt2.aspmx.l.google.com	none	-
alt3.aspmx.l.google.com	none	-
alt4.aspmx.l.google.com	none	-
aspmx.l.google.com	none	-
usb-smtp-inbound-1.mimecast.com	none	-
usb-smtp-inbound-2.mimecast.com	none	-

Checks

✓ Record published #32

MTA-STS record found with id 20240911T1200.
✗

Policy not reachable

The MTA-STS record exists but the policy could not be fetched, so senders ignore MTA-STS: https://mta-sts.vultr.com/.well-known/mta-sts.txt returned HTTP 403.

#33
!

Not configured

MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".

#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