ultradns.netDNS 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 mail servers have no A or AAAA record, so mail cannot be delivered to them.
How to fix: Add A/AAAA records for these host names or remove the MX records.
The domain has no DMARC record. Receivers decide on their own what to do with mail that fails SPF and DKIM, and you get no reports about who sends in your name. Large mail providers require DMARC from bulk senders.
How to fix: Add a TXT record at _dmarc.ultradns.net. Start by only collecting reports: v=DMARC1; p=none; rua=mailto:you@ultradns.net
www.ultradns.net 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.
The .net zone lists 8 nameservers for ultradns.net.
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 2019110430.
The primary nameserver udns1.ultradns.net is not in the NS list. That is fine for a hidden primary.
Refresh is 900 s (15 minutes), outside the usual range of 20 minutes to 12 hours. This matters only if your secondary nameservers copy the zone with zone transfers.
Some mail servers have no A or AAAA record, so mail cannot be delivered to them.
How to fix: Add A/AAAA records for these host names or remove the MX records.
The domain has 2 MX records.
All nameservers return the same MX records.
No MX record points to a CNAME.
The domain has no DMARC record. Receivers decide on their own what to do with mail that fails SPF and DKIM, and you get no reports about who sends in your name. Large mail providers require DMARC from bulk senders.
How to fix: Add a TXT record at _dmarc.ultradns.net. Start by only collecting reports: v=DMARC1; p=none; rua=mailto:you@ultradns.net
The domain has one SPF record.
Checking this record takes 2 of the 10 DNS lookups a receiver allows, includes within includes counted.
www.ultradns.net 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.
ultradns.net resolves.
The website has no AAAA record, so it is reachable over IPv4 only.
Report generated in 504 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 8 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 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.
No mail server has an IPv6 address.
Mail from servers the record does not list fails SPF (-all).
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.