Website readiness profile · Snapshot 23 October 2026
celcomdigi.com
celcomdigi.com's public homepage, certificate and DNS checked against 31 practices and compared with 285 Telecommunications & Internet sites.
- Readiness index
- 82/100
- Ahead of
- 92%
- Practices observed
- 23/31
- Popularity band
- Top 50K
Telecommunications & Internet median 67
of measured Telecommunications & Internet sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: celcomdigi.com. Thin bar: Telecommunications & Internet peer median.
Enable
87/100
Peers 82
Harden
72/100
Peers 61
Accelerate
90/100
Peers 57
Recover
100/100
Peers 16
Priority fixes for celcomdigi.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
Content Security Policy present
Observed: The homepage response did not include a Content-Security-Policy header.
Why it matters: A CSP limits where scripts, styles and frames can load from, which reduces the impact of injected or compromised third-party code.
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.
On Webflow: this setting is largely controlled by the platform. Check the platform's settings and documentation, or ask its support team whether it can be changed for your domain.
48% of Telecommunications & Internet peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.
Guide: Payment Security and PCI DSS: What Website Owners Need to Know
Priority 2 · 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.
Priority 3 · Harden
CAA records limit who can issue certificates
Observed: No CAA record was found for celcomdigi.com, so any public certificate authority may issue for it.
What to do: Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.
15% of Telecommunications & Internet peers do this.
Priority 4 · Harden
security.txt published
Observed: No valid /.well-known/security.txt with a Contact field was returned.
What to do: Publish /.well-known/security.txt with at least Contact and Expires fields, as RFC 9116 requires, and review it before it expires.
13% of Telecommunications & Internet peers do this.
What celcomdigi.com 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
- Referrer-Policy setReferrer-Policy present.33% of peers
- No render-blocking scripts in <head>Head scripts load without blocking.37% of peers
What we saw
- Homepage checked
- https://www.celcomdigi.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Amazon, 197-day validity, expiring 2027-03-02
- CDN or edge
- Amazon CloudFront
- Platform or framework
- Webflow
- DNS operators
- 2 self-run or other nameserver domains
- HSTS
- max-age 365 days
- DMARC policy
- p=reject
- Homepage HTML
- 713 KB, br
- Images on homepage
- 40 (jpg 336, png 272, avif 5, webp 4)
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
Not observed 8
Observed 23
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Referrer-Policy set
- HTTP/2 negotiated
- HTML compressed
- Static files cached for 30 days or more
- Modern image formats in use
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Structured data present
- Page language declared
- At most one redirect to the homepage
- Nameservers spread across providers
Own celcomdigi.com?
Re-run the checks after a change, or verify the site in a free workspace to save reports with history, compare against similar sites and competitors, and track a private action plan. What owners get.
Live status for this site: Status Is Down: celcomdigi.com. This profile covers configuration only.