prosettings.net

Readiness by lane

Green: prosettings.net. Thin bar: Gaming Platforms & Consoles peer median.

Priority fixes for prosettings.net

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 180 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.

   30% of Gaming Platforms & Consoles 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 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for prosettings.net 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.

   26% of Gaming Platforms & Consoles peers do this.

   Guide: A Practical Website Health Check for Owners

3. Priority 3 · Accelerate

   HTTP/3 advertised

   Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.

   What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.

   On Cloudflare: Enable HTTP/3 (with QUIC) under Speed > Optimization > Protocol Optimization.

   42% of Gaming Platforms & Consoles peers do this.

   Guide: CDN Guide for Website Owners

4. Priority 4 · Harden

   Content Security Policy present

   Observed: The homepage response did not include a Content-Security-Policy header.

   What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.

   22% of Gaming Platforms & Consoles peers do this.

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

What prosettings.net already does well

Practices fewer than half of Gaming Platforms & Consoles peers use.

• Referrer-Policy setReferrer-Policy present.26% of peers
• X-Content-Type-Options: nosniffnosniff header present.38% of peers
• Structured data presentJSON-LD structured data found.40% of peers

What we saw

Homepage checked

https://prosettings.net/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

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

CDN or edge

Cloudflare

Platform or framework

WordPress

DNS operators

Cloudflare

HSTS

max-age 180 days, includeSubDomains, preload

DMARC policy

p=none

Homepage HTML

176 KB, br

Images on homepage

168 (png 442, webp 72, svg 34, jpg 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

Compare with other Gaming Platforms & Consoles sites

• kupikod.com77
• macrospacepanel.net77
• method.gg77
• renderz.app77
• rollercoin.com77

Gaming Platforms & Consoles readiness benchmark