abadis.ir

Readiness by lane

Green: abadis.ir. Thin bar: Literary & Knowledge peer median.

Priority fixes for abadis.ir

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

1. Priority 1 · Harden

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   Why it matters: TLS 1.3 removes legacy cipher suites and completes the handshake in fewer round trips, so it is both safer and faster for new connections.

   What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

   On Cloudflare: Turn on TLS 1.3 under SSL/TLS > Edge Certificates.

   88% of Literary & Knowledge peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   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.

   28% of Literary & Knowledge peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Enable

   Canonical URL declared

   Observed: The homepage did not declare a canonical URL.

   What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.

   67% of Literary & Knowledge peers do this.

   Guide: Canonical Tags: A Decision Guide for Duplicate URLs

4. Priority 4 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for abadis.ir was p=none, which asks receivers to take no action on failing mail.

   What to do: 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.

   22% of Literary & Knowledge peers do this.

   Guide: A Practical Website Health Check for Owners

What abadis.ir already does well

Practices fewer than half of Literary & Knowledge peers use.

• Modern image formats in useWebP or AVIF images detected.31% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.48% of peers
• Offscreen images lazy-loadedNative lazy loading in use.48% of peers

What we saw

Homepage checked

https://abadis.ir/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

Asseco Data Systems S.A., 198-day validity, expiring 2027-02-05

DNS operators

Cloudflare

DMARC policy

p=none

Homepage HTML

50 KB, gzip

Images on homepage

14 (webp 12, svg 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 Literary & Knowledge sites

• 8ghrb.com56
• akknovel.com56
• bcn.cl56
• truyentranhdammyy.site57
• vymanga.site57

Literary & Knowledge readiness benchmark