Nameserver redundancy
How many nameservers answer for the domain. Two or more, in different places, keep the site resolvable when one of them fails.
Nameservers are the authoritative DNS servers for your domain: every visitor's resolver asks them where the website and the mail servers are. If all of them are unreachable, the domain disappears — the site, the mail and every API on it — as soon as cached answers expire, even though the web server itself is fine.
How SiteScan checks
The scan reads the NS records of the registrable domain. Two or more nameservers are green; a single one is a warning, because it is a single point of failure for everything on the domain. This is the one real fault in the infrastructure half of this group. The Domain registration group may show the nameservers as listed by the registry, which should match.
How to improve it
- Use at least two nameservers, ideally on different networks. Managed DNS providers give you several by default, usually anycast and spread across continents.
- If you run your own, put the secondary on a different provider or data centre, and make sure zone transfers keep it in sync.
- Check that the NS records in the zone match the delegation at the registrar; stale entries pointing at an old provider cause intermittent failures.
- For extra resilience, some teams use two independent DNS providers serving the same zone.
Related: DNSSEC and domain registrar.
See this check on your own site
Run a free scan: the report shows this row for your domain along with the other checks of the site audit.
More in “DNS & email”
What SiteScan checks
TLS certificate
- TLS certificate expiry
- Outdated TLS versions (TLS 1.0/1.1)
- TLS certificate chain
- TLS certificate issuer
- Certificate signature algorithm
Domain registration
- Domain registration expiry
- Registered domain name
- Domain registrar
- Domain registration date
- Domain last updated date
- Domain status codes (EPP)
- Domain transfer lock
- Registrar abuse contact
- RDAP and WHOIS data source
Indexing
- robots.txt file
- CSS and JS blocked in robots.txt
- XML sitemap
- Sitemap index file
- Off-domain URLs in the sitemap
- Sitemap lastmod dates
- Broken URLs in the sitemap
- RSS and Atom feed
Addresses & redirects
Security headers
- HTTP security headers and grade
- Strict-Transport-Security (HSTS) header
- Content-Security-Policy (CSP) header
- X-Content-Type-Options: nosniff
- X-Frame-Options and clickjacking
- Referrer-Policy header
- Permissions-Policy header
- HSTS preload list
- CORS and cross-origin reads
- HTTP TRACE method
Delivery & reputation
- Cache-Control header for HTML
- ETag and Last-Modified revalidation
- HTTP/3 and QUIC support
- Server version disclosure in headers
- DNS blocklist (DNSBL) check
Internal links
Exposure
- Exposed sensitive files (.env, .git, backups)
- Directory listing enabled
- Public JavaScript source maps
- Exposed WordPress endpoints
Well-known files
- security.txt file
- llms.txt for AI assistants
- llms-full.txt file
- ads.txt authorized sellers file
- humans.txt file
- Well-known change-password URL
DNS & email
- MX records (mail servers)
- SPF record
- DMARC record and policy
- DNSSEC signing
- CAA record
- Nameserver redundancy
- IPv6 support (AAAA record)
- MTA-STS policy
- TLS-RPT reporting record
- BIMI record (brand logo in email)
- Wildcard DNS record
- Dangling CNAME and subdomain takeover
Privacy & consent
- Analytics and tracking scripts
- Cookie consent banner
- Privacy policy link
- Terms of service link
- Imprint (Impressum)
- Accessibility statement
Core Web Vitals
- Lighthouse performance score
- Largest Contentful Paint (LCP)
- Cumulative Layout Shift (CLS)
- Interaction to Next Paint (INP)
- CrUX field data vs lab data