coccoc.com

Readiness by lane

Green: coccoc.com. Thin bar: Search Engines peer median.

Priority fixes for coccoc.com

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

1. Priority 1 · Harden

   HTTP requests move to HTTPS

   Observed: A request to http://coccoc.com/ was not redirected to HTTPS.

   Why it matters: Visitors who type the address or follow an old link start on unencrypted HTTP. A redirect moves them to the encrypted site before any cookies or form data are sent.

   What to do: Add a permanent (301 or 308) redirect from every http:// URL to the same https:// URL at your CDN, load balancer or web server.

   87% of Search Engines peers do this. Limit: Measured for the homepage only, from one location, at the time of the check.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Harden

   Certificate has more than 14 days left

   Observed: The certificate from GlobalSign nv-sa was due to expire on 2026-11-07 (14 days after the check).

   What to do: Automate renewal with ACME (for example Let's Encrypt or your CDN's managed certificates) and add a renewal review to your release calendar so any certificate inside 21 days of expiry gets attention.

   98% of Search Engines peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Harden

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

   90% of Search Engines peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 182 days, below the one-year benchmark.

   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.

   30% of Search Engines peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What coccoc.com already does well

Practices fewer than half of Search Engines peers use.

• Nameservers spread across providersNameservers spread across more than one operator.8.5% of peers
• Content Security Policy presentContent-Security-Policy present.28% of peers
• Referrer-Policy setReferrer-Policy present.28% of peers

What we saw

Homepage checked

https://coccoc.com/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

GlobalSign, 199-day validity, expiring 2026-11-07

Platform or framework

Astro

DNS operators

2 self-run or other nameserver domains

HSTS

max-age 182 days, includeSubDomains

DMARC policy

p=reject

Homepage HTML

122 KB, gzip

Images on homepage

45 (svg 21, png 18, jpg 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 Search Engines sites

• azet.sk65
• rambler.ru64
• shuru.co.in68
• tgramsearch.com64
• yahoo.co.jp66

Search Engines readiness benchmark