AWS CloudFront Detector
Paste any URL and instantly see whether the site is built with AWS CloudFront — with the matched evidence.
We do not store the URL you audit. Want the full audit (performance / images / SEO / accessibility + real-browser speed test)? → run the full audit
Why check this
Confirm the platform first: Hosting & CDN decides what can be changed and whether it is worth it.
What this is
AWS CloudFront is Amazon’s CDN for enterprise sites and API edges. Confirming `x-amz-cf-id` or CloudFront tokens in Via headers shows whether cache behaviour, certificates and origin fetch match intent. Distribution headers tell you more about cache truth than an architecture slide ever will.
How to tell from a public page
- [CloudFront] Response headers include `x-amz-cf-id`.
- [CloudFront] The `via` header contains a CloudFront token.
- [CloudFront] Age/cache header combinations match typical distribution behaviour.
- [CloudFront] Error pages or custom responses leave distribution-config traces.
How to read the result
Confirm when distribution headers reproduce; an architecture diagram with a CDN icon does not qualify. Absence can mean another CDN wraps the distribution. Pasted sample HAR files can invent Via tokens. After a hit, verify TTL, compression and HTTP/3.
What to do next
Tune cache policy, enable compression, and compare with other edges such as Cloudflare — open Cloudflare detector. Holistic scoring returns via run the full performance / images / SEO / accessibility audit on the home page. Prefer distribution metrics over anecdotal slowness reports.
Related detectors
FAQ
How is AWS CloudFront detected?
From structural signatures in the public HTML and response headers (domains, paths, attributes, scripts). Every verdict lists how many times each pattern matched — nothing is guessed.
Can the result be wrong?
If only a bare brand keyword matches without structural evidence, we label it \u201clikely\u201d instead of \u201cconfirmed\u201d — we would rather under-report than cry wolf.
Do you save the URLs I check?
No. The audit runs inside the request and the URL you paste is not written to storage. There are no third-party tracking scripts on the page either, so no log of who checked what exists. Copy the result yourself if you want a record.
Can a website hide what it is built with?
Partly, but rarely completely. The HTML sent to your browser, the response headers, script paths and asset structure have to be exposed to work, so there is always something readable. Server-side code, build config and private APIs stay invisible. That is why this tool reports the evidence it found rather than claiming a full picture. No match does not mean the technology is absent.
Optimization help is available
Tell me your URL and what you want fixed — you get a clear scope, price and timeline.
To：[email protected] | Cc：[email protected]
