Skip to content
https://lbl.gov

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
73
GRADE
C
FIX
3
REVIEW
2
PASS
4
INFO
0
Probed from New York, United Stated
301 Moved Permanently
Checks
9
4 PASS 2 REVIEW 3 FIX
D
Redirect Chain
Action
2 redirect(s), 1565 ms total
FIX
2 redirect(s), 1565 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
HTTP to HTTPS redirect present
Info::
WWW normalization redirect
Warning::
2-hop chain could be reduced to 1 hop
Redirect directly from https://lbl.gov to https://www.lbl.gov/
Warning::
Redirect overhead: 1565 ms total
Got: 1565 ms

https://lbl.gov

1267 ms · HTTP/1.0

301

http://www.lbl.gov/

83 ms · HTTP/1.1

301

https://www.lbl.gov/

214 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://lbl.gov3011267 msHTTP/1.0BigIP
2http://www.lbl.gov/30183 msHTTP/1.1cloudflare
3https://www.lbl.gov/200214 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

Redirect directly from https://lbl.gov to https://www.lbl.gov/

Why this matters

Redirect chain could be flattened to one hop — server config tweak removes intermediate latency.

Source: web.dev

D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
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
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 301 Expected: 301 redirect to HTTPS

www / non-www

200https://www.lbl.gov/
200https://lbl.gov/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://lbl.gov/ http://www.lbl.gov/

HTTP version does not redirect to HTTPS

D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

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

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A
DNS Records
1 A records, 417 ms lookup
PASS
1 A records, 417 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 131.243.228.58
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: adns.lbl.gov, adns1.es.net, adns2.es.net
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
Warning::
DNS resolution is slow (417 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 417 ms
A131.243.228.58
AAAA
CNAME
NSadns.lbl.gov, adns1.es.net, adns2.es.net
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 alt4.aspmx.l.google.com
10 alt3.aspmx.l.google.com
TXT
qa1mnrllgnbfii00rdk66vjvm2
c3c383f2-a153-4617-9717-54e564cb59e0
ca3-7d1dfaea22424670b66fd99306419327
docusign=0f6bb425-7a31-4e68-82be-fbd457f31774
docusign=1eee3cad-4748-4aaf-9ed7-b2605c9483cc
canva-site-verification=mgUHPJc6r0NE6Q4prE9zpQ
openai-domain-verification=dv-sfvJakqc0pd21hOhaJqnqUTd
anthropic-domain-verification-h102fx=00CIodRx8WUfix92z4OI6tLwt
logmein-verification-code=b89f15f9-74de-42e6-beba-fc61fb213ff5
google-site-verification=2dpiQJ9xZceLN1pILOitQbB163hcYnJhaK7I3y8BJ-8
google-site-verification=GhY8O8foCyslsuOSh5VOpyIt6kp9gaZF_6X2WbtVQVI
google-site-verification=vRtEcyl-bcyq9LlAx-IKqgI_Uw5H4I_Fn0bIxGQwWek
pardot1008322=a85fde4e241411eab5a95741a5485759066251b9421d2aa2a4fbf634872dbed4
box-domain-verification=c15c129b49edfeda4f2998f51ab86512161af5251e765e73f8c312e8...
atlassian-domain-verification=9IP0nkgLSi6HnSykGR9L6B4/iYnroZIv6KiAGQZfcNV5YAZOLa...
atlassian-domain-verification=PZUpopCxEiaiTq0EmOJiF1oCvepxHULA64xstX0NEVv2Yx7HgF...
SPF v=spf1 include:spfint.lbl.gov ip6:2001:400:310::/64 ip4:198.124.252.166 ip4:198....
CAALookup not available with standard resolver
Resolved in 417 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.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
Crawlability
robots.txt present, sitemap with 1 URLs
PASS
robots.txt present, sitemap with 1 URLs
Info::
robots.txt is present
Got: 59 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1 entries
Info::
Sitemap index with 1 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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 59 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /wp-admin/
Disallow: /wp-login.php

sitemap.xml 200 OK
Type Sitemap Index URLs 1 entries Valid XML Yes
A+
Domain Intelligence
lbl.gov — via get.gov, 28 years, 11 months old, hosted on LBL - Lawrence Berkeley National Laboratory, US
PASS
lbl.gov — via get.gov, 28 years, 11 months old, hosted on LBL - Lawrence Berkeley National Laboratory, US
Info::
Domain registered until Aug 28, 2026 (4 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: get.gov
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.
Info::
Hosting: LBL - Lawrence Berkeley National Laboratory, US
Got: AS16
Domain expiry

74 days

August 28, 2026

SSL certificate

270 days

Issued by Internet2

Domain age

28 years, 11 months

Registered October 2, 1997

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

LBL - Lawrence Berkeley National Laboratory, US

ASN AS16

131.243.228.58

Registrar

get.gov

Unlocked 3 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 registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar get.gov
Created October 2, 1997 (28 years, 11 months ago)
Expires August 28, 2026 (4 months)
Last Updated March 20, 2026
Name Servers adns.lbl.gov, adns1.es.net, adns2.es.net
DNSSEC Enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 131.243.228.58
ASN AS16 (LBL - Lawrence Berkeley National Laboratory, US)
Provider LBL - Lawrence Berkeley National Laboratory, US
Data source: rdap (0.3s)

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 401 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
70 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
67 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
177 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
401 ms
Total Time Total request time from DNS lookup through full response.
401 ms

Connection waterfall

DNS Lookup 70 ms TCP Connect 67 ms TLS Handshake 177 ms Server Processing 86 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