river.go.jp

Readiness by lane

Green: river.go.jp. Thin bar: Government Services peer median.

Priority fixes for river.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.river.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 · Enable

   robots.txt published

   Observed: No robots.txt file was returned at the site root.

   What to do: Publish /robots.txt with any crawl rules you need and a Sitemap: line pointing to your XML sitemap.

   61% of Government Services peers do this.

   Guide: Robots.txt Guide: Control Crawling Without Hiding Mistakes

3. Priority 3 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 1 hours, 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

4. Priority 4 · Enable

   Canonical URL declared

   Observed: The homepage did not declare a canonical URL.

   What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.

   41% of Government Services peers do this.

   Guide: Canonical Tags: A Decision Guide for Duplicate URLs

What river.go.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
• No render-blocking scripts in <head>Head scripts load without blocking.39% of peers

What we saw

Homepage checked

https://www.river.go.jp/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

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

CDN or edge

Akamai

DNS operators

3 self-run or other nameserver domains

HSTS

max-age 365 days

Homepage HTML

9 KB, gzip

Images on homepage

0

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

• apprenticeshipindia.gov.in65
• odigostoupoliti.eu66
• oss.go.id66
• psahelpline.ph66
• turkiye.gov.tr66

Government Services readiness benchmark