Guide
Free Proxy Tools: Test, Verify and Route Your Connection
A free proxy toolkit for testing proxies in bulk, checking what your IP reveals, and routing desktop apps through proxies with profiles and split tunneling.
Most proxy problems are diagnosable in under a minute with the right tool, and spend hours undiagnosed without one. Is this proxy alive? Is my browser actually using it? Does this address geolocate where the provider claims? Which forty entries in this list of two hundred are dead?
The FlameProxies tools page collects free utilities for these questions. They are provider-agnostic — they work with any proxies, not only ours — and none require an account.
Proxy Tester
Paste a list of proxies and get back, per entry: whether it connects, whether authentication succeeds, latency, the exit IP, geolocation, ISP and ASN, connection type, and whether it leaks identifying headers.
The bulk aspect is what makes it useful. Checking one proxy is easy manually; checking two hundred is not, and the distribution across a large sample is where the interesting information lives. A pool whose addresses cluster into three ASNs behaves very differently from one spread across hundreds, and you only see that in aggregate.
Use it when: evaluating a provider during a trial, auditing an inherited list, onboarding a new geographic market, or isolating whether a drop in success rate came from your proxies or your targets.
What's My IP
Shows what your current connection reveals: exit address, geolocation down to city, ISP and organization, ASN, and how the address classifies — residential, datacenter, mobile, hosting.
The browser version answers "what am I presenting right now." There is also a curl-friendly endpoint at ipcheck.flameproxies.com for scripts:
curl -x "http://user:pass@gateway.flameproxies.com:8080" \
https://ipcheck.flameproxies.comThat one command is the fastest way to confirm a proxy configuration is actually applying. It is also the basis for a geo-verification gate — check the location at session start, discard sessions that landed in the wrong market, and wrong-market records never enter your dataset.
Use it when: verifying a new proxy setup, confirming targeting parameters resolve correctly, checking for leaks after a network interruption, or gating automated sessions on geographic accuracy.
Flame Proxy Connector
flameproxies.com/tools/flame-proxy-connector
A Windows desktop application that routes any program on your machine through proxies — including applications with no proxy support of their own. Functionally it is a VPN client with proxies behind it instead of VPN servers.
What it provides: rotating, sticky, or static modes with configurable rotation intervals; country and city selection across a thousand-plus cities; saved profiles you switch between; split tunneling to choose which applications are routed; a kill switch that blocks traffic rather than silently falling back to your real IP; and auto-connect on startup. Live stats show upload, download, latency, and the current exit IP.
It works with proxies from any provider. Connecting a FlameProxies account adds automatic plan sync with live bandwidth balances, full location targeting from the interface, native rotation control, and the advanced targeting dimensions described below.
Use it when: routing desktop applications that have no proxy settings, doing manual verification work across markets, accessing accounts from a consistent geographic IP, or testing how your own product behaves from another country.
Not the tool for: programmatic collection at volume. If your code accepts a proxy URL, use the gateway directly — you get per-request IP control and unlimited concurrent sessions, rather than funneling parallel work through one machine's tunnel.
New Targeting Dimensions
Three targeting options were added recently that go beyond the usual country and city selection, available through a FlameProxies account.
Operating system targeting selects IPs associated with a specific OS — Windows, macOS, Android, or iOS. Useful wherever platform changes what gets served: mobile-specific ad inventory, app-install campaigns, OS-gated content, or any test where the IP's device profile should match the client you are presenting.
ASN targeting selects IPs from a specific autonomous system — a particular ISP or carrier. Two applications. Precision, when you need to see what a customer on a specific network sees. And distribution control, which matters more at scale: because many targets aggregate reputation by network rather than by address, being able to steer toward or away from particular ASNs is a lever that per-IP rotation alone does not give you.
Region targeting selects by region group rather than by enumerating countries — tier-1 markets, EU, LATAM, and similar. At scale this collapses a lot of configuration. "EU traffic" becomes one parameter instead of a maintained country list you rotate through yourself, which is the right abstraction when the economic or regulatory region matters more than the specific country.
Which Tool for Which Question
| Question | Tool |
|---|---|
| Is this list of proxies usable? | Proxy Tester |
| What does my connection reveal right now? | What's My IP |
| Did my targeting parameters resolve correctly? | ipcheck endpoint |
| Is my browser actually using the proxy? | What's My IP |
| How do I route an app with no proxy settings? | Flame Proxy Connector |
| How do I verify geography inside a script? | ipcheck endpoint |
| Which of my proxies are leaking headers? | Proxy Tester |
| How do I switch markets without reconfiguring? | Connector profiles |
A Practical Sequence
Setting up a new proxy workflow, the tools fit together in a natural order:
- Test the proxies in bulk before building anything on them. Dead entries, wrong geolocation, and incorrect IP types are all cheaper to find now than in production.
- Verify a single connection end to end with the curl endpoint, confirming credentials, targeting syntax, and rotation behavior all work as expected.
- Build the geo-verification gate into your collection code using the same endpoint, so every session is checked before it collects.
- Use the connector for the manual and interactive parts of the work — spot checks, verification by hand, anything in a browser.
- Re-test periodically, because pool composition drifts and accuracy that was good at onboarding degrades quietly.
Steps 1 and 5 are the ones most often skipped, and they account for a disproportionate share of data quality problems that get blamed on something else.
All three tools are free and work with any provider's proxies. They are at flameproxies.com/tools if you want to try them against whatever you are currently running.