Skip to content
https://openssl.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Amsterdam, Netherlands
200 OK
Checks
9
5 PASS 4 REVIEW
C
Crawlability
Action
robots.txt present, sitemap with 5 URLs
REVIEW
robots.txt present, sitemap with 5 URLs
Info::
robots.txt is present
Got: 26 bytes
Critical::
robots.txt blocks all crawlers
Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 5 entries
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.

Why this matters

Disallow: / in robots.txt blocks every search crawler — the site becomes invisible in organic search.

Learn more ▾

Common deployment mistake: a staging robots.txt with `User-agent: * / Disallow: /` ships to prod. The site falls out of search results within days. Verify your robots.txt is the production-intended version. If this is intentional (private site), no action needed.

Source: Google Search Central

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 26 B Sitemaps referenced 0 User-agents * Blocking Yes — all crawlers blocked
User-agent: *
Disallow: /
sitemap.xml 200 OK
Type URL Set URLs 5 entries Valid XML Yes
Sample URLs:
B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.openssl.org/
200https://openssl.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://openssl.org/ → https://openssl.org:443/

Consistent

B
TLS Certificate Expiry & Recommendations
47 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

47
days left
0d 30d 60d 90d+

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN & Delivery
Google Cloud CDN
REVIEW
Google Cloud CDN
Info::
Site is served via Google Cloud CDN CDN
Got: via: 1.1 google
CDN Detected: Google Cloud CDN
Provider Google Cloud CDN Evidence via: 1.1 google
A+
DNS Records
1 A records, 22 ms lookup
PASS
1 A records, 22 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 34.49.79.89
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2600:1901:0:d50b::
Info::
4 nameserver(s) configured
Got: ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com
Info::
5 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 22 ms
Got: 22 ms
A34.49.79.89
AAAA2600:1901:0:d50b::
CNAME—
NSns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 alt3.aspmx.l.google.com
10 alt4.aspmx.l.google.com
TXT
MS=ms30329591
bw=8FWhDisk9A5pIZaRqgEVlw9bmNX2JfRXqrMEIQ7H3LDq
openai-domain-verification=dv-yMgwPMed7LsPUgnVC7wKD1yQ
anthropic-domain-verification-aak9cc=zhKPG1Uo7ZmC2C0SRXdTupz4B
google-site-verification=UcenFo8BSxiqYnF3VG-WR2sRg5sA6_rqD95uHRd1XCQ
google-site-verification=Vfn-VvIAKa3dsUvBlPcoj9Fs9n4vjWvTNRblV_fqJJY
google-site-verification=gSC0oSoa_ORUbibpFTgJOzjCiSO1RbQvSLAFNf_Rlyc
SPF v=spf1 include:_spf.google.com include:spf.ourmailsender.com include:mail.zendes...
CAALookup not available with standard resolver
Resolved in 22 ms

Multiple A records provide failover if one server goes down.

Why this matters

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.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://openssl.org

https://openssl.org

150 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://openssl.org200150 msHTTP/1.1UploadServer
A+
IPv6 Readiness
IPv6 reachable (2 ms)
PASS
IPv6 reachable (2 ms)
Info::
IPv6 is configured and reachable at 2600:1901:0:d50b::
Got: 2 ms connect
IPv6 Ready
AAAA Records 2600:1901:0:d50b:: Connection Reachable (2 ms)
A+
Domain Intelligence
openssl.org — via Gandi SAS, 27 years, 8 months old
PASS
openssl.org — via Gandi SAS, 27 years, 8 months old
Info::
Domain registered until Dec 19, 2032 (6 years, 9 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: Gandi SAS
Warning::
Registrar lock is NOT enabled
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.
Domain expiry

2352 days

December 19, 2032

SSL certificate

47 days

Issued by Google Trust Services

Domain age

27 years, 8 months

Registered December 19, 1998

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2600:1901:0:d50b::

Registrar

Gandi SAS

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Gandi SAS
Created December 19, 1998 (27 years, 8 months ago)
Expires December 19, 2032 (6 years, 9 months)
Last Updated October 17, 2025
Name Servers ns-cloud-b1.googledomains.com, ns-cloud-b4.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com
DNSSEC Enabled
Hosting
IP Address 2600:1901:0:d50b::
Data source: rdap (0.6s)

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.

Why this matters

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

A+
HTTP Probe Timing
Total 143 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
18 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
2 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
12 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
143 ms
Total Time Total request time from DNS lookup through full response.
143 ms

Connection waterfall

DNS Lookup 18 ms TCP Connect 2 ms TLS Handshake 12 ms Server Processing 112 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback