zendocs.com

Readiness by lane

Green: zendocs.com. Thin bar: Web Tools peer median.

Priority fixes for zendocs.com

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

1. Priority 1 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script without async or defer.

   Why it matters: A plain <script src> in the head stops the browser from showing anything until that file has downloaded and run.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   On Next.js: Use the next/script component with an appropriate loading strategy.

   69% of Web Tools peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

   Guide: Control Third-Party Scripts Before They Control Your Page

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

   15% of Web Tools peers do this.

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

3. Priority 3 · Harden

   CAA records limit who can issue certificates

   Observed: No CAA record was found for zendocs.com, 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.

   14% of Web Tools 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.

   4.8% of Web Tools peers do this.

   Guide: A Practical Website Health Check for Owners

What zendocs.com already does well

Practices fewer than half of Web Tools peers use.

• Nameservers spread across providersNameservers spread across more than one operator.6.1% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.23% of peers
• HSTS kept for at least a yearHSTS with a 730-day max-age covering subdomains.30% of peers

What we saw

Homepage checked

https://zendocs.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

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

CDN or edge

Cloudflare

Platform or framework

Next.js

DNS operators

3 self-run or other nameserver domains

HSTS

max-age 730 days, includeSubDomains, preload

DMARC policy

p=quarantine

Homepage HTML

812 KB, gzip

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 Web Tools sites

• brave.com85
• freeconvert.com84
• notube.im85
• publicrecordsdata.us84
• slt.bio85

Web Tools readiness benchmark