mlit.go.jp

Readiness by lane

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

Priority fixes for mlit.go.jp

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

1. Priority 1 · Harden

   HSTS kept for at least a year

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

   Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.

   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.

   On Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.

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

   Guide: HTTPS and TLS Guide for Website 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 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

4. Priority 4 · Harden

   Framing restricted

   Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

   What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

   On Amazon CloudFront: Set frame options in a response headers policy.

   68% of Government Services peers do this.

   Guide: A Practical Website Health Check for Owners

What mlit.go.jp already does well

Practices fewer than half of Government Services peers use.

• Nameservers spread across providersNameservers spread across more than one operator.25% of peers

What we saw

Homepage checked

https://www.mlit.go.jp/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

SECOM Trust Systems Co., Ltd., 188-day validity, expiring 2027-02-21

CDN or edge

Amazon CloudFront

DNS operators

3 self-run or other nameserver domains

DMARC policy

p=quarantine

Homepage HTML

59 KB, gzip

Images on homepage

79 (png 37, svg 27, jpg 14, gif 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

Compare with other Government Services sites

• financnasprava.sk45
• juntadeandalucia.es45
• magyarorszag.hu45
• parichay.nic.in45
• philhealth.gov.ph45

Government Services readiness benchmark