takvim.com.tr

Readiness by lane

Green: takvim.com.tr. Thin bar: News & Media peer median.

Priority fixes for takvim.com.tr

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

1. Priority 1 · Harden

   Certificate has more than 14 days left

   Observed: The certificate from GoDaddy.com, Inc. was due to expire on 2026-11-06 (14 days after the check).

   Why it matters: An expired certificate makes browsers show a full-page warning. Renewing well ahead of expiry leaves time to fix a failed renewal.

   What to do: Automate renewal with ACME (for example Let's Encrypt or your CDN's managed certificates) and add a renewal review to your release calendar so any certificate inside 21 days of expiry gets attention.

   99% of News & Media 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 Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.

   35% of News & Media peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Harden

   Certificate lifetime of 100 days or less

   Observed: The certificate from GoDaddy.com, Inc. had a 198-day validity period, longer than the 100-day maximum that applies from March 2027.

   What to do: Move to automated issuance and renewal now, while you still have time to test it.

   66% of News & Media peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

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

   29% of News & Media peers do this.

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

What takvim.com.tr already does well

Practices fewer than half of News & Media peers use.

• Referrer-Policy setReferrer-Policy present.22% of peers
• HTTP/3 advertisedHTTP/3 advertised.36% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=reject.37% of peers

What we saw

Homepage checked

https://www.takvim.com.tr/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

GoDaddy, 198-day validity, expiring 2026-11-06

CDN or edge

Amazon CloudFront

DNS operators

Amazon Route 53

DMARC policy

p=reject

Homepage HTML

272 KB, gzip

Images on homepage

205 (jpg 185, png 75, webp 3, 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 News & Media sites

• starhit.ru71
• starnieuws.com71
• stavropol.media71
• telegram.hr71
• telemadrid.es71

News & Media readiness benchmark