This is an intelligence module — it doesn't carry a score, but it tells you exactly what infrastructure your site (or a competitor's) is running on: which CDN is in front of it, who hosts it, whether a load balancer is distributing traffic, and what the server's technology fingerprint reveals.
🌿 Beginner — Plain English explanations
What is infrastructure intelligence?
Behind every website is a stack of invisible infrastructure: a hosting provider that physically runs the server, often a CDN (Content Delivery Network) that caches your content in data centres around the world so visitors load it from somewhere nearby, and sometimes a load balancer that spreads traffic across multiple servers so no single one gets overwhelmed. PEKRYON's scan detects and reports on all three, purely by analysing publicly visible response headers and DNS records — no login or server access required.
Why this matters even without a score
- CDN detection — confirms whether you're actually benefiting from a CDN you've paid for or configured, or whether traffic is hitting your origin server directly (slower, and more exposed to traffic spikes and DDoS attempts).
- Hosting provider identification — useful for due diligence when evaluating a site (e.g. before an acquisition) or simply confirming your own site is running where you expect.
- IP type — flags if your site's public-facing IP is accidentally in a private address range, which would mean it isn't actually reachable from the internet.
- ASN / Network — the Autonomous System Number and owning organization (e.g. "AS13335 Cloudflare, Inc.") — much more reliable infrastructure intel than header-pattern guessing alone.
- Geolocation — a country/city hint for where your server is physically located, useful for spotting a mismatch (e.g. a site claiming to be a local business hosted on another continent).
- Load balancer detection — indicates whether the site is architected to handle traffic spikes gracefully or is running on a single point of failure.
- Server fingerprint — a summary of what the underlying stack looks like, useful context alongside the Technology Fingerprinting module.
What to do with this information
If the scan shows no CDN in front of a content-heavy or globally-visited site, that's a straightforward performance win available: moving static assets behind a CDN typically improves load times for visitors far from your server's physical location, and adds a layer of protection against traffic spikes.