heroku.comDNS health report
Testing every nameserver. This takes a few seconds.
Testing every nameserver. This takes a few seconds.
Failures and warnings, most serious first, each with what to do.
Some DKIM keys are 1024-bit RSA. They still verify, but are considered weak.
How to fix: Create a 2048-bit key at the mail provider that uses the selector and publish it in place of the old one.
The .com zone lists 8 nameservers for heroku.com.
8 nameservers are listed. At least two are required.
Every nameserver that needs a glue record has one.
Every nameserver name resolves to an address.
All 16 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 1661184191.
The primary nameserver dns1.p04.nsone.net 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.
Some DKIM keys are 1024-bit RSA. They still verify, but are considered weak.
How to fix: Create a 2048-bit key at the mail provider that uses the selector and publish it in place of the old one.
The domain has one SPF record.
Checking this record takes 9 of the 10 DNS lookups a receiver allows, includes within includes counted.
www.heroku.com resolves.
www.heroku.com is an alias (CNAME).
heroku.com resolves.
The website has an AAAA record and is reachable over IPv6.
Report generated in 289 ms.
Every nameserver has an IPv6 address.
No DS record at the parent zone. The domain is not signed with DNSSEC.
No nameserver reveals its software version.
Nameservers are spread over 3 IPv4 networks.
Retry is 600 s (10 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 450 s (7 minutes), within the usual range.
There is a single MX record. That is fine if the host is itself redundant; senders retry for several days anyway.
Mail from servers the record does not list fails SPF (~all).
The domain has a DMARC record.
Mail that fails both SPF and DKIM is rejected (p=reject).
Receivers send aggregate reports to the address in the rua tag.