Use the proxy checker with a specific question
A proxy checker helps explain why an IP address appears in a network list. It does not look inside your device, read your VPN settings or prove how every application connects. Start with the address that matters to your question, then compare the separate observations instead of treating one label as a final verdict.
Read more
Enter one public IPv4 or IPv6 address in the proxy checker. Do not add a URL, port number, subnet prefix or domain name. Private, loopback and documentation addresses cannot identify a public exit and are rejected. If you have a hostname, resolve it with hostname lookup first and inspect the relevant returned address.
Choose Use my IP to fill the address this site observes. That action does not run the proxy checker automatically. Read the disclosure, then choose Check sources. An address observed by this site can differ from the address used by another destination, another browser, an application or a separate IPv6 connection.
The proxy checker sends the chosen address to this site's lookup service. Source providers receive downloads of their public catalogs, without your entered address in those requests. This tool does not connect to the target, test its proxy ports or send traffic through a listed server. Looking up an address is distinct from probing it.
Four cards cover VPN networks, broader datacenter/VPN networks, published proxies and Tor exit observations. Overlapping categories can match together, but a range association does not prove present use.
If a lookup takes too long, use Stop. The proxy checker discards the pending report; a later response cannot restore it. Shared source refreshes may finish independently because other lookups can use that public data. Clear removes the address and report, and editing the input invalidates evidence for the previous address.
Read each proxy checker result on its own
Listed evidence found means an address or containing network matched the named usable snapshot. A network range, connection endpoint and observed exit are different evidence roles. Read the matching value before interpreting it.
Read more
No listing in this snapshot means the proxy checker searched usable data for a supported address family and did not find a match. It is a limited negative result. New services, private tunnels, residential relays and recently reassigned addresses may be absent. Avoid translating this status into “definitely residential,” “not a VPN” or “safe.”
Address family not covered means that source has no corresponding family data. It says nothing about whether IPv6 connectivity works. Source unavailable means no usable current data could be obtained; neither state counts as a negative match.
Snapshot too old to classify retains earlier data for context while withholding a current verdict. A recently downloaded file can still contain old observations. Within the age limit, a failed refresh can use the prior snapshot with a visible notice.
What the four sources actually describe
VPN networks come from X4B’s network list. Its netblocks are not an inventory of every active tunnel endpoint. The broader datacenter file includes VPN and hosting networks together, rather than a separate hosting-only diagnosis.
monosans observations distinguish a proxy’s connection endpoint from its observed exit. Those addresses can differ; the matched role is retained rather than silently exchanged.
Onionoo supplies IPv4 addresses observed exiting from running Tor exit relays within the previous twenty-four hours. Relay listening addresses are not substituted. This integration has no corresponding IPv6 exit-membership verdict.
Source dates and update behavior
Published identifies the source version’s time; Downloaded identifies this site’s retrieval. GitHub files use the last data-changing commit and that exact revision. These dates are snapshot metadata, not individual-address test times.
Network snapshots refresh on demand at most hourly; proxy and Tor snapshots at most every fifteen minutes. Concurrent requests share refresh work. Invalid or partial source downloads cannot become empty negative results.
Classification stops for network snapshots older than seven days, proxy snapshots older than four hours and Tor snapshots older than six hours. These are operating limits, not publisher update promises.
Proxy checker limitations that affect interpretation
A proxy checker cannot prove the absence of a VPN. A privately operated tunnel may use an ordinary cloud server or residential connection without appearing on a public list. Even a commercial provider can add addresses before a catalog updates. The absence of a listing should narrow your investigation, not end it.
Read more
Shared exits complicate a proxy checker result. Carrier-grade NAT, company gateways, public Wi-Fi and commercial VPNs can put many users behind one address. A listing describes the address or its network, not the intent or identity of every user. Do not use a single match as evidence that someone committed misconduct.
If one destination sees an unexpected exit, use IP comparison for request evidence and this page for address classification. A listed proxy is not a recommendation to use it, and no connection test occurs here.