Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BTLS Certificate Expiry & Recommendations34 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- 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, 35 ms lookupPASS
| A | 172.66.171.169, 104.20.30.15 |
| AAAA | 2606:4700:10::ac42:aba9, 2606:4700:10::6814:1e0f |
| CNAME | — |
| NS | arturo.ns.cloudflare.com, alice.ns.cloudflare.com |
| MX | 1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 aspmx2.googlemail.com 10 aspmx3.googlemail.com |
| TXT | SPF v=spf1 mx include:_spf.google.com ?all google-site-verification=S3lc6L8R99COYAE0Fj2tezgoIzorofySj_e7d76fJ2g google-site-verification=CZ-kPUQasutHoXWOhY4Fl8BTdviuHDXoGkjQl8RRZVg google-site-verification=G9VUfylR4fB8lf_0vt4fXjXBtUiAEpiaGvYNshxkW-s google-site-verification=RKlvCAeipVgUFwSUrhNl0EvsEj2oq-LAYVvwCB69lIM google-gws-recovery-domain-verification=45475660 SPF v=spf1 include:bounces.opensource.org ~all |
| 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://opensource.org
79 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://opensource.org | 200 | 79 ms | HTTP/1.1 | cloudflare |
A+IPv6 ReadinessIPv6 reachable (17 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 3 URLsPASS
Sitemap: https://opensource.org/sitemap.xml
Sitemap: https://opensource.org/news-sitemap.xml
# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:
Sitemap: https://opensource.org/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligenceopensource.org — via Gandi SAS, 28 years, 7 months oldPASS
239 days
February 10, 2027
34 days
Issued by Google Trust Services
28 years, 7 months
Registered February 11, 1998
Not enabled
Protects against DNS spoofing
Unknown
2606:4700:10::6814:1e0f
Gandi SAS
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