alditalk.de

Readiness by lane

Green: alditalk.de. Thin bar: Telecommunications & Internet peer median.

Priority fixes for alditalk.de

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 0 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.

   54% of Telecommunications & Internet 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 · Enable

   robots.txt published

   Observed: No robots.txt file was returned at the site root.

   What to do: Publish /robots.txt with any crawl rules you need and a Sitemap: line pointing to your XML sitemap.

   88% of Telecommunications & Internet peers do this.

   Guide: Robots.txt Guide: Control Crawling Without Hiding Mistakes

3. Priority 3 · Harden

   DMARC policy enforces quarantine or reject

   Observed: No DMARC record was found at _dmarc.alditalk.de.

   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.

   59% of Telecommunications & Internet peers do this.

   Guide: A Practical Website Health Check for Owners

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

   76% of Telecommunications & Internet peers do this.

   Guide: Canonical Tags: A Decision Guide for Duplicate URLs

What alditalk.de already does well

Practices fewer than half of Telecommunications & Internet peers use.

• Nameservers spread across providersNameservers spread across more than one operator.16% of peers
• Static files cached for 30 days or moreLong-lived caching on static files.41% of peers

What we saw

Homepage checked

https://www.alditalk.de/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 198-day validity, expiring 2026-12-04

DNS operators

2 self-run or other nameserver domains

HSTS

max-age 0 days

Homepage HTML

218 KB, gzip

Images on homepage

50 (png 81, jpg 23, svg 10)

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 Telecommunications & Internet sites

• a1.bg62
• play.pl62
• pldthome.com62
• totalwireless.com63
• yousee.dk63

Telecommunications & Internet readiness benchmark