Public signal checker
Website Infrastructure Checker
This checker groups public infrastructure clues so owners and agencies can see how a site is reached, served and routed.
The check uses public live signals and does not make a security, malware, fraud or legal verdict.
Run a public signal check
- HTTP
- DNS
- TLS
- RDAP
- Archive
What this checker analyzes
- Public A, AAAA and nameserver records.
- Server and infrastructure headers such as CDN or platform markers.
- HTML size, response content type and public hosting hints.
Why it matters
- Infrastructure signals explain availability, performance and ownership handoff questions.
- They also help separate first-party setup issues from CDN, DNS or hosting-provider behavior.
What the results mean
- Hosting and CDN hints are shown as public clues, not proof of ownership.
- DNS records are live responses and can differ by resolver, region or time.
- Server headers may be intentionally hidden or replaced by a proxy.
Limits of this check
- The checker does not scan ports or internal networks.
- It does not bypass CDN protection, authentication or geo-specific routing.
- It does not store infrastructure snapshots over time.
What should also be reviewed manually?
Review notable values in the context of the actual website, its subpages and connected services. A homepage check cannot prove the complete configuration, legal position or security posture.
FAQ
Does an infrastructure hint prove where a site is hosted?
No. A CDN or proxy can hide the origin. Treat the hint as context for a technical review.