Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.FIPv6 ReadinessActionIPv6 records exist but unreachableFIX
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.
Learn more ▾ ▴
Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.
Source: RFC 8305 (Happy Eyeballs)
BTLS Certificate Expiry & Recommendations75 days until leaf cert expires — 5 issues to addressREVIEW
Certificate validity
Recommended actions
- Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
- Add includeSubDomains to the HSTS directive
- 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 Records2 A records, 22 ms lookupPASS
| A | 172.67.178.154, 104.21.17.220 |
| AAAA | 2606:4700:3035::ac43:b29a, 2606:4700:3035::6815:11dc |
| CNAME | — |
| NS | mia.ns.cloudflare.com, randy.ns.cloudflare.com |
| MX | 0 computerhistory-org.mail.protection.outlook.com |
| TXT | 1JPhzj9k7fEHgtsngDZNS6yfV03c0x5VyuvqC4odAJkWfpEFvI9mD72+vQiSbKOtDMvUyMNqklKmOw+O... MS=498D467512A4DA933158597F4042806719B8E25B MS=ms12064115 _globalsign-domain-verification=a0QaafMZgRS0DbVMw3XLx2rdUg41VfP9I_fBBuSk-m _globalsign-domain-verification=w4J1QxPn3aNctgVGzY51pbeSFxpzwNCjLN4HV-i699 apple-domain-verification=zj49fL4xByFmwuNN docusign=5c1c9cad-846f-41c0-9049-a0cbe3169cfb facebook-domain-verification=og8r6zl8mxkeszsryklveiywpkyzuq gJPngtlEoee5tmwh7SsQYLjyX5sIac7gbdszvgbHPluMG1oiUo8PIlF0NqxwNAHCjePqMKlQQgd2pg++... google-site-verification=p5tnnWmagFi2txnFJKyqJhSWZaKddUMCc6sKK-zCX5M lgpoa4pn3skmfbm0f4amo8fruc mPvdaxG4vvybwa8VZI0J4AncjCIh3T75uHBGRwH3TSD1kU8XFwFx0yDDAbsgB7n+UZ3fAELT6dI16V6e... nfM5CrwvDFasS6IfAOTkTvjNzm7gYjif2NEd49JW97+JBXBTD0dGmQDeyu/RnpXC76UvmzlMQm8KbMAN... openai-domain-verification=dv-LxzDCWHjzW2cxVrmyRlJZ4So rm_verify=b4106fa28e SPF v=spf1 include:spf.protection.outlook.com include:_spf.psm.knowbe4.com include:s... |
| 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.
A+Redirect ChainNo redirects — direct accessPASS
https://computerhistory.org
44 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://computerhistory.org | 200 | 44 ms | HTTP/1.1 | cloudflare |
A+Crawlabilityrobots.txt present, sitemap with 14 URLsPASS
# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:
Sitemap: https://computerhistory.org/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK
- https://computerhistory.org/post-sitemap...
- https://computerhistory.org/page-sitemap...
- https://computerhistory.org/events-sitem...
- https://computerhistory.org/publications...
- https://computerhistory.org/press_releas...
- https://computerhistory.org/profiles-sit...
- https://computerhistory.org/profiles-sit...
- https://computerhistory.org/jobs-sitemap...
- https://computerhistory.org/playlists-si...
- https://computerhistory.org/stories-site...
- https://computerhistory.org/exhibits-sit...
- https://computerhistory.org/category-sit...
- https://computerhistory.org/event-type-s...
- https://computerhistory.org/event-catego...
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencecomputerhistory.org — via Cloudflare, Inc., 28 years, 7 months old, hosted on CloudflarePASS
231 days
February 2, 2027
75 days
Issued by Google Trust Services
28 years, 7 months
Registered February 3, 1998
Not enabled
Protects against DNS spoofing
Cloudflare
ASN AS13335
104.21.17.220
Cloudflare, Inc.
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