ns1-124.akam.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.
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.akam.net. Start by only collecting reports: v=DMARC1; p=none; rua=mailto:you@akam.net
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 ns1-124.akam.net: v=spf1 -all
www.ns1-124.akam.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.
ns1-124.akam.net is part of the akam.net zone. Nameserver and SOA checks apply to that zone.
The .net zone lists 8 nameservers for akam.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.
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 16 nameserver addresses answered over UDP.
The zone's SOA record.
All nameservers have serial 1712081400.
The primary nameserver internal.akam.net is not in the NS list. That is fine for a hidden primary.
Refresh is 90000 s (1.0 days), 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 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.akam.net. Start by only collecting reports: v=DMARC1; p=none; rua=mailto:you@akam.net
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 ns1-124.akam.net: 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.ns1-124.akam.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.
ns1-124.akam.net resolves.
The website has an AAAA record and is reachable over IPv6.
Report generated in 298 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.
The NS records at the parent and in the zone match.
No nameserver offers recursion to the public.
Nameservers are spread over 8 IPv4 networks.
Retry is 90000 s (1.0 days), outside the usual range of 2 minutes to 2 hours. This matters only if your secondary nameservers copy the zone with zone transfers.
Expire is 90000 s (1.0 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 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.