ns3-02.azure-dns.orgDNS 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 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.azure-dns.org. Start by only collecting reports: v=DMARC1; p=none; rua=mailto:you@azure-dns.org
The NS records at the .org zone and in the zone itself differ.
How to fix: Make the nameserver list at your registrar match the NS records in the zone.
All nameservers are in the same /24 network. One network outage takes down all of them.
How to fix: Host at least one nameserver on a different network.
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 ns3-02.azure-dns.org: v=spf1 -all
www.ns3-02.azure-dns.org 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.
ns3-02.azure-dns.org is part of the azure-dns.org zone. Nameserver and SOA checks apply to that zone.
The .org zone lists 4 nameservers for azure-dns.org.
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.
The NS records at the .org zone and in the zone itself differ.
How to fix: Make the nameserver list at your registrar match the NS records in the zone.
All nameservers are in the same /24 network. One network outage takes down all of them.
How to fix: Host at least one nameserver on a different network.
All 8 nameserver addresses answered over UDP.
The zone's SOA record.
All nameservers have serial 6.
The primary nameserver ns1-01.azure-dns.com is not in the NS list. That is fine for a hidden primary.
Refresh is 7200 s (2 hours), within the usual range.
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 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.azure-dns.org. Start by only collecting reports: v=DMARC1; p=none; rua=mailto:you@azure-dns.org
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 ns3-02.azure-dns.org: v=spf1 -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.
www.ns3-02.azure-dns.org 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.
ns3-02.azure-dns.org resolves.
The website has an AAAA record and is reachable over IPv6.
Report generated in 180 ms.
Every nameserver has an IPv6 address.
No DS record at the parent zone. The domain is not signed with DNSSEC.
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.
Retry is 900 s (15 minutes), within the usual range.
Expire is 2419200 s (28 days), within the usual range.
Minimum (negative cache TTL) is 3600 s (1 hour), within the usual range.