Infrastructure - https://cpsc.gov BeaverCheck Audit

F

DNSSEC

Action

DS at parent but zone has no DNSKEY

FIX

DS at parent but zone has no DNSKEY

Parent zone has DS record but the zone publishes no DNSKEY

The registry advertises this domain as signed (DS record present) but the zone returns no DNSKEY records. Validating resolvers will SERVFAIL. Either republish the DNSKEY records or remove the DS record at the registrar.

D

URL Variants

Action

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

FIX

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 version does not redirect to HTTPS

Got: HTTP 301 Expected: 301 redirect to HTTPS

www / non-www

200https://www.cpsc.gov/

200https://cpsc.gov/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://cpsc.gov/ → http://www.cpsc.gov/

HTTP version does not redirect to HTTPS

B

CAA Records

No CAA records (any CA may issue certificates)

REVIEW

No CAA records (any CA may issue certificates)

No CAA records published

Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.

B

Reverse DNS

0/3 IPs match cert SAN

REVIEW

0/3 IPs match cert SAN

PTR for 23.220.155.193 does not match any cert SAN: a23-220-155-193.deploy.static.akamaitechnologies.com

Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.

PTR for 2a02:26f0:e0:886::983 does not match any cert SAN: g2a02-26f0-00e0-0886-0000-0000-0000-0983.deploy.static.akamaitechnologies.com

Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.

PTR for 2a02:26f0:e0:887::983 does not match any cert SAN: g2a02-26f0-00e0-0887-0000-0000-0000-0983.deploy.static.akamaitechnologies.com

Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.

B

TLS Certificate Expiry & Recommendations

85 days until leaf cert expires — 1 issues to address

REVIEW

Certificate validity

85

days left

0d 30d 60d 90d+

Recommended actions

Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains

B

CDN & Delivery

Document on Akamai; assets also on Cloudflare

REVIEW

Document on Akamai; assets also on Cloudflare

Document is served via Akamai CDN

Got: server: AkamaiGHost

Assets on Akamai: www.cpsc.gov (assets: 16)

Got: delegation www.cpsc.gov.edgekey.net

Assets on Cloudflare: cdn.jsdelivr.net (assets: 6), cache HIT

Got: delegation cdn.jsdelivr.net.cdn.cloudflare.net

Document served via CDN: Akamai

Provider Akamai Evidence server: AkamaiGHost

Asset hosts on a CDN

www.cpsc.gov — Akamai · assets: 16
cdn.jsdelivr.net — Cloudflare · assets: 6 · Cache Status: HIT

Other asset hosts

www.googletagmanager.com — assets: 6 · Google
content.govdelivery.com — assets: 2 · below probe threshold
dap.digitalgov.gov — assets: 2 · below probe threshold
fonts.googleapis.com — assets: 2 · below probe threshold
static.addtoany.com — assets: 2 · below probe threshold

B

CDN Cache Observability

No CDN cache-status headers in the response

REVIEW

No CDN cache-status headers in the response

Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.

B

Operational Status Page

No status page link detected

REVIEW

No status page link detected

No operational status page link detected

Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.

B

Health Check Endpoint

No conventional health endpoint found

REVIEW

No conventional health endpoint found

Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.

A+

DNS Records

1 A records, 41 ms lookup

PASS

1 A records, 41 ms lookup

Resolves to 1 IPv4 address(es)

Got: 23.220.155.193

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:e0:886::983, 2a02:26f0:e0:887::983

6 nameserver(s) configured

Got: a28-66.akam.net, a4-64.akam.net, a3-67.akam.net, a1-85.akam.net, a13-64.akam.net, a20-65.akam.net

1 mail exchanger(s) configured

SPF record present in TXT

DNS resolution time: 41 ms

Got: 41 ms

A	23.220.155.193
AAAA	2a02:26f0:e0:886::983, 2a02:26f0:e0:887::983
CNAME	—
NS	a28-66.akam.net, a4-64.akam.net, a3-67.akam.net, a1-85.akam.net, a13-64.akam.net, a20-65.akam.net
MX	0 cpsc-gov.mail.protection.outlook.com
TXT	SPF v=spf1 ip4:50.224.209.125 mx include:spf.protection.outlook.com include:mailgun.... identrust_validate=t3CSpOgu2r93d3dKMnQYjCO2ljoKON4dTaaEghLHR1Uk Domain-verification=L27XF0w-vnHLxuyaBKnKvZAWZDsDu2hO_A2Fr7XuTUw Gta/s6B33mNiKI0TImkQy6p0hblAnYDnUGIwOe2+q71UwputDZEV+T6Eu5l1FSuuBi2/0LZ8jLELS3jh... QuoVadis=e2cf6d31-9ae0-4a21-8f56-49c5bfb5f45d google-site-verification=u2S-nSBP2FcFy0isf6KSsyk9O4Qeks_yfEb9d31qRpw MS=ms64095673
CAA	Lookup not available with standard resolver

Resolved in 41 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

A+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

No CNAME record present

A

Multi-Resolver DNS Speed

Mean 51ms across 3 resolvers (spread 67ms)

PASS

Mean 51ms across 3 resolvers (spread 67ms)

Google: 29ms

Got: 29ms via 8.8.8.8:53

Cloudflare: 30ms

Got: 30ms via 1.1.1.1:53

Quad9: 96ms

Got: 96ms via 9.9.9.9:53

A

Redirect Chain

1 redirect(s), 26 ms total

PASS

1 redirect(s), 26 ms total

Single redirect

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

WWW normalization redirect

https://cpsc.gov

16 ms · HTTP/1.1

301

https://www.cpsc.gov/

9 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://cpsc.gov	301	16 ms	HTTP/1.1	AkamaiGHost
2	https://www.cpsc.gov/	200	9 ms	HTTP/1.1	nginx

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:e0:886::983, 2a02:26f0:e0:887::983

Got: 1 ms connect

IPv6 Ready

AAAA Records 2a02:26f0:e0:886::983, 2a02:26f0:e0:887::983 Connection Reachable (1 ms)

A+

Crawlability

robots.txt present, sitemap with 19998 URLs

PASS

robots.txt present, sitemap with 19998 URLs

robots.txt is present

Got: 3254 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 19998 entries

robots.txt references sitemap

robots.txt 200 OK

Size 3254 B Sitemaps referenced 1 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: /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
# Url Params
Disallow: /*archivepage?*
Allow: /*archivepage?page*
Disallow: /*Archivepage?*
Allow: /*Archivepage?page*
Disallow: /*business--manufacturing/business-education/faq/search?*
Disallow: /*Business--Manufacturing/Business-Education/FAQ/Search?*
Disallow: /*newsroom/foia/reportlist?*
Allow: /*newsroom/foia/reportlist?page*
Disallow: /*Newsroom/FOIA/ReportList?*
Allow: /*Newsroom/FOIA/ReportList?page*
Disallow: /*newsroom/news-releases?*
Allow: /*newsroom/news-releases?page*
Disallow: /*Newsroom/News-Releases?*
Allow: /*Newsroom/News-Releases?page*
Disallow: /*newsroom/public-calendar?*
Allow: /*newsroom/public-calendar?page*
Disallow: /*Newsroom/Public-Calendar?*
Allow: /*Newsroom/Public-Calendar?page*
Disallow: /*product_recalls_download?*
Disallow: /*Product_Recalls_Download?*
Disallow: /*recalls?*
Allow: /*recalls?page*
Disallow: /*Recalls?*
Allow: /*Recalls?page*
Disallow: /*noticias?*
Allow: /*noticias?page*
Disallow: /*Noticias?*
Allow: /*Noticias?page*
Disallow: /*search?*
Disallow: /*Search?*
# Ajax
Disallow: /*This-Path-is-added-for-month-block-ajax-to-work*
Disallow: /*this-path-is-added-for-month-block-ajax-to-work*
# Sitemap
Sitemap: https://www.cpsc.gov/sitemap.xml

sitemap.xml 200 OK

Type URL Set URLs 19998 entries Valid XML Yes

Sample URLs:

A+

Domain Intelligence

cpsc.gov — via get.gov, 29 years, 5 months old

PASS

cpsc.gov — via get.gov, 29 years, 5 months old

Domain registered until Aug 5, 2027 (9 months remaining)

DNSSEC is enabled

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

290 days

August 5, 2027

SSL certificate

85 days

Issued by DigiCert Inc

Domain age

29 years, 5 months

Registered October 2, 1997

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2a02:26f0:e0:887::983

Registrar

get.gov

Unlocked 6 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Recommended actions

Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar get.gov

Created October 2, 1997 (29 years, 5 months ago)

Expires August 5, 2027 (9 months)

Last Updated August 14, 2026

Name Servers a1-85.akam.net, a13-64.akam.net, a20-65.akam.net, a28-66.akam.net, a3-67.akam.net, a4-64.akam.net

DNSSEC Enabled

Registrant REDACTED FOR PRIVACY

Hosting

IP Address 2a02:26f0:e0:887::983

Data source: rdap (0.5s)

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 44 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

PASS

DNS Lookup

32 ms

TCP Connect

1 ms

TLS Handshake

4 ms

Time to First Byte

43 ms

Total Time

44 ms

Connection waterfall

DNS Lookup 32 ms TCP Connect 1 ms TLS Handshake 4 ms Server Processing 7 ms Content Transfer 1 ms