anilist.co

Readiness by lane

Green: anilist.co. Thin bar: Forums & Communities peer median.

Priority fixes for anilist.co

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

   28% of Forums & Communities 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 · Enable

   Meta description written

   Observed: The homepage had no meta description.

   What to do: Write a short, specific description of the page for people, not a list of keywords.

   85% of Forums & Communities peers do this.

   Guide: Meta Titles and Descriptions That Match Search Intent

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.

   61% of Forums & Communities peers do this.

   Guide: Canonical Tags: A Decision Guide for Duplicate URLs

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

   33% of Forums & Communities peers do this.

   Guide: CDN Guide for Website Owners

What anilist.co already does well

Practices fewer than half of Forums & Communities peers use.

• DMARC policy enforces quarantine or rejectDMARC policy p=reject.31% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.41% of peers
• X-Content-Type-Options: nosniffnosniff header present.47% of peers

What we saw

Homepage checked

https://anilist.co/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

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

CDN or edge

Cloudflare

DNS operators

Cloudflare

DMARC policy

p=reject

Homepage HTML

5 KB, br

Images on homepage

0

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

• discord-ch.site68
• filmmakers.co.kr68
• masrawysat.com69
• muusikoiden.net69
• whackahack.com69

Forums & Communities readiness benchmark