insecam.org

Readiness by lane

Green: insecam.org. Thin bar: Security & Monitoring peer median.

Priority fixes for insecam.org

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://www.insecam.org/ 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.

   88% of Security & Monitoring 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

   HSTS kept for at least a year

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

   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.

   42% of Security & Monitoring peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Accelerate

   Modern image formats in use

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

   50% of Security & Monitoring peers do this.

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

4. Priority 4 · Harden

   DMARC policy enforces quarantine or reject

   Observed: No DMARC record was found at _dmarc.insecam.org.

   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.

   40% of Security & Monitoring peers do this.

   Guide: A Practical Website Health Check for Owners

What we saw

Homepage checked

http://www.insecam.org/

Homepage response

HTTP 200

DNS operators

1 self-run or other nameserver domain

Homepage HTML

18 KB, gzip

Images on homepage

9 (jpg 1)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

All 31 checks

Select a gap for the method and fix. How each check works

Compare with other Security & Monitoring sites

• brunoespiao.com.br57
• chopluna.ru51
• mobile-tracker-free.com62
• mobile-tracker-free.fr58
• tabangohar.com64

Security & Monitoring readiness benchmark