ixdzs8.com

Readiness by lane

Green: ixdzs8.com. Thin bar: Literary & Knowledge peer median.

Priority fixes for ixdzs8.com

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

1. Priority 1 · Harden

   HTTP requests move to HTTPS

   Observed: A request to http://ixdzs8.com/ was not redirected to HTTPS.

   Why it matters: Visitors who type the address or follow an old link start on unencrypted HTTP. A redirect moves them to the encrypted site before any cookies or form data are sent.

   What to do: Add a permanent (301 or 308) redirect from every http:// URL to the same https:// URL at your CDN, load balancer or web server.

   89% of Literary & Knowledge peers do this. Limit: Measured for the homepage only, from one location, at the time of the check.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Harden

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   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.

   88% of Literary & Knowledge peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Enable

   XML sitemap discoverable

   Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

   What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

   69% of Literary & Knowledge peers do this.

   Guide: XML Sitemap Guide: Include Only URLs You Stand Behind

4. Priority 4 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 1 hours, short of the 30-day benchmark.

   What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.

   49% of Literary & Knowledge peers do this.

   Guide: Browser Caching Guide for Website Owners

What ixdzs8.com already does well

Practices fewer than half of Literary & Knowledge peers use.

• DMARC policy enforces quarantine or rejectDMARC policy p=reject.22% of peers
• HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.28% of peers
• Structured data presentJSON-LD structured data found.46% of peers

What we saw

Homepage checked

https://ixdzs8.com/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

SSL2BUY EMEA LLC, 395-day validity, expiring 2027-01-18

DNS operators

GoDaddy DNS

HSTS

max-age 365 days, includeSubDomains, preload

DMARC policy

p=reject

Homepage HTML

57 KB, gzip

Images on homepage

45 (jpg 44)

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

• fantlab.ru42
• icd10data.com42
• lyricstape.com42
• mtgwiki.com43
• piaotia.com42

Literary & Knowledge readiness benchmark