pch.com

Readiness by lane

Green: pch.com. Thin bar: Uncategorized peer median.

Priority fixes for pch.com

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 91 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 Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.

   34% of Uncategorized 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

   Modern image formats in use

   Observed: The homepage had 45 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.

   On Cloudflare: Cloudflare Polish can convert images to WebP.

   33% of Uncategorized peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

3. Priority 3 · Harden

   security.txt published

   Observed: No valid /.well-known/security.txt with a Contact field was returned.

   What to do: Publish /.well-known/security.txt with at least Contact and Expires fields, as RFC 9116 requires, and review it before it expires.

   On Cloudflare: Cloudflare Security Center can serve a security.txt file for the zone.

   4.5% of Uncategorized peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Harden

   DNSSEC signed

   Observed: No DS record was found for pch.com at its parent zone, so its DNS answers are not DNSSEC-signed.

   What to do: Enable DNSSEC at your DNS provider, then add the DS record at your registrar. Plan provider moves carefully: a stale DS record can make the domain fail to resolve.

   On Cloudflare: Enable DNSSEC in DNS > Settings and add the DS record at the registrar.

   9.3% of Uncategorized peers do this.

   Guide: Website Uptime Readiness: Prepare Before Traffic Arrives

What pch.com already does well

Practices fewer than half of Uncategorized peers use.

• CAA records limit who can issue certificatesCAA limits issuance to digicert.com, globalsign.com, letsencrypt.org and others.8.7% of peers
• Content Security Policy presentContent-Security-Policy present.24% of peers
• HTTP/3 advertisedHTTP/3 advertised.33% of peers

What we saw

Homepage checked

https://www.pch.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2026-11-30

CDN or edge

Cloudflare, Shopify

Platform or framework

Shopify

DNS operators

Amazon Route 53

HSTS

max-age 91 days

DMARC policy

p=reject

Homepage HTML

845 KB, br

Images on homepage

45 (png 89, jpg 34, svg 4)

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 Uncategorized sites

• change.org82
• godrejenterprises.com85
• hrw.org82
• receitasnestle.com.br87
• sinaisdoguga.com88

Uncategorized readiness benchmark