transphoto.org

Readiness by lane

Green: transphoto.org. Thin bar: Forums & Communities peer median.

Priority fixes for transphoto.org

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

1. Priority 1 · Harden

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   Why it matters: TLS 1.3 removes legacy cipher suites and completes the handshake in fewer round trips, so it is both safer and faster for new connections.

   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.

   On Cloudflare: Turn on TLS 1.3 under SSL/TLS > Edge Certificates.

   88% of Forums & Communities peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Enable

   XML sitemap discoverable

   Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

   What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

   61% of Forums & Communities peers do this.

   Guide: XML Sitemap Guide: Include Only URLs You Stand Behind

3. Priority 3 · 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.

   On Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.

   28% of Forums & Communities peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for transphoto.org 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.

   31% of Forums & Communities peers do this.

   Guide: A Practical Website Health Check for Owners

What transphoto.org already does well

Practices fewer than half of Forums & Communities peers use.

• HTTP/3 advertisedHTTP/3 advertised.33% of peers
• Reachable over IPv6IPv6 address published.47% of peers

What we saw

Homepage checked

https://transphoto.org/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

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

CDN or edge

Cloudflare

DNS operators

Cloudflare

DMARC policy

p=none

Homepage HTML

287 KB, br

Images on homepage

166 (gif 144, jpg 15, png 5)

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 Forums & Communities sites

• gamerch.com48
• girlswithmuscle.com49
• grupostelegram.net49
• gruposwats.com49
• vin.com49

Forums & Communities readiness benchmark