k1._domainkey.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 domain has no SPF record. Even a domain that sends no mail should have one, so that nobody else can send in its name.
How to fix: If the domain sends no mail, add this TXT record at k1._domainkey.intacct.com: v=spf1 -all
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.
www.k1._domainkey.intacct.com does not resolve to any address. Visitors who type the www form will get an error.
How to fix: Add an A/AAAA record or a CNAME for www.
k1._domainkey.intacct.com is part of the intacct.com zone. Nameserver and SOA checks apply to that zone.
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 no MX records, so it does not receive e-mail (or mail falls back to the A record).
How to fix: If the domain should receive e-mail, add MX records. If not, publish a null MX record (0 .).
The domain has no SPF record. Even a domain that sends no mail should have one, so that nobody else can send in its name.
How to fix: If the domain sends no mail, add this TXT record at k1._domainkey.intacct.com: v=spf1 -all
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.
The domain has no DMARC record of its own and is covered by the record of intacct.com.
www.k1._domainkey.intacct.com does not resolve to any address. Visitors who type the www form will get an error.
How to fix: Add an A/AAAA record or a CNAME for www.
k1._domainkey.intacct.com itself has no A or AAAA record. Visitors who type the domain without www will get an error.
How to fix: Add an A/AAAA record for the bare domain, or an ALIAS/ANAME record if your DNS host offers one.
Report generated in 956 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.
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.