Skip to content
https://bea.gov

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
92
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Amsterdam, Netherlands
200 OK
Checks
9
6 PASS 3 REVIEW
C
URL Variants
Action
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
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.bea.gov/
200https://bea.gov/

Inconsistent — duplicate content risk

HTTP → HTTPS

307http://bea.gov/ → https://bea.gov/

Use 301 (permanent) instead of 302 (temporary)

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

Certificate validity

306
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
Azure CDN (CONFIG_NOCACHE)
REVIEW
Azure CDN (CONFIG_NOCACHE)
Info::
Site is served via Azure CDN CDN
Got: x-azure-ref: 20260422T204629Z-r1ff48f47d7cghx9hC1PARvz300000000920000000007mnp
Info::
CDN cache status: CONFIG_NOCACHE
CDN Detected: Azure CDN
Provider Azure CDN Cache Status CONFIG_NOCACHE Evidence x-azure-ref: 20260422T204629Z-r1ff48f47d7cghx9hC1PARvz300000000920000000007mnp
A+
DNS Records
1 A records, 38 ms lookup
PASS
1 A records, 38 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 150.171.109.100
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: 2620:1ec:29:1::67, 2620:1ec:48:1::67
Info::
3 nameserver(s) configured
Got: blue.foundationdns.com, blue.foundationdns.net, blue.foundationdns.org
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: 38 ms
Got: 38 ms
A150.171.109.100
AAAA2620:1ec:29:1::67, 2620:1ec:48:1::67
CNAME—
NSblue.foundationdns.com, blue.foundationdns.net, blue.foundationdns.org
MX
10 mx1.bea.gov
20 mx2.bea.gov
TXT
Mf1jbZKEdUYEj6KxffMKn4FePdWdG0e6ImWjfxIAcpx7uS9UIhP85uIDaA8kE9O4ZNbk+GyJGzr3uQ6E...
adobe-idp-site-verification=2b3acdf4edeec1546e0aade0d83f7a87efd37d00d73cfa9b8f12...
SPF v=spf1 ip6:2610:20:3005:1::10 ip6:2610:20:3005:1::11 ip4:192.149.12.0/24 ip4:170...
CAALookup not available with standard resolver
Resolved in 38 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://bea.gov

https://bea.gov

398 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://bea.gov200398 msHTTP/1.1
A+
IPv6 Readiness
IPv6 reachable (10 ms)
PASS
IPv6 reachable (10 ms)
Info::
IPv6 is configured and reachable at 2620:1ec:29:1::67, 2620:1ec:48:1::67
Got: 10 ms connect
IPv6 Ready
AAAA Records 2620:1ec:29:1::67, 2620:1ec:48:1::67 Connection Reachable (10 ms)
A+
Crawlability
robots.txt present, sitemap with 9 URLs
PASS
robots.txt present, sitemap with 9 URLs
Info::
robots.txt is present
Got: 2027 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 9 entries
Info::
Sitemap index with 9 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 2027 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
#
# 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
sitemap.xml 200 OK
Type Sitemap Index URLs 9 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
bea.gov — via get.gov, 25 years, 8 months old
PASS
bea.gov — via get.gov, 25 years, 8 months old
Info::
Domain registered until Aug 25, 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.
Domain expiry

44 days

August 25, 2026

SSL certificate

306 days

Issued by DigiCert Inc

Domain age

25 years, 8 months

Registered December 13, 2000

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2620:1ec:29:1::67

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 December 13, 2000 (25 years, 8 months ago)
Expires August 25, 2026 (4 months)
Last Updated August 30, 2025
Name Servers blue.foundationdns.com, blue.foundationdns.net, blue.foundationdns.org
DNSSEC Enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 2620:1ec:29:1::67
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 619 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
82 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
10 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
31 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
475 ms
Total Time Total request time from DNS lookup through full response.
619 ms

Connection waterfall

DNS Lookup 82 ms TCP Connect 10 ms TLS Handshake 31 ms Server Processing 351 ms Content Transfer 145 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback