STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

gqjapan.jp

gqjapan.jp's public homepage, certificate and DNS checked against 31 practices and compared with 3,856 News & Media sites.

Readiness index
79/100

News & Media median 68

Ahead of
86%

of measured News & Media sites

Practices observed
23/31

0 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 11:42:43 UTC from one location. How we measure

Readiness by lane

Green: gqjapan.jp. Thin bar: News & Media peer median.

Enable

100/100

Peers 89

Harden

65/100

Peers 56

Accelerate

85/100

Peers 68

Recover

0/100

Peers 11

Priority fixes for gqjapan.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.

    35% of News & Media 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 60 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.

    44% of News & Media peers do this.

  3. Priority 3 · Harden

    Certificate lifetime of 100 days or less

    Observed: The certificate from Amazon had a 394-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.

    66% of News & Media peers do this.

  4. Priority 4 · Harden

    CAA records limit who can issue certificates

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

    13% of News & Media peers do this.

What gqjapan.jp already does well

Practices fewer than half of News & Media peers use.

  • Content Security Policy presentContent-Security-Policy present.29% of peers
  • HTTP/3 advertisedHTTP/3 advertised.36% of peers
  • DMARC policy enforces quarantine or rejectDMARC policy p=reject.37% of peers

What we saw

Homepage checked
https://www.gqjapan.jp/
Homepage response
HTTP 200
TLS
TLSv1.3, HTTP/2
Certificate
Amazon, 394-day validity, expiring 2027-03-06
CDN or edge
Amazon CloudFront
DNS operators
Amazon Route 53
DMARC policy
p=reject
Homepage HTML
1,538 KB, br
Images on homepage
60 (jpg 726, png 50, svg 2)

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 23

  • HTTP requests move to HTTPS
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • DMARC policy enforces quarantine or reject
  • X-Content-Type-Options: nosniff
  • Framing restricted
  • Content Security Policy present
  • HTTP/2 negotiated
  • HTTP/3 advertised
  • HTML compressed
  • Static files cached for 30 days or more
  • 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
  • Structured data present
  • Social preview image set
  • Page language declared
  • At most one redirect to the homepage

Own gqjapan.jp?

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: gqjapan.jp. This profile covers configuration only.

Compare with other News & Media sites