docomo.ne.jp

Readiness by lane

Green: docomo.ne.jp. Thin bar: Telecommunications & Internet peer median.

Priority fixes for docomo.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 183 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 Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.

   54% of Telecommunications & Internet 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.

   88% of Telecommunications & Internet peers do this.

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

3. Priority 3 · Enable

   XML sitemap discoverable

   Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

   What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

   83% of Telecommunications & Internet peers do this.

   Guide: XML Sitemap Guide: Include Only URLs You Stand Behind

4. Priority 4 · 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.

   41% of Telecommunications & Internet peers do this.

   Guide: Browser Caching Guide for Website Owners

What docomo.ne.jp already does well

Practices fewer than half of Telecommunications & Internet peers use.

• Reachable over IPv6IPv6 address published.33% of peers

What we saw

Homepage checked

https://www.docomo.ne.jp/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

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

CDN or edge

Amazon CloudFront

Platform or framework

Adobe Experience Manager

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 183 days

DMARC policy

p=quarantine

Homepage HTML

181 KB, gzip

Images on homepage

129 (svg 102, png 13, webp 13)

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 Telecommunications & Internet sites

• claro.com.do59
• im3.id59
• softbank.jp59
• tntph.com60
• vodafone.gr60

Telecommunications & Internet readiness benchmark