Bitrix: readiness playbook

Readiness by lane

The Bitrix playbook

Gaps ordered by impact, with the platform-specific step where one exists.

1. HSTS kept for at least a year

   28% observed · all sites 31%

   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.

   Guide: HTTPS and TLS Guide for Website Owners

2. DMARC policy enforces quarantine or reject

   28% observed · all sites 31%

   Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.

   Guide: A Practical Website Health Check for Owners

3. security.txt published

   <1% observed · all sites 5.5%

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

   Guide: A Practical Website Health Check for Owners

4. CAA records limit who can issue certificates

   2.9% observed · all sites 11%

   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.

   Guide: HTTPS and TLS Guide for Website Owners

5. HTTP/3 advertised

   3.2% observed · all sites 36%

   Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.

   Guide: CDN Guide for Website Owners

6. Modern image formats in use

   42% observed · all sites 40%

   Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.

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

7. Content Security Policy present

   25% observed · all sites 31%

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

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

8. DNSSEC signed

   <1% observed · all sites 8.1%

   Enable DNSSEC at your DNS provider, then add the DS record at your registrar. Plan provider moves carefully: a stale DS record can make the domain fail to resolve.

   Guide: Website Uptime Readiness: Prepare Before Traffic Arrives

Where Bitrix sites lead

• Static files cached for 30 days or more69% observedall sites 50%
• XML sitemap discoverable91% observedall sites 73%
• robots.txt published97% observedall sites 79%
• Nameservers spread across providers24% observedall sites 11%

All 31 checks on Bitrix

High-readiness Bitrix sites

• prufy.ru72

Related