novelai.net

Readiness by lane

Green: novelai.net. Thin bar: Design & Content Creation peer median.

Priority fixes for novelai.net

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.

   37% of Design & Content Creation 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

   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.

   80% of Design & Content Creation peers do this.

   Guide: Canonical Tags: A Decision Guide for Duplicate URLs

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

   64% of Design & Content Creation peers do this.

   Guide: Structured Data Basics for Website Owners

4. Priority 4 · Harden

   Content Security Policy present

   Observed: The homepage response did not include a Content-Security-Policy header.

   What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.

   On Next.js: Next.js documents nonce-based CSP with middleware.

   29% of Design & Content Creation peers do this.

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

What novelai.net already does well

Practices fewer than half of Design & Content Creation peers use.

• security.txt publishedsecurity.txt with a contact found.9.1% of peers
• CAA records limit who can issue certificatesCAA limits issuance to comodoca.com, digicert.com, letsencrypt.org and others.17% of peers
• Referrer-Policy setReferrer-Policy present.26% of peers

What we saw

Homepage checked

https://novelai.net/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2027-01-16

CDN or edge

Cloudflare

Platform or framework

Next.js

DNS operators

Cloudflare

DMARC policy

p=reject

Homepage HTML

154 KB, br

Images on homepage

61 (webp 180, svg 1)

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 Design & Content Creation sites

• 1001fonts.com84
• fish.audio84
• heygen.com84
• pixelbin.io84
• suno.com84

Design & Content Creation readiness benchmark