_dmarc.outlook.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 nameservers reveal their software version, which helps attackers pick exploits.
How to fix: Hide the version string (in BIND: version "none"; in the options block).
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 _dmarc.outlook.com: v=spf1 -all
www._dmarc.outlook.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.
_dmarc.outlook.com is part of the outlook.com zone. Nameserver and SOA checks apply to that zone.
The .com zone lists 4 nameservers for outlook.com.
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.
Some nameservers reveal their software version, which helps attackers pick exploits.
How to fix: Hide the version string (in BIND: version "none"; in the options block).
All 8 nameserver addresses answered over UDP.
All reachable nameservers answered over TCP.
Every reachable nameserver answers authoritatively for the zone.
The zone's SOA record.
All nameservers have serial 2017971531.
The primary nameserver ns1-05.azure-dns.com is one of the listed nameservers.
Refresh is 300 s (5 minutes), outside the usual range of 20 minutes to 12 hours. This matters only if your secondary nameservers copy the zone with zone transfers.
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 _dmarc.outlook.com: v=spf1 -all
The domain has no DMARC record of its own and is covered by the record of outlook.com.
Mail that fails both SPF and DKIM goes to spam (sp=quarantine).
Receivers send aggregate reports to the address in the rua tag.
www._dmarc.outlook.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.
_dmarc.outlook.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 132 ms.
Every nameserver has an IPv6 address.
The parent zone publishes a DS record, so DNSSEC is enabled for this domain.
The NS records at the parent and in the zone match.
No nameserver offers recursion to the public.
Nameservers are spread over 4 IPv4 networks.
Retry is 120 s (2 minutes), within the usual range.
Expire is 2419200 s (28 days), within the usual range.
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 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.