amazon.comDNS health report
Testing every nameserver. This takes a few seconds.
Testing every nameserver. This takes a few seconds.
The .com zone lists 4 nameservers for amazon.com.
4 nameservers are listed. At least two are required.
Every nameserver that needs a glue record has one.
Every nameserver name resolves to an address.
Every nameserver has an IPv6 address.
No DS record at the parent zone. The domain is not signed with DNSSEC.
All 8 nameserver addresses answered over UDP.
All reachable nameservers answered over TCP.
Every reachable nameserver answers authoritatively for the zone.
The NS records at the parent and in the zone match.
No nameserver offers recursion to the public.
The zone's SOA record.
All nameservers have serial 201.
The primary nameserver dns-external-route53.us-east-1.amazonaws.com is not in the NS list. That is fine for a hidden primary.
Refresh is 3600 s (1 hour), within the usual range.
The domain has 1 MX record.
All nameservers return the same MX records.
Every mail server resolves to an address.
No MX record points to a CNAME.
Every mail server address has a reverse DNS record.
The domain has one SPF record.
Checking this record takes 4 of the 10 DNS lookups a receiver allows, includes within includes counted.
Mail from servers the record does not list fails SPF (-all).
The domain has a DMARC record.
www.amazon.com resolves.
www.amazon.com is an alias (CNAME).
amazon.com resolves.
Report generated in 1029 ms.
No nameserver reveals its software version.
Nameservers are spread over 4 IPv4 networks.
Retry is 900 s (15 minutes), within the usual range.
Expire is 604800 s (7 days), outside the usual range of 2 to 4 weeks. This matters only if your secondary nameservers copy the zone with zone transfers.
Minimum (negative cache TTL) is 60 s (1 minute), outside the usual range of 5 minutes to 1 day. This matters only if your secondary nameservers copy the zone with zone transfers.
There is a single MX record. That is fine if the host is itself redundant; senders retry for several days anyway.
No mail server has an IPv6 address.
Mail that fails both SPF and DKIM goes to spam (p=quarantine).
Receivers send aggregate reports to the address in the rua tag.
No DKIM key was found under 38 common selectors. That does not prove there is none: DNS cannot list the selectors of a domain.
How to fix: Find the selector in the DKIM-Signature header of a message you sent (the s= value) and check it on the DKIM page of this domain.
The website has an AAAA record and is reachable over IPv6.