intacct.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.
The NS records at the .com zone and in the zone itself differ.
How to fix: Make the nameserver list at your registrar match the NS records in the zone.
Nameservers return different NS records. A zone change may not have reached all of them.
Nameservers have different SOA serials. Some have not received the latest zone yet.
How to fix: Wait for the zone transfer, or check NOTIFY and transfer settings between primary and secondaries.
The policy is p=none: receivers send reports but still deliver mail that fails the checks, so the domain is not yet protected against forged mail.
How to fix: Read the reports until every service that sends for you passes, then move to p=quarantine and finally p=reject.
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 6 nameservers for intacct.com.
6 nameservers are listed. At least two are required.
Every nameserver that needs a glue record has one.
Every nameserver name resolves to an address.
The NS records at the .com zone and in the zone itself differ.
How to fix: Make the nameserver list at your registrar match the NS records in the zone.
Nameservers return different NS records. A zone change may not have reached all of them.
Nameservers have different SOA serials. Some have not received the latest zone yet.
How to fix: Wait for the zone transfer, or check NOTIFY and transfer settings between primary and secondaries.
The zone's SOA record.
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 policy is p=none: receivers send reports but still deliver mail that fails the checks, so the domain is not yet protected against forged mail.
How to fix: Read the reports until every service that sends for you passes, then move to p=quarantine and finally p=reject.
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.
www.intacct.com resolves.
www.intacct.com is an alias (CNAME).
intacct.com resolves.
The website has no AAAA record, so it is reachable over IPv4 only.
Report generated in 3333 ms.
Every nameserver has an IPv6 address.
No DS record at the parent zone. The domain is not signed with DNSSEC.
All 12 nameserver addresses answered over UDP.
All reachable nameservers answered over TCP.
Every reachable nameserver answers authoritatively for the zone.
No nameserver offers recursion to the public.
No nameserver reveals its software version.
Nameservers are spread over 6 IPv4 networks.
The primary nameserver ns10.digicertdns.com is one of the listed nameservers.
Refresh is 43200 s (12 hours), within the usual range.
Retry is 3600 s (1 hour), within the usual range.
Expire is 1209600 s (14 days), within the usual range.
Minimum (negative cache TTL) is 180 s (3 minutes), 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.
Checking this record takes 7 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.
Receivers send aggregate reports to the address in the rua tag.