Donate
Donate

Proxy Check

Understand common proxy signals and why detection isn't always perfect
Lily's route guide

Treat proxy signals as clues, not proof

Proxy detection combines network ownership, reverse DNS, Tor, and request-header clues. Confirm the route with leak checks and ASN context before deciding what the result means.

Run the VPN checksCheck the ASN
Lily inspecting a network route for a proxy or VPN gateway

How proxy detection works

Proxy checks look for signals such as hosting , suspicious patterns, or proxy/VPN ranges. These are best-effort indicators, not definitive proof.

Common signals

  • Hosting provider or data center
  • keywords (vpn, proxy, exit, cloud)
  • Shared gateways or carrier NAT ()

Proxy detection is not exact. Many checks rely on indirect signals (reverse DNS, network classification, routing behavior, and request headers). Depending on the network you're on, some tests can produce false positives, especially when an IP belongs to a shared gateway, corporate network, or mobile carrier.

If you're using a proxy or VPN and it wasn't detected, it may simply mean there were no obvious signals available. Detection methods also change over time.

If your goal is privacy on public Wi-Fi, a VPN is usually safer than a proxy. See VPN vs Proxy for a quick comparison.

To test a different IP address, use the IP location lookup.

Related: ASN, CGNAT, and ASN in networking.

Finding the proxy check useful?

It is free with no sign-up. A small contribution helps keep this tool running and the troubleshooting guides current.

Support this tool

Reading proxy detection signals correctly

Proxy detection combines several heuristics. No single signal is definitive. Here is how to interpret the most common ones:

  • Hosting/data center ASN: the IP belongs to a cloud or hosting provider (AWS, DigitalOcean, OVH, etc.) rather than a residential ISP. Most VPNs and proxies route through hosting ASNs. Check with ASN lookup.
  • Reverse DNS keywords: PTR records containing “vpn”, “proxy”, “exit”, “node”, or “cloud” suggest the IP is part of a privacy or hosting network. Verify with reverse DNS lookup.
  • Known Tor exit node: the IP appears on the public Tor exit relay list. This is a strong signal but only applies to Tor traffic.
  • HTTP header anomalies: forwarding headers like X-Forwarded-For or Via can reveal intermediate proxies, though many modern proxies strip these.
  • Port scan patterns: open SOCKS or HTTP proxy ports (1080, 3128, 8080) suggest the IP is running a proxy service. Not always accurate for residential connections with custom services.

False positives are common. Corporate VPNs, mobile carriers with , and shared business gateways can trigger proxy signals without any proxy being involved.

Dig deeper into each signal

What to do next after proxy detection

Proxy/VPN signals are best-effort hints. Validate IP, ASN, and leak behavior before acting on one result.

1Next step
Baseline

Check your public IP and ISP

Confirm what websites see, then compare ISP/provider context to avoid misreading proxy-like signals.

Open IP checker
2Next step
Routing context

Verify ASN ownership

Hosting, carrier, and enterprise ASNs can look like proxies. ASN data helps explain many false positives.

Check ASN
3Next step
Hostname signal

Inspect reverse DNS (PTR)

PTR hostnames can reveal provider patterns used by proxy detection checks.

Run reverse DNS
4Next step
VPN workflow

Run the VPN verification wizard

If you are testing a VPN, combine proxy detection with IP, DNS, and WebRTC checks in one guided flow.

Open wizard

Related Articles

VPN vs Proxy: Privacy, Speed, and Which to Use14 min read • August 1, 2026What Is a Proxy Server? Privacy, Security, and Use Cases7 min read • January 9, 2026Are Free Proxies Safe? Risks, Red Flags, and Better Options6 min read • January 9, 2026What is Tor?6 min read • January 9, 2026What Is My ISP? How to Check Your Internet Provider and ASN15 min read • February 9, 2026What Is a DNSBL? Email Blacklist Basics and Lookup Checks6 min read • January 9, 2026

Frequently asked questions

How accurate is proxy detection?
Proxy detection is not perfectly accurate. Many methods rely on indirect signals (headers, reverse DNS, network classification), so false positives and false negatives can happen.
Why can a mobile or corporate network look like a proxy?
Large networks often route many users through shared gateways and carrier NAT. That shared infrastructure can resemble proxy-like behavior to some detection checks.
If this tool says "not a proxy", am I safe?
No. "Not a proxy" only means the tool did not find strong signals. It does not guarantee an IP is residential or that a VPN/proxy is not in use.
Can reverse DNS reveal VPN or proxy usage?
Sometimes. Some providers use recognizable hostnames in PTR records, but many do not. Reverse DNS can help interpret results but is not definitive.
What should I do if I get a false positive?
Try testing from a different network, reboot your router to get a new IP (if your ISP rotates), and compare results with IP/ASN details and reverse DNS.
Why do proxy detection tools sometimes disagree?
Each tool uses different signals, update schedules, and risk thresholds. One service may classify a shared gateway, cloud range, or newly reassigned IP differently from another, so important decisions should use several checks.