explore.org

Readiness by lane

Green: explore.org. Thin bar: Live Streaming peer median.

Priority fixes for explore.org

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   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.

   29% of Live Streaming 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.

   45% of Live Streaming peers do this.

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

3. Priority 3 · Enable

   Canonical URL declared

   Observed: The homepage did not declare a canonical URL.

   What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.

   67% of Live Streaming peers do this.

   Guide: Canonical Tags: A Decision Guide for Duplicate URLs

4. Priority 4 · Harden

   Framing restricted

   Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

   What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

   On Next.js: Add it in next.config.js headers().

   39% of Live Streaming peers do this.

   Guide: A Practical Website Health Check for Owners

What explore.org already does well

Practices fewer than half of Live Streaming peers use.

• Content Security Policy presentContent-Security-Policy present.24% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=reject.29% of peers
• Static files cached for 30 days or moreLong-lived caching on static files.48% of peers

What we saw

Homepage checked

https://explore.org/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2026-12-31

Platform or framework

Next.js

DNS operators

Amazon Route 53

DMARC policy

p=reject

Homepage HTML

58 KB, gzip

Images on homepage

2 (svg 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 Live Streaming sites

• botrix.live70
• hot51.llc65
• latina.pe64
• skylinewebcams.com66
• twitch.tv67

Live Streaming readiness benchmark