stspg-customer.comDNS health report
Testing every nameserver. This takes a few seconds.
Testing every nameserver. This takes a few seconds.
The .com zone lists 4 nameservers for stspg-customer.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.
Every nameserver has an IPv6 address.
No DS record at the parent zone. The domain is not signed with DNSSEC.
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-1711.awsdns-21.co.uk is one of the listed nameservers.
Refresh is 7200 s (2 hours), within the usual range.
The domain has 7 MX records.
All nameservers return the same MX records.
Every mail server resolves to an address.
No MX record points to a CNAME.
The domain has one SPF record.
Checking this record takes 0 of the 10 DNS lookups a receiver allows, includes within includes counted.
Mail from servers the record does not list fails SPF (~all).
The domain has a DMARC record.
www.stspg-customer.com resolves.
stspg-customer.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.
The website has no AAAA record, so it is reachable over IPv4 only.
Report generated in 1229 ms.
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.
Every mail server address has a reverse DNS record.
Mail that fails both SPF and DKIM is rejected (p=reject).
Receivers send aggregate reports to the address in the rua tag.
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.