pref.kanagawa.jp

Readiness by lane

Green: pref.kanagawa.jp. Thin bar: Government Services peer median.

Priority fixes for pref.kanagawa.jp

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

1. Priority 1 · Harden

   HTTP requests move to HTTPS

   Observed: A request to http://www.pref.kanagawa.jp/ was not redirected to HTTPS.

   Why it matters: Visitors who type the address or follow an old link start on unencrypted HTTP. A redirect moves them to the encrypted site before any cookies or form data are sent.

   What to do: Add a permanent (301 or 308) redirect from every http:// URL to the same https:// URL at your CDN, load balancer or web server.

   88% of Government Services peers do this. Limit: Measured for the homepage only, from one location, at the time of the check.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Accelerate

   HTTP/2 negotiated

   Observed: The TLS handshake selected http/1.1 instead of HTTP/2.

   What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.

   55% of Government Services peers do this.

   Guide: CDN Guide for Website Owners

3. Priority 3 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   What to do: Send Strict-Transport-Security on HTTPS responses. Start with a short max-age (for example 300 seconds), confirm every subdomain works over HTTPS, then raise it in steps to 31536000. Add includeSubDomains only when all subdomains are HTTPS. HSTS preload is optional and hard to undo; hstspreload.org itself does not recommend it by default.

   51% of Government Services peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for pref.kanagawa.jp was p=none, which asks receivers to take no action on failing mail.

   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.

   Guide: A Practical Website Health Check for Owners

What pref.kanagawa.jp already does well

Practices fewer than half of Government Services peers use.

• DNSSEC signedDNSSEC delegation (DS record) present.19% of peers
• Nameservers spread across providersNameservers spread across more than one operator.25% of peers
• Social preview image setog:image present.36% of peers

What we saw

Homepage checked

https://www.pref.kanagawa.jp/

Homepage response

HTTP 200

TLS

TLSv1.3, http/1.1

Certificate

GlobalSign, 199-day validity, expiring 2027-04-16

DNS operators

3 self-run or other nameserver domains

DMARC policy

p=none

Homepage HTML

27 KB, gzip

Images on homepage

33 (jpg 18, png 15)

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

• moi.gov.eg36
• motortax.ie36
• portal.edu.az36
• sss.gov.ph36
• statedrugs.gov.in36

Government Services readiness benchmark