Infrastructure - https://uscourts.gov BeaverCheck Audit

B

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

REVIEW

www/non-www, trailing slash, HTTP→HTTPS

Both www and non-www versions serve content

Got: Both variants return 200 Expected: One variant 301-redirects to the other

HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.uscourts.gov/

200https://uscourts.gov/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://uscourts.gov/ → https://uscourts.gov/

Consistent

C

TLS Certificate Expiry & Recommendations

Action

27 days until leaf cert expires — 4 issues to address

REVIEW

Certificate validity

27

days left

0d 30d 60d 90d+

Renew soon — under 30 days remaining

Recommended actions

Renew certificate — 27 days remaining
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

Site is served via Akamai CDN

Got: server header

CDN Detected: Akamai

Provider Akamai Evidence server header

A+

DNS Records

1 A records, 29 ms lookup

PASS

1 A records, 29 ms lookup

Resolves to 1 IPv4 address(es)

Got: 88.221.44.231

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

Has 2 IPv6 (AAAA) record(s)

Got: 2a02:26f0:2380:28d::3291, 2a02:26f0:2380:28b::3291

6 nameserver(s) configured

Got: a16-65.akam.net, a1-221.akam.net, a11-64.akam.net, a24-67.akam.net, a2-66.akam.net, a7-64.akam.net

2 mail exchanger(s) configured

CAA records not checked

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

SPF record present in TXT

DNS resolution time: 29 ms

Got: 29 ms

A	88.221.44.231
AAAA	2a02:26f0:2380:28d::3291, 2a02:26f0:2380:28b::3291
CNAME	—
NS	a16-65.akam.net, a1-221.akam.net, a11-64.akam.net, a24-67.akam.net, a2-66.akam.net, a7-64.akam.net
MX	20 mail1.uscourts.gov 30 mail3.uscourts.gov
TXT	SPF v=spf1 include:spfh.ao.uscourts.gov -all apple-domain-verification=BJ8iQXsXSFyn9f3f adobe-idp-site-verification=7734476fc0fc1203dfda054f872a2f4aa3c08208214df45aca0e... cisco-ci-domain-verification=3fff3dc36ffc9349f0826b7cf2d154fd79a1d4f2e06d11d19db... MS=ms96408798 _3qvsn5hqkhfr5qyvg2j2vdkgru5wb97
CAA	Lookup 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

1 redirect(s), 244 ms total

PASS

1 redirect(s), 244 ms total

Single redirect

Got: https://uscourts.gov → https://www.uscourts.gov/ (301)

WWW normalization redirect

https://uscourts.gov

18 ms · HTTP/1.1

301

https://www.uscourts.gov/

227 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://uscourts.gov	301	18 ms	HTTP/1.1	AkamaiGHost
2	https://www.uscourts.gov/	200	227 ms	HTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+

IPv6 Readiness

IPv6 reachable (1 ms)

PASS

IPv6 reachable (1 ms)

IPv6 is configured and reachable at 2a02:26f0:2380:28d::3291, 2a02:26f0:2380:28b::3291

Got: 1 ms connect

IPv6 Ready

AAAA Records 2a02:26f0:2380:28d::3291, 2a02:26f0:2380:28b::3291 Connection Reachable (1 ms)

A+

Crawlability

robots.txt present, sitemap with 21 URLs

PASS

robots.txt present, sitemap with 21 URLs

robots.txt is present

Got: 1782 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 21 entries

Sitemap index with 21 child sitemaps

robots.txt does not reference a 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 1782 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.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
Disallow: /federal-court-finder/
# 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
Disallow: /index.php/federal-court-finder/

sitemap.xml 200 OK

Type Sitemap Index URLs 21 entries Valid XML Yes

Child Sitemaps:

A+

Domain Intelligence

uscourts.gov — via get.gov, 28 years, 11 months old

PASS

uscourts.gov — via get.gov, 28 years, 11 months old

Domain registered until Sep 24, 2026 (5 months remaining)

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.

Registrar: get.gov

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

71 days

September 24, 2026

SSL certificate

27 days

Issued by DigiCert Inc

Domain age

28 years, 11 months

Registered October 2, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a02:26f0:2380:28b::3291

Registrar

get.gov

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
Renew the TLS certificate or verify auto-renewal is working
Enable DNSSEC to protect visitors from DNS spoofing
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar get.gov

Created October 2, 1997 (28 years, 11 months ago)

Expires September 24, 2026 (5 months)

Last Updated September 29, 2025

Name Servers a1-221.akam.net, a11-64.akam.net, a16-65.akam.net, a2-66.akam.net, a24-67.akam.net, a7-64.akam.net

DNSSEC Not enabled

Registrant REDACTED FOR PRIVACY

Hosting

IP Address 2a02:26f0:2380:28b::3291

Data source: rdap (0.7s)

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

A+

HTTP Probe Timing

Total 40 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

PASS

DNS Lookup

28 ms

TCP Connect

1 ms

TLS Handshake

6 ms

Time to First Byte

40 ms

Total Time

40 ms

Connection waterfall

DNS Lookup 28 ms TCP Connect 1 ms TLS Handshake 6 ms Server Processing 5 ms Content Transfer 0 ms