Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BCrawlabilityno robots.txt, no sitemapREVIEW
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.
Learn more ▾ ▴
A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.
Source: robotstxt.org
A sitemap helps search engines discover and index your pages more efficiently.
No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.
Learn more ▾ ▴
A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.
Source: sitemaps.org / Google Search Central
No robots.txt found
This is fine for most sites — a missing robots.txt allows all crawling by default.
No sitemap found
Adding a sitemap helps search engines discover your pages.
BTLS Certificate Expiry & Recommendations146 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
- Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
- Enable DNSSEC on your domain for DNS spoofing protection
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+DNS Records2 A records, 155 ms lookupPASS
| A | 76.223.39.37, 13.248.188.197 |
| AAAA | — |
| CNAME | — |
| NS | ns45.domaincontrol.com, ns46.domaincontrol.com |
| MX | 10 aspmx.l.google.com 20 alt1.aspmx.l.google.com 30 alt2.aspmx.l.google.com 40 aspmx2.googlemail.com 50 aspmx3.googlemail.com |
| TXT | amazonses:l/8pYMJ/Nf4H4s7MGckvZxSAyBCkZQ61yjKmRmplgzQ= _dbcj62wj67pius523k6hasmia5g5bl0 google-site-verification=c6fxl6VmysIl8gPZB9OidxyPsX9eAsO3rF4i7dvcK8c apple-domain-verification=UxC0ZR3sl1QwXHPpTf__Vc38_eQ1V_ewQ8IOh6x7Dt8 globalsign-domain-verification=A981A20B51E61D66E1D8C65892D894A3 SPF v=spf1 ip4:209.165.174.70 ip4:209.165.174.71 ip4:23.23.161.12 ip4:184.106.33.1 i... globalsign-domain-verification=52b71aa584e9f9635f844d012b637147 tollbit-domain-verification=102f3a013b4eda4a3c10ce56e86ee26d01e4cf5cd75dbf7ba632... globalsign-domain-verification=B58E4E271864A398C41C200EBB815864 globalsign-domain-verification=4698F53B9DA7ACD658EAA55939388A78 duo_sso_verification=8sBJ4kQm57jOzIPmjVCgceQLA1yL00RpfQQTvqjHZykfQgwk9qebQxTNQTZ... globalsign-domain-verification=77AEAE44B763B7FD49AE4476F3AA8E90 google-site-verification=0jCxy09HheDUj4TXsKq-JxxarIkwj2mpodpLtoMS-Ik google-site-verification=t8HqdcEvLGWUElzPd3IicNllX03CTAEijfxlsL1qDqc MS=A7B8294B6BE9F394A792E86AC0000E7484F37D55 google-site-verification=piM_nXQkESX87a6GtUCHykRDfYU4KdMi3FdEgJBdb8g globalsign-domain-verification=47F6E9CF86A67C550A3B69FF7F2F1CE9 |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
ARedirect Chain1 redirect(s), 211 ms totalPASS
https://adn.com
129 ms · HTTP/1.1
https://www.adn.com:443/
82 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://adn.com | 301 | 129 ms | HTTP/1.1 | awselb/2.0 |
| 2 | https://www.adn.com:443/ | 403 | 82 ms | HTTP/1.1 | AkamaiGHost |
See the visual redirect chain in the HTTP Probe tab →
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
HTTP → HTTPS
Consistent
A+Domain Intelligenceadn.com — via GoDaddy.com, LLC, 31 years, 10 months old, hosted on AWSPASS
1617 days
November 17, 2030
146 days
Issued by Amazon
31 years, 10 months
Registered November 18, 1994
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
76.223.39.37
GoDaddy.com, LLC
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.
Learn more ▾ ▴
DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.
Source: ICANN / RFC 4033
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.
Learn more ▾ ▴
Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.
Source: ICANN / domain-security best practice