orange.be

Readiness by lane

Green: orange.be. Thin bar: Telecommunications & Internet peer median.

Priority fixes for orange.be

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

1. Priority 1 · Harden

   DMARC policy enforces quarantine or reject

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

   Why it matters: An enforcing DMARC policy helps receiving mail systems reject email that falsely claims to come from your domain, a common route for phishing your customers.

   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. Limit: Read from public DNS at the time of the check; records may have changed since.

   Guide: A Practical Website Health Check for Owners

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

   41% of Telecommunications & Internet peers do this.

   Guide: Browser Caching Guide for Website Owners

3. Priority 3 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 4 external scripts without async or defer.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   37% of Telecommunications & Internet peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

4. Priority 4 · Enable

   Social preview image set

   Observed: The homepage had no og:image, so shared links may show without a preview image.

   What to do: Add Open Graph tags, including og:image with a 1200 x 630 image.

   59% of Telecommunications & Internet peers do this.

   Guide: SEO Checklist for a New Website

What orange.be already does well

Practices fewer than half of Telecommunications & Internet peers use.

• Referrer-Policy setReferrer-Policy present.33% of peers
• Content Security Policy presentContent-Security-Policy present.48% of peers

What we saw

Homepage checked

https://www.orange.be/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 197-day validity, expiring 2027-01-09

CDN or edge

Imperva, Acquia

Platform or framework

Drupal

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 365 days, includeSubDomains

DMARC policy

p=none

Homepage HTML

184 KB, gzip

Images on homepage

37 (webp 69, svg 7, jpg 1, png 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 Telecommunications & Internet sites

• hmd.com71
• jcom.co.jp71
• mci.ir71
• telenor.se71
• teltarif.de71

Telecommunications & Internet readiness benchmark