atpress.ne.jp

Readiness by lane

Green: atpress.ne.jp. Thin bar: SEO & Email Marketing peer median.

Priority fixes for atpress.ne.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: Strict-Transport-Security was sent with a max-age of 0 days, below the one-year benchmark.

   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 Next.js: Add the header in the headers() option of next.config.js for all routes.

   36% of SEO & Email Marketing 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 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script without async or defer.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   On Next.js: Use the next/script component with an appropriate loading strategy.

   56% of SEO & Email Marketing peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

3. Priority 3 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for atpress.ne.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.

   37% of SEO & Email Marketing peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Harden

   CAA records limit who can issue certificates

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

   20% of SEO & Email Marketing peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What atpress.ne.jp already does well

Practices fewer than half of SEO & Email Marketing peers use.

• Content Security Policy presentContent-Security-Policy present.27% of peers
• HTTP/3 advertisedHTTP/3 advertised.41% of peers
• Modern image formats in useWebP or AVIF images detected.41% of peers

What we saw

Homepage checked

https://www.atpress.ne.jp/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2026-12-11

CDN or edge

Google edge

Platform or framework

Next.js

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 0 days

DMARC policy

p=none

Homepage HTML

933 KB, gzip

Images on homepage

776 (jpg 524, png 240, webp 12)

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 SEO & Email Marketing sites

• klaviyo.com78
• mailchimp.com76
• prtimes.jp73
• publer.com73
• seoclerk.com76

SEO & Email Marketing readiness benchmark