gov-online.go.jp

Readiness by lane

Green: gov-online.go.jp. Thin bar: Government Services peer median.

Priority fixes for gov-online.go.jp

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

1. Priority 1 · Harden

   DMARC policy enforces quarantine or reject

   Observed: No DMARC record was found at _dmarc.gov-online.go.jp.

   Why it matters: An enforcing DMARC policy helps receiving mail systems reject email that falsely claims to come from your domain, a common route for phishing your customers.

   What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.

   52% of Government Services peers do this. Limit: Read from public DNS at the time of the check; records may have changed since.

   Guide: A Practical Website Health Check for Owners

2. Priority 2 · Accelerate

   Static files cached for 30 days or more

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

   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.

   30% of Government Services peers do this.

   Guide: Browser Caching Guide for Website Owners

3. Priority 3 · 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.

   41% of Government Services peers do this.

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

4. Priority 4 · Harden

   CAA records limit who can issue certificates

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

   17% of Government Services peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What gov-online.go.jp already does well

Practices fewer than half of Government Services peers use.

• Modern image formats in useWebP or AVIF images detected.15% of peers
• Reachable over IPv6IPv6 address published.27% of peers
• Social preview image setog:image present.36% of peers

What we saw

Homepage checked

https://www.gov-online.go.jp/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 198-day validity, expiring 2027-04-24

CDN or edge

Amazon CloudFront

DNS operators

Amazon Route 53

HSTS

max-age 365 days, includeSubDomains, preload

Homepage HTML

455 KB, br

Images on homepage

149 (webp 95, svg 49, png 5)

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

Compare with other Government Services sites

• bundestag.de73
• migrationsverket.se73
• mom.gov.sg73
• pensionsmyndigheten.se74
• sec.gov74

Government Services readiness benchmark