atsu.moe

Readiness by lane

Green: atsu.moe. Thin bar: Literary & Knowledge peer median.

Priority fixes for atsu.moe

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.

   28% of Literary & Knowledge 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

   Structured data present

   Observed: The homepage had no JSON-LD structured data.

   What to do: Add JSON-LD for your organization and main content types, then test it with Google's Rich Results Test.

   46% of Literary & Knowledge peers do this.

   Guide: Structured Data Basics for Website Owners

3. Priority 3 · Harden

   CAA records limit who can issue certificates

   Observed: No CAA record was found for atsu.moe, so any public certificate authority may issue for it.

   What to do: Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.

   On Cloudflare: Cloudflare documents which CAs its managed certificates need; include them in your CAA records.

   13% of Literary & Knowledge peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Harden

   security.txt published

   Observed: No valid /.well-known/security.txt with a Contact field was returned.

   What to do: Publish /.well-known/security.txt with at least Contact and Expires fields, as RFC 9116 requires, and review it before it expires.

   On Cloudflare: Cloudflare Security Center can serve a security.txt file for the zone.

   5% of Literary & Knowledge peers do this.

   Guide: A Practical Website Health Check for Owners

What atsu.moe already does well

Practices fewer than half of Literary & Knowledge peers use.

• Content Security Policy presentContent-Security-Policy present.18% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.22% of peers
• Referrer-Policy setReferrer-Policy present.22% of peers

What we saw

Homepage checked

https://atsu.moe/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

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

CDN or edge

Cloudflare

DNS operators

Cloudflare

HSTS

max-age 180 days

DMARC policy

p=quarantine

Homepage HTML

22 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 Literary & Knowledge sites

• akkords.pro83
• honeytoon.com83
• okutoon.com84
• runescape.wiki84
• tamil2lyrics.com83

Literary & Knowledge readiness benchmark