hmd.com

Readiness by lane

Green: hmd.com. Thin bar: Telecommunications & Internet peer median.

Priority fixes for hmd.com

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.

   On Azure Front Door/CDN: Add a response header action in a Front Door rule set.

   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 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for hmd.com 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.

   59% of Telecommunications & Internet peers do this.

   Guide: A Practical Website Health Check for Owners

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

   48% of Telecommunications & Internet peers do this.

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

4. Priority 4 · Harden

   X-Content-Type-Options: nosniff

   Observed: The homepage response did not include X-Content-Type-Options: nosniff.

   What to do: Send X-Content-Type-Options: nosniff on all responses and make sure each file is served with the correct Content-Type.

   64% of Telecommunications & Internet peers do this.

   Guide: A Practical Website Health Check for Owners

What hmd.com already does well

Practices fewer than half of Telecommunications & Internet peers use.

• Reachable over IPv6IPv6 address published.33% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.37% 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.hmd.com/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 184-day validity, expiring 2027-02-17

CDN or edge

Azure Front Door/CDN

DNS operators

GoDaddy DNS

DMARC policy

p=none

Homepage HTML

612 KB, br

Images on homepage

35 (png 1128, jpg 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

• blau.de71
• comviq.se71
• free.fr71
• jcom.co.jp71
• mci.ir71

Telecommunications & Internet readiness benchmark