Website readiness profile · Snapshot 23 October 2026
publicrecordsdata.us
publicrecordsdata.us's public homepage, certificate and DNS checked against 31 practices and compared with 492 Web Tools sites.
- Readiness index
- 84/100
- Ahead of
- 94%
- Practices observed
- 22/29
- Popularity band
- Top 50K
Web Tools median 67
of measured Web Tools sites
2 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: publicrecordsdata.us. Thin bar: Web Tools peer median.
Enable
95/100
Peers 84
Harden
72/100
Peers 55
Accelerate
100/100
Peers 69
Recover
0/100
Peers 6
Priority fixes for publicrecordsdata.us
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
Certificate lifetime of 100 days or less
Observed: The certificate from Amazon had a 394-day validity period, longer than the 100-day maximum that applies from March 2027.
Why it matters: Under CA/Browser Forum Ballot SC-081v3, the maximum lifetime of public TLS certificates fell to 200 days on 15 March 2026 and falls to 100 days on 15 March 2027 and 47 days on 15 March 2029. Sites that renew by hand will need to renew far more often.
What to do: Move to automated issuance and renewal now, while you still have time to test it.
87% of Web Tools peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.
Priority 2 · Harden
Content Security Policy present
Observed: The homepage response did not include a Content-Security-Policy header.
What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.
On Next.js: Next.js documents nonce-based CSP with middleware.
15% of Web Tools peers do this.
Guide: Payment Security and PCI DSS: What Website Owners Need to Know
Priority 3 · Harden
CAA records limit who can issue certificates
Observed: No CAA record was found for publicrecordsdata.us, so any public certificate authority may issue for it.
What to do: Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.
14% of Web Tools peers do this.
Priority 4 · Enable
Reachable over IPv6
Observed: No IPv6 (AAAA) address was published for www.publicrecordsdata.us.
What to do: Enable IPv6 at your CDN or host and publish the AAAA record it provides.
67% of Web Tools peers do this.
What publicrecordsdata.us already does well
Practices fewer than half of Web Tools peers use.
- DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.23% of peers
- HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.30% of peers
- Referrer-Policy setReferrer-Policy present.30% of peers
What we saw
- Homepage checked
- https://www.publicrecordsdata.us/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Amazon, 394-day validity, expiring 2027-03-05
- CDN or edge
- Amazon CloudFront
- Platform or framework
- Next.js
- DNS operators
- Amazon Route 53
- HSTS
- max-age 365 days, includeSubDomains, preload
- DMARC policy
- p=quarantine
- Homepage HTML
- 123 KB, br
- Images on homepage
- 1 (svg 1)
Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.
Stack and providers
Seen in the homepage response, certificate and DNS. Provider pages compare how their customers configure the same checks.
All 31 checks
Select a gap for the method and fix. How each check works
Not observed 7
Observed 22
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Referrer-Policy set
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- Static files cached for 30 days or more
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Structured data present
- Social preview image set
- Page language declared
- At most one redirect to the homepage
Not measured 2
- Modern image formats in use
- Offscreen images lazy-loaded
Own publicrecordsdata.us?
Re-run the checks after a change, or verify the site in a free workspace to save reports with history, compare against similar sites and competitors, and track a private action plan. What owners get.
Live status for this site: Status Is Down: publicrecordsdata.us. This profile covers configuration only.