aeaaea67f78d16938.awsglobalaccelerator.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 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.aeaaea67f78d16938.awsglobalaccelerator.com. Start by only collecting reports: v=DMARC1; p=none; rua=mailto:you@aeaaea67f78d16938.awsglobalaccelerator.com
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 aeaaea67f78d16938.awsglobalaccelerator.com: v=spf1 -all
www.aeaaea67f78d16938.awsglobalaccelerator.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.
aeaaea67f78d16938.awsglobalaccelerator.com is part of the awsglobalaccelerator.com zone. Nameserver and SOA checks apply to that zone.
The .com zone lists 4 nameservers for awsglobalaccelerator.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.
All 8 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 1.
The primary nameserver ns-609.awsdns-12.net is one of the listed nameservers.
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.aeaaea67f78d16938.awsglobalaccelerator.com. Start by only collecting reports: v=DMARC1; p=none; rua=mailto:you@aeaaea67f78d16938.awsglobalaccelerator.com
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 aeaaea67f78d16938.awsglobalaccelerator.com: 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.aeaaea67f78d16938.awsglobalaccelerator.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.
aeaaea67f78d16938.awsglobalaccelerator.com resolves.
The website has no AAAA record, so it is reachable over IPv4 only.
Report generated in 878 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 4 IPv4 networks.
Retry is 900 s (15 minutes), within the usual range.
Expire is 1209600 s (14 days), within the usual range.
Minimum (negative cache TTL) is 86400 s (1 day), within the usual range.