informabtl.com

Readiness by lane

Green: informabtl.com. Thin bar: Data & Analytics peer median.

Priority fixes for informabtl.com

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.

   34% of Data & Analytics 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 · Accelerate

   Modern image formats in use

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

   On Cloudflare: Cloudflare Polish can convert images to WebP.

   31% of Data & Analytics peers do this.

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

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

   24% of Data & Analytics peers do this.

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

4. Priority 4 · Harden

   CAA records limit who can issue certificates

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

   15% of Data & Analytics peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What informabtl.com already does well

Practices fewer than half of Data & Analytics peers use.

• DNSSEC signedDNSSEC delegation (DS record) present.8.2% of peers
• Referrer-Policy setReferrer-Policy present.33% of peers
• HTTP/3 advertisedHTTP/3 advertised.37% of peers

What we saw

Homepage checked

https://www.informabtl.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

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

CDN or edge

Cloudflare

Platform or framework

WordPress

DNS operators

Cloudflare

HSTS

max-age 180 days, preload

DMARC policy

p=quarantine

Homepage HTML

595 KB, br

Images on homepage

138 (jpg 253, png 8, gif 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 Data & Analytics sites

• dolarbluebolivia.click80
• hsi.com.hk82
• investidor10.com.br84
• keepa.com86
• listafirme.ro81

Data & Analytics readiness benchmark