dailyverses.net

Readiness by lane

Green: dailyverses.net. Thin bar: Literary & Knowledge peer median.

Priority fixes for dailyverses.net

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.

   88% of Literary & Knowledge 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 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 30 days, below the one-year benchmark.

   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.

   28% of Literary & Knowledge peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Accelerate

   Modern image formats in use

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

   31% of Literary & Knowledge peers do this.

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

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.

   47% of Literary & Knowledge peers do this.

   Guide: CDN Guide for Website Owners

What dailyverses.net already does well

Practices fewer than half of Literary & Knowledge peers use.

• DNSSEC signedDNSSEC delegation (DS record) present.5.7% of peers
• Nameservers spread across providersNameservers spread across more than one operator.5.8% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=reject.22% of peers

What we saw

Homepage checked

https://dailyverses.net/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

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

DNS operators

3 self-run or other nameserver domains

HSTS

max-age 30 days

DMARC policy

p=reject

Homepage HTML

33 KB, gzip

Images on homepage

7 (jpg 7)

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

• chordzaa.com70
• emojigraph.org70
• fastdic.com70
• up-manga.com71
• wikihow.com71

Literary & Knowledge readiness benchmark