Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BRedirect Chain1 redirect(s), 1157 ms totalREVIEW
https://llnl.gov
833 ms · HTTP/1.0
https://www.llnl.gov/
324 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://llnl.gov | 301 | 833 ms | HTTP/1.0 | |
| 2 | https://www.llnl.gov/ | 200 | 324 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations333 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
- 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
ADNS Records1 A records, 966 ms lookupPASS
| A | 198.128.246.5 |
| AAAA | — |
| CNAME | — |
| NS | ns0.llnl.gov, adns2.es.net, adns1.es.net |
| MX | 10 mxa-00379502.gslb.gpphosted.com 10 mxb-00379502.gslb.gpphosted.com |
| TXT | domain-verification=07b5ce3c287f554b41a36312c252d70534f13d3a0cc3024c64822325aeab... _10koyys895hs3ymh5u9h8ysn3u3zm4c domain-verification=b9fc4a60cdd7b3c7bac07923d9ecbf1076ff9c32b66d07b4849b5aa8c8c1... google-site-verification=4EqJgIylpANKx9-dfb0VlCOQFzaLSCkeR6vHCNPMpIc SPF v=spf1 include:_spf.llnl.gov include:spf-00379502.gpphosted.com ip4:128.15.12.4... vtv1lc683lq91m87gh4m9mv32hpty78h google-gws-recovery-domain-verification=68408356 openai-domain-verification=dv-oFzYLoRgNJxXNYbB1kIko6ON _n1w1ku8eqdr1jzh77dv9a1bf7izc8lj docusign=bc4d24a6-0d09-4d1d-820c-b95698db5af3 apple-domain-verification=ABwGni7cMh8LMpb5 cisco-ci-domain-verification=5ea053ba6e0f511026cfb190e8b6dd599aab46c59d4f781e930... anthropic-domain-verification-52whj2=0QaHMNeov9PUxx48e02idlVPM box-domain-verification=6939a02eb679e2375e18e51b26b336ca1961ea94c6a7f6ad2084d36b... nhtab0p11op3mdi1n1jt56i2he adobe-idp-site-verification=c92c5f0aa9b86e1ff942798faed32deb472e85136c8adc9e004b... google-site-verification=BXJ8WIQT33-KhzxFh_f5tvp6tr0u5j_1oBM7Zcpr32s |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
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.
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.
DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.
Source: DNS performance benchmarks
A+Crawlabilityrobots.txt present, sitemap with 2120 URLsPASS
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
#
# robots.txt
#
# This file is to prevent the crawling and indexing of certain parts
# of your site by web crawlers and spiders run by sites like Yahoo!
# and Google. By telling these "robots" where not to go on your site,
# you save bandwidth and server resources.
#
# This file will be ignored unless it is at the root of your host:
# Used: http://example.com/robots.txt
# Ignored: http://example.com/site/robots.txt
#
# For more information about the robots.txt standard, see:
# http://www.robotstxt.org/robotstxt.html
User-agent: *
# CSS, JS, Images
Allow: /core/*.css$
Allow: /core/*.css?
Allow: /core/*.js$
Allow: /core/*.js?
Allow: /core/*.gif
Allow: /core/*.jpg
Allow: /core/*.jpeg
Allow: /core/*.png
Allow: /core/*.svg
Allow: /profiles/*.css$
Allow: /profiles/*.css?
Allow: /profiles/*.js$
Allow: /profiles/*.js?
Allow: /profiles/*.gif
Allow: /profiles/*.jpg
Allow: /profiles/*.jpeg
Allow: /profiles/*.png
Allow: /profiles/*.svg
# Directories
Disallow: /core/
Disallow: /profiles/
# Files
Disallow: /README.md
Disallow: /composer/Metapackage/README.txt
Disallow: /composer/Plugin/ProjectMessage/README.md
Disallow: /composer/Plugin/Scaffold/README.md
Disallow: /composer/Plugin/VendorHardening/README.txt
Disallow: /composer/Template/README.txt
Disallow: /modules/README.txt
Disallow: /sites/README.txt
Disallow: /themes/README.txt
Disallow: /web.config
# Paths (clean URLs)
Disallow: /admin/
Disallow: /comment/reply/
Disallow: /filter/tips
Disallow: /node/add/
Disallow: /search/
Disallow: /user/register
Disallow: /user/password
Disallow: /user/login
Disallow: /user/logout
Disallow: /media/oembed
Disallow: /*/media/oembed
# Paths (no clean URLs)
Disallow: /index.php/admin/
Disallow: /index.php/comment/reply/
Disallow: /index.php/filter/tips
Disallow: /index.php/node/add/
Disallow: /index.php/search/
Disallow: /index.php/user/password
Disallow: /index.php/user/register
Disallow: /index.php/user/login
Disallow: /index.php/user/logout
Disallow: /index.php/media/oembed
Disallow: /index.php/*/media/oembed
- https://www.llnl.gov/
- https://www.llnl.gov/community-education/employee-retirement-resources/in-memoriam/mary-ann-chapeta
- https://www.llnl.gov/community-education/employee-retirement-resources/in-memoriam/thomas-tillotson
- https://www.llnl.gov/llnl-scientists-inspect-iraqi-installations
- https://www.llnl.gov/community-education/employee-retirement-resources/in-memoriam/chuzo-okuda
A+Domain Intelligencellnl.gov — via get.gov, 28 years, 11 months old, hosted on ESNET-WEST - ESnet, USPASS
37 days
August 22, 2026
333 days
Issued by GoDaddy.com, Inc.
28 years, 11 months
Registered October 2, 1997
Not enabled
Protects against DNS spoofing
ESNET-WEST - ESnet, US
ASN AS292
198.128.246.5
get.gov
Expiry timeline
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
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