Skip to content
https://openjdk.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
89
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
4 PASS 4 REVIEW 1 FIX
F
HTTP Probe Timing
Action
Total 9290 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
FIX
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
27 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
4 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
9.29 s
Total Time Total request time from DNS lookup through full response.
9.29 s

Connection waterfall

DNS Lookup 27 ms TCP Connect 1 ms TLS Handshake 4 ms Server Processing 9.26 s Content Transfer 0 ms
B
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

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.

Why this matters

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

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 0 Expected: 301 redirect to HTTPS

www / non-www

https://www.openjdk.org/
200https://openjdk.org/

HTTP → HTTPS

http://openjdk.org/

HTTP version does not redirect to HTTPS

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

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • 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
B
CDN & Delivery
Akamai
REVIEW
Akamai
Info::
Site is served via Akamai CDN
Got: x-akamai-transformed: 0 - 0 -
CDN Detected: Akamai
Provider Akamai Evidence x-akamai-transformed: 0 - 0 -
A+
DNS Records
1 A records, 29 ms lookup
PASS
1 A records, 29 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 23.37.171.85
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a02:26f0:e0:59c::2c21, 2a02:26f0:e0:596::2c21
Info::
6 nameserver(s) configured
Got: a22-64.akam.net, a6-66.akam.net, a3-66.akam.net, a10-65.akam.net, a1-93.akam.net, a13-64.akam.net
Info::
2 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: 29 ms
Got: 29 ms
A23.37.171.85
AAAA2a02:26f0:e0:59c::2c21, 2a02:26f0:e0:596::2c21
CNAME—
NSa22-64.akam.net, a6-66.akam.net, a3-66.akam.net, a10-65.akam.net, a1-93.akam.net, a13-64.akam.net
MX
10 mxb-00069f01.gslb.pphosted.com
10 mxa-00069f01.gslb.pphosted.com
TXT
SPF v=spf1 include:spf-00069f02.pphosted.com ~all
CAALookup not available with standard resolver
Resolved in 29 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 redirect data available
PASS
No redirect data available
Info::
No redirect data captured
A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2a02:26f0:e0:59c::2c21, 2a02:26f0:e0:596::2c21
Got: 1 ms connect
IPv6 Ready
AAAA Records 2a02:26f0:e0:59c::2c21, 2a02:26f0:e0:596::2c21 Connection Reachable (1 ms)
A
Domain Intelligence
openjdk.org — via MarkMonitor Inc., 20 years old
PASS
openjdk.org — via MarkMonitor Inc., 20 years old
Warning::
Domain expires in 87 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jul 18, 2026
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: MarkMonitor Inc.
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

33 days

July 18, 2026

SSL certificate

165 days

Issued by DigiCert Inc

Domain age

20 years

Registered July 18, 2006

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a02:26f0:e0:596::2c21

Registrar

MarkMonitor Inc.

Unlocked 6 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
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
Registrar MarkMonitor Inc.
Created July 18, 2006 (20 years ago)
Expires July 18, 2026 (2 months)
Last Updated June 22, 2025
Name Servers a1-93.akam.net, a10-65.akam.net, a13-64.akam.net, a22-64.akam.net, a3-66.akam.net, a6-66.akam.net
DNSSEC Not enabled
Hosting
IP Address 2a02:26f0:e0:596::2c21
Data source: rdap (0.3s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

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.

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback