Free proxy checker

Paste your proxies to see whether each one works, which IP address and location websites will see, what kind of network it is, and, if it fails, why, with a link to the guide that fixes it. Every proxy is tested against ipvolt's own endpoint, never against another site.

Free proxy checker

Formats: host:port, host:port:user:pass, user:pass@host:port or scheme://user:pass@host:port, with http, https, socks5 or socks5h. Up to 50 proxies per check.

What each result means

  • Status

    Works: an HTTPS request through the proxy reached ipvolt's endpoint and ipvolt's certificate verified. HTTP only: HTTPS failed but a plain-HTTP request got through. Failed: neither did. Not checked: the address or port is not a public proxy, so no connection was made.

  • Exit IP

    The address ipvolt's endpoint saw the request come from. Websites see this address, not yours. If plain HTTP leaves from a different address, both are shown.

  • Location

    Country and city for the exit IP from two independent geolocation databases. When they disagree, the row says so; neither is a measurement of where the device is.

  • ASN and network type

    The network that announces the exit IP. The type (hosting, mobile carrier, internet provider) is an estimate from that network's ASN, not a test of the device.

  • IPv6

    Yes when the proxy could reach ipvolt's IPv6 address. No means it could not, or refused to, from this exit.

  • Latency

    Milliseconds from ipvolt's server: TCP connect to the proxy, the tunnel (CONNECT or SOCKS5) handshake, TLS to ipvolt's endpoint through it, and the total. Your own location adds its own latency.

  • Headers

    Headers the proxy added to a plain-HTTP request, such as Via, X-Forwarded-For or Forwarded. If one contains the checker's own address, the proxy reveals its user's IP to websites.

  • Details

    For a failure: the step that failed, the proxy's status code when it sent one, and a one-sentence cause with a guide. Causes marked Likely are inferences; the rest are what the proxy actually answered.

Guides for common failures

What the checker stores

  • Proxy passwords are used only to connect to your proxy during the check. They are never logged, stored or sent back: results show user:****.
  • Proxy addresses and exit IPs are not logged. The service records only how many proxies were checked and which failure types occurred.
  • Rate limits keep a keyed hash of your IP address for the length of the limit window (up to one hour), in memory only.
  • The checker only connects to the proxies you enter and, through them, to ipvolt's own endpoint at check.ipvolt.com. It never tests against another website.
Privacy policy

Questions

Which site does the checker test against?

Only ipvolt's own endpoint, check.ipvolt.com. Each proxy is asked to open an HTTPS connection to it, and one plain-HTTP request is sent to see headers the proxy adds. You cannot choose another destination.

Does a working result mean the proxy works on every site?

No. It means the proxy accepted your login, opened a tunnel and delivered an intact HTTPS response from ipvolt's endpoint. A particular site can still block the exit IP or rate-limit it.

Why is the network type an estimate?

It comes from the ASN that announces the exit IP. Many carriers serve mobile and home lines from the same ASN, and the ASN cannot tell which one a request used.

Why do the two location databases disagree?

They are built from different sources and update on different schedules. Mobile and recently moved addresses often differ. Disagreement is shown rather than hidden.

What is the difference between socks5 and socks5h?

With socks5, the hostname is resolved on your side and the proxy receives an IP address. With socks5h, the proxy resolves it. Auto-detect tries socks5h first and falls back to socks5 if the server refuses hostnames.

Are my proxy passwords stored?

No. They are used for the check and discarded. Results, CSV exports and logs never contain them.

Need a proxy that passes? Mobile proxies from $9/day. See pricing