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 & Recommendations45 days until leaf cert expires — 5 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
- Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
- Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
- 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 Records1 A records, 151 ms lookupPASS
| A | 207.54.136.33 |
| AAAA | — |
| CNAME | — |
| NS | ns4-05.azure-dns.info, ns3-05.azure-dns.org, ns1-05.azure-dns.com, ns2-05.azure-dns.net |
| MX | 10 mxb-0057c701.gslb.pphosted.com 10 mxa-0057c701.gslb.pphosted.com |
| TXT | 738c29777f756e911f3084c61ca41c4ae54875d827cfec34e65c368d96c7592e google-site-verification=Ra0nvdMvVeNLeiwakV23odew0-Kp5EeMHDRnkz_JZQk CHyRcqMa3BCrAq68EGvDrdSPLx4D8Qa6hlNHJjkAC5wV40QeKtY0jDsbqw6KZsO2uZ/gUwuRUU47i6on... docusign=2144f067-4ef1-41c0-8c8e-ccee63ee0ec9 prodpad-domain-verification=yuanjsQZ5hdnnhOOc65RAzMpxIQhrsmD8ubDmiylJ54= gitkraken-domain-verification=62e9b29144889d2813dc2627e18d247482c58e99c764cc1a19... atlassian-domain-verification=Br4EabUYyGqVOFO5dQFoeMbXNsHOTrqFRtG7hsZ9Zsh7UI8xZW... jhfew22bf489a9xbh6v912n334n768y Foxit-domain-verification=62d230480cbb5d40fb5977591b8008d3 anthropic-domain-verification-br4ndb=iCCas75qhjxr9xc7ID308QY2p MS=ms12292089 bw=GBwFQPzpXWjS1Kup5xfAxq7Jquub0AgEKyCNQm4kqokM SXomk/k/cbZE/0AK4BTng/79b4Z9r01JwIWNwNY4C9EUKCQolmqthXVuQEbj4ibYKdZnjmWXau1Bdj+D... docker-verification=394db3d0-23d6-447b-b196-7250149a3051 formstack-domain-verification=71063a625accb3d0f1a0ada266468a54 facebook-domain-verification=ywzlhjiwei4pz4qt6gryr1jfudusjk jamf-site-verification=FwiblA7KURdGLLb16Y3fHw google-site-verification=WUUO4M8lCeyPRDYvKXnxRcsSgy93Rv8n72CwDHmC_kc amazon-business-verification=f52a237c46c86c28184951123ab88f2522dd611be27406237bd... canva-site-verification=dQhk03PhyvIE_RUfjl8qZQ airtable-verification=cede8f48f6d3d3d31e08c91a74ed4c39 SPF v=spf1 ip4:207.54.136.3 ip4:207.54.136.2 ip4:207.54.136.4 include:_spf.salesforc... |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.
Learn more ▾ ▴
Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.
Source: SRE practice / DNS architecture
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), 724 ms totalPASS
https://overdrive.com
432 ms · HTTP/1.1
https://www.overdrive.com/
292 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://overdrive.com | 302 | 432 ms | HTTP/1.1 | |
| 2 | https://www.overdrive.com/ | 403 | 292 ms | HTTP/1.1 | CFS 1124 |
See the visual redirect chain in the HTTP Probe tab →
If permanent, use 301 instead.
302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.
Learn more ▾ ▴
Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).
Source: Google Search Central
AURL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
HTTP → HTTPS
Use 301 (permanent) instead of 302 (temporary)
A+Domain Intelligenceoverdrive.com — via eNom, LLC, 30 years, 7 months old, hosted on EXPEDIENT - Expedient, USPASS
218 days
February 19, 2027
45 days
Issued by Google Trust Services
30 years, 7 months
Registered February 18, 1996
Not enabled
Protects against DNS spoofing
EXPEDIENT - Expedient, US
ASN AS17054
207.54.136.33
eNom, 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