STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

esakal.com

esakal.com's public homepage, certificate and DNS checked against 31 practices and compared with 3,856 News & Media sites.

Readiness index
80/100

News & Media median 68

Ahead of
90%

of measured News & Media sites

Practices observed
22/30

1 of 31 could not be measured

Popularity band
Top 10K

Chrome UX Report top-sites list

Measured 2026-10-23 12:18:38 UTC from one location. How we measure

Readiness by lane

Green: esakal.com. Thin bar: News & Media peer median.

Enable

92/100

Peers 89

Harden

65/100

Peers 56

Accelerate

100/100

Peers 68

Recover

0/100

Peers 11

Priority fixes for esakal.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 1 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.

    35% of News & Media peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

  2. Priority 2 · Enable

    Social preview image set

    Observed: The homepage had no og:image, so shared links may show without a preview image.

    What to do: Add Open Graph tags, including og:image with a 1200 x 630 image.

    71% of News & Media peers do this.

  3. Priority 3 · Harden

    X-Content-Type-Options: nosniff

    Observed: The homepage response did not include X-Content-Type-Options: nosniff.

    What to do: Send X-Content-Type-Options: nosniff on all responses and make sure each file is served with the correct Content-Type.

    On Cloudflare: Add the header with a response header transform rule.

    42% of News & Media peers do this.

  4. Priority 4 · Harden

    CAA records limit who can issue certificates

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

    13% of News & Media peers do this.

What esakal.com already does well

Practices fewer than half of News & Media peers use.

  • Content Security Policy presentContent-Security-Policy present.29% of peers
  • HTTP/3 advertisedHTTP/3 advertised.36% of peers
  • DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.37% of peers

What we saw

Homepage checked
https://www.esakal.com/
Homepage response
HTTP 200
TLS
TLSv1.3, HTTP/2
Certificate
Google Trust Services, 90-day validity, expiring 2026-11-30
CDN or edge
Cloudflare
DNS operators
Cloudflare
HSTS
max-age 1 days
DMARC policy
p=quarantine
Homepage HTML
2,230 KB, br
Images on homepage
84 (png 3)

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

Observed 22

  • HTTP requests move to HTTPS
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • Certificate lifetime of 100 days or less
  • DMARC policy enforces quarantine or reject
  • Framing restricted
  • Content Security Policy present
  • HTTP/2 negotiated
  • HTTP/3 advertised
  • HTML compressed
  • Modern image formats in use
  • Offscreen images lazy-loaded
  • No render-blocking scripts in <head>
  • robots.txt published
  • XML sitemap discoverable
  • Reachable over IPv6
  • Canonical URL declared
  • Meta description written
  • Mobile viewport configured
  • Structured data present
  • Page language declared
  • At most one redirect to the homepage

Not measured 1

  • Static files cached for 30 days or more

Own esakal.com?

Re-run the checks after a change, keep a private action plan in a free workspace, or report a mistake.

Live status for this site: Status Is Down: esakal.com. This profile covers configuration only.

Compare with other News & Media sites