STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

justice.gov

justice.gov's public homepage, certificate and DNS checked against 31 practices and compared with 954 Government Services sites.

Readiness index
81/100

Government Services median 53

Ahead of
96%

of measured Government Services sites

Practices observed
24/31

0 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 12:12:09 UTC from one location. How we measure

Readiness by lane

Green: justice.gov. Thin bar: Government Services peer median.

Enable

92/100

Peers 59

Harden

83/100

Peers 59

Accelerate

70/100

Peers 41

Recover

0/100

Peers 25

Priority fixes for justice.gov

Ordered by impact and by how common each practice is among peers.

  1. Priority 1 · Accelerate

    Static files cached for 30 days or more

    Observed: A same-site stylesheet or script was cacheable for 14 days, short of the 30-day benchmark.

    Why it matters: Returning visitors and later page views reuse cached files instead of downloading them again.

    What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.

    On Cloudflare: Use Cache Rules to set edge and browser TTLs for static file paths.

    30% of Government Services peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

  2. Priority 2 · Accelerate

    Modern image formats in use

    Observed: The homepage had 48 images and none used WebP or AVIF.

    What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.

    On Cloudflare: Cloudflare Polish can convert images to WebP.

    15% of Government Services peers do this.

  3. Priority 3 · Harden

    CAA records limit who can issue certificates

    Observed: No CAA record was found for justice.gov, 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.

    On Cloudflare: Cloudflare documents which CAs its managed certificates need; include them in your CAA records.

    17% of Government Services peers do this.

  4. Priority 4 · Harden

    Certificate lifetime of 100 days or less

    Observed: The certificate from DigiCert Inc had a 198-day validity period, longer than the 100-day maximum that applies from March 2027.

    What to do: Move to automated issuance and renewal now, while you still have time to test it.

    34% of Government Services peers do this.

What justice.gov already does well

Practices fewer than half of Government Services peers use.

  • HTTP/3 advertisedHTTP/3 advertised.11% of peers
  • DNSSEC signedDNSSEC delegation (DS record) present.19% of peers
  • Reachable over IPv6IPv6 address published.27% of peers

What we saw

Homepage checked
https://www.justice.gov/
Homepage response
HTTP 200
TLS
TLSv1.3, HTTP/2
Certificate
DigiCert, 198-day validity, expiring 2026-11-08
CDN or edge
Akamai, Acquia
Platform or framework
Drupal
DNS operators
Cloudflare
HSTS
max-age 365 days, includeSubDomains, preload
DMARC policy
p=reject
Homepage HTML
100 KB, gzip
Images on homepage
48 (svg 24, png 11, jpg 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

Observed 24

  • HTTP requests move to HTTPS
  • HSTS kept for at least a year
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • DNSSEC signed
  • DMARC policy enforces quarantine or reject
  • X-Content-Type-Options: nosniff
  • Framing restricted
  • Content Security Policy present
  • Referrer-Policy set
  • HTTP/2 negotiated
  • HTTP/3 advertised
  • HTML compressed
  • Offscreen images lazy-loaded
  • No render-blocking scripts in <head>
  • robots.txt published
  • XML sitemap discoverable
  • Reachable over IPv6
  • Canonical URL declared
  • Meta description written
  • Mobile viewport configured
  • Social preview image set
  • Page language declared
  • At most one redirect to the homepage

Own justice.gov?

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: justice.gov. This profile covers configuration only.

Compare with other Government Services sites