osintverse-community/cdncheck
Tells whether an IP or host is behind a CDN, cloud provider or WAF, and which one
→ finds other
No key · Docker
No key · Docker
Verified publisher
Tell a CDN edge from the real server
4 tools. 4 run with ot in a sandbox on Windows, macOS and Linux. Compare them side by side ↓
Many sites sit behind a CDN or a web application firewall, so the address their domain resolves to belongs to Cloudflare, Akamai or a cloud provider, not to the owner. Before you look up an IP's owner, ports or neighbours, find out whether it is an edge: these tools say which CDN, cloud or WAF an address or host belongs to, and filter lists of IPs down to the ones that may be origin servers.
With ot, in a sandbox
All IP address tools →Windows, macOS and Linux, with Docker or Podman. Each tool runs in a read-only container that can reach only the sites it declares, and every result comes back in the same JSON shape.
osintverse-community/cut-cdn
Filters out IP addresses that belong to known CDN providers, leaving the ones that point at real origin servers
Takes ip address → finds ip
No key · Docker
No key · Docker
Verified publisher
osintverse-community/findcdn
Detects which CDN a domain uses from its DNS records, HTTP headers and IP ownership
Takes domain → finds ip, organization
No key · Docker
No key · Docker
Verified publisher
osintverse-community/httpx
Probes a host's web server: status, title, technologies, TLS, CDN and IP
Takes url → finds ip, other, url
No key · Docker
No key · Docker
Verified publisher
ot install osintverse-community/cdncheck osintverse-community/cut-cdn osintverse-community/findcdn osintverse-community/httpxInstalls the first 4 in one go; ot auto ip:… then runs every installed tool that takes an IP address and saves the results. No ot yet? Install it in one line.
The 4 registry tools side by side
| osintverse-community/ | other | None | Online, passive | No | Docker | No reports yet | fewer than 10 |
| osintverse-community/ | ip | None | Online, passive | No | Docker | No reports yet | fewer than 10 |
| osintverse-community/ | ip, organization | None | Contacts the target | No | Docker | No reports yet | fewer than 10 |
| osintverse-community/ | ip, other, url | None | Contacts the target | No | Docker | No reports yet | fewer than 10 |
Facts from each tool's manifest and what people report about whether it works. "Reaches" says whether a run stays offline, reads public sources, sends requests about the target, or may notify them.
How to tell a CDN edge from the real server
- Check the address or host (cdncheck) to see whether it is a CDN, cloud or WAF edge, and which one.
- Filter a list of resolved IPs (cut-cdn) to keep the ones outside CDN ranges.
- Look for the origin elsewhere: old DNS records, subdomains that skip the CDN, and certificates or favicons shared with other hosts.
Every registry tool here runs on your machine in a sandbox, and ot auto ip:… runs all the installed ones on one value.
Before you run one
Can these tools find the origin server behind a CDN?
Not on their own. They tell you which addresses are edges so you stop investigating those; finding the origin takes other evidence, such as subdomains that resolve directly or historical DNS.
Does a CDN check contact the site?
cdncheck and cut-cdn compare addresses with published CDN and cloud ranges. findcdn and httpx also read the site's HTTP headers, so they send it a request; their rows say so.
Do these tools send my search anywhere?
No. ot runs each tool on your own machine in a read-only container that can only reach the sites the tool declares, and results stay in your results folder. The registry only counts installs.
Do I need an API key?
Most tools here work without one; the row says "Key required" when one is needed, and ot keys set stores it in your OS keychain so only that tool's container sees it.
More from an IP address
Owner and ASNDomains on itReputationOpen portsLocationAll IP address tools