Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DRedirect ChainAction2 redirect(s), 1277 ms totalFIX
https://opendns.com
470 ms · HTTP/1.1
http://www.opendns.com/
329 ms · HTTP/1.1
https://www.opendns.com:443/
478 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://opendns.com | 301 | 470 ms | HTTP/1.1 | nginx |
| 2 | http://www.opendns.com/ | 301 | 329 ms | HTTP/1.1 | nginx |
| 3 | https://www.opendns.com:443/ | 200 | 478 ms | HTTP/1.1 | nginx |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
Redirect directly from https://opendns.com to https://www.opendns.com:443/
Redirect chain could be flattened to one hop — server config tweak removes intermediate latency.
Source: web.dev
FHTTP Probe TimingActionTotal 7947 ms — DNS, TCP, TLS, TTFB, content transfer breakdownFIX
Connection waterfall
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
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations85 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, 11 ms lookupPASS
| A | 146.112.62.105 |
| AAAA | — |
| CNAME | — |
| NS | auth1.opendns.com, auth2.opendns.com, auth3.opendns.com |
| MX | 10 alln-mx-01.cisco.com 20 rcdn-mx-01.cisco.com 30 aer-mx-01.cisco.com |
| TXT | 8a0qMBOOpB-h4tuZsbRSOi00ZA docusign=2dcbb085-bb7f-44b2-8cdd-c9a93a8c0514 google-site-verification=1uqoSSYwOE4E7Vue1oAcKDmEt6yn5US6vuQ6shGu2dg google-site-verification=VXNIemKQVGZ9Q3215ANNzcTDK5ZejVDwd6RQsQ2u1GI identrust_validate=5sxUJXEBNGIryr9TcBm31oSDJsqEiIkNIodAE18dD/xn SPF v=spf1 ptr include:_nets.opendns.com include:mail.zendesk.com include:amazonses.... _qhmqsb0grgjeq03vl0tvsnhchg7seuf |
| 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.
ACrawlabilityno robots.txt, sitemap with 18 URLsPASS
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
No robots.txt found
This is fine for most sites — a missing robots.txt allows all crawling by default.
A+Domain Intelligenceopendns.com — via PDR Ltd. d/b/a PublicDomainRegistry.com, 22 years, 11 months old, hosted on CISCO-UMBRELLA - Cisco OpenDNS, LLC, USPASS
81 days
September 4, 2026
85 days
Issued by Let's Encrypt
22 years, 11 months
Registered September 4, 2003
Not enabled
Protects against DNS spoofing
CISCO-UMBRELLA - Cisco OpenDNS, LLC, US
ASN AS36692
146.112.62.105
PDR Ltd. d/b/a PublicDomainRegistry.com
Expiry timeline
Recommended actions
- Renew the domain or enable auto-renewal to prevent accidental expiry
- 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