rade.ir

Readiness by lane

Green: rade.ir. Thin bar: Banking & Finance peer median.

Priority fixes for rade.ir

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.

   62% of Banking & Finance 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 · 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.

   51% of Banking & Finance peers do this.

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

3. Priority 3 · Accelerate

   HTTP/3 advertised

   Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.

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

   22% of Banking & Finance peers do this.

   Guide: CDN Guide for Website Owners

4. Priority 4 · Harden

   CAA records limit who can issue certificates

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

   20% of Banking & Finance peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What rade.ir already does well

Practices fewer than half of Banking & Finance peers use.

• No render-blocking scripts in <head>Head scripts load without blocking.36% of peers
• Modern image formats in useWebP or AVIF images detected.37% of peers
• Static files cached for 30 days or moreLong-lived caching on static files.43% of peers

What we saw

Homepage checked

https://www.rade.ir/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Asseco Data Systems S.A., 198-day validity, expiring 2027-03-18

Platform or framework

WordPress

DNS operators

1 self-run or other nameserver domain

DMARC policy

p=reject

Homepage HTML

827 KB, gzip

Images on homepage

131 (svg 106, jpg 71, png 7, webp 6)

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 Banking & Finance sites

• bankhapoalim.co.il76
• chase.com76
• piramalfinance.com76
• tatacapital.com76
• tavex.pl76

Banking & Finance readiness benchmark