Free Proxy Checker & Tester
Check proxies in bulk with a free proxy checker and tester. See whether each one reaches IPv4, IPv6, or both, the exit IP it shows, and where that IP is located — so you can validate proxy lists before production.
Bulk Proxy Testing
IPv4 and IPv6 checks
Structured location output
What is a proxy checker?
A proxy checker — also called a proxy tester or proxy list checker — tests whether a proxy works: whether it reaches IPv4, IPv6, or both, what exit IP it shows, and where that IP is located. Use it to check proxies in bulk before scraping, QA, ad verification, or account work so you do not waste time on dead or misrouted proxies.
Best for
Bulk checking proxy lists before you put them into a live workflow.
What you enter
One or more proxies, one per line, as HOST:PORT, HOST:PORT:USER:PASS, or USER:PASS@HOST:PORT, where HOST is an IP address or hostname.
What you get
IPv4/IPv6 working status, exit IP, country, region, city, and any failure reason.
People also search for this page as a proxy tester, proxy list checker, or bulk proxy checker.
How to Use the Proxy Checker
Enter Proxies
Paste your proxy list, one proxy per line. Use HOST:PORT with an IP address or hostname, and add USER:PASS for authenticated proxies.
Start Testing
Click "Begin Test" to start the test. Longer lists run as automatic batches, and results update live as IPv4 and IPv6 checks finish for each proxy.
View Results
See real-time results with separate IPv4 and IPv6 outcomes, exit IPs, and structured country, region, and city fields.
What Our Proxy Checker Reveals
Each test shows which IP family works, what exit IP the target sees, and where that exit IP is located.
Connection Status
Confirms whether the proxy responds to requests. A working proxy returns data from the target server. A failed status usually means the proxy is offline, blocked, or misconfigured.
IP Family Reachability
Shows whether the proxy reaches the IPv4 endpoint, the IPv6 endpoint, or both. This helps you catch proxies that only work on one family.
Exit IP Address
Shows the IP address the destination server sees when your request goes through the proxy. Confirm it is the proxy's exit IP, not your own.
Geographic Location
Reports the country and city where the proxy exit IP is located. Useful for confirming geo-targeting accuracy before running location-dependent tasks.
Response Details
Shows the failure reason, such as timed out, invalid response, or unavailable, when a family does not work. This helps you diagnose unusable proxies quickly.
Want to see the IP a site sees for you? Check your visible address with our IP Checker tool, or test IPv6 support with our IPv6 Checker.
When You Need a Proxy Checker
Testing proxies before production saves hours of debugging. Here are the cases where running a quick bulk check matters most.
Web Scraping at Scale
Dead or misrouted proxies break scraping jobs mid-run. Validate your whole list first, then deploy only the working ones. Read our guide on proxies for web scraping.
Price Monitoring and Ad Verification
Location accuracy matters when you verify local pricing or check geo-targeted ads. Confirm the exit country before you run the job. See price monitoring proxies.
Multi-Account Management
Each account needs a stable, unique IP. Test every proxy and drop the ones that share exit nodes. Learn more about multi-accounting proxies.
QA and Localization Checks
When a localized test depends on a specific exit country, a dead or wrong-region proxy creates noisy results. Check the exit IP and location before a full QA pass.
Social Media Automation
Stable residential IPs support separated account operations. Validate proxy health before routing a workflow. See how social media proxies fit your workflow.
SEO and SERP Tracking
Track rankings from specific cities with controlled request volume. The checker confirms each proxy exits from the city you need. Compare proxy providers for the best SEO setup.
Why Use This Proxy Checker & Tester?
Our proxy checker focuses on the details teams actually need before production: does the proxy connect, which IP family works, what exit IP appears, and where that IP is located.
- Batch JobsBatch testing of proxy lists
- Broad Proxy InputAccepts plain and authenticated proxy entries
- Structured Location OutputShows IP address, country, region, and city for each working family
- IPv4 and IPv6 ChecksSee whether the proxy works on IPv4, IPv6, or both
- 100% FreeNo registration required, no software to install
Choose a plan after testing proxy output
After testing your connection, compare ColdProxy plans, pricing, and common workflow examples.
Choose from the four public plans
Start with the proxy type and billing model that matches your workflow.Compare pricing and test proxy output
Compare billing options, then test the connection and confirm exit IP and location.Common workflow examples
These are examples. The use-case hub shows more supported workflows.Need a tailored plan or volume pricing? Contact sales.
Proxy Checker: Frequently Asked Questions
To check if a proxy is working, paste it as HOST:PORT or HOST:PORT:USER:PASS, where HOST is an IP address or hostname, and start the test. The proxy checker runs a batch job that sends a request through each proxy to an IPv4 reflection endpoint and an IPv6 reflection endpoint, then reports the result for each family live. A working proxy returns the exit IP that the destination server sees, along with its country, region, and city. If a proxy is dead, expired, blocked, or misconfigured, the matching IPv4 or IPv6 family is marked as failed with a reason such as timeout or invalid response. A proxy is healthy when at least one family returns a successful reachability result with an exit IP. Run your full list before production so you only deploy proxies that respond and exit from the location you expect.
The tool submits your proxies in batches of up to 25 and runs the batches one after another. For each proxy, it checks an IPv4 reflection endpoint and an IPv6 reflection endpoint, then returns the exit IP plus country, region, and city for every working family. Results appear in real time as each family finishes.
Yes. Enter authenticated proxies in HOST:PORT:USERNAME:PASSWORD or USERNAME:PASSWORD@HOST:PORT format, one per line, where HOST is an IP address or hostname. If your password contains a colon, use the USERNAME:PASSWORD@HOST:PORT form. The checker sends your credentials with each test, and wrong credentials show as a failed check.
Paste your full list, one proxy per line - there is no overall limit. The checker automatically splits the list into batches of up to 25 proxies, runs them one after another, and updates results live as the IPv4 and IPv6 checks finish for each one.
A failed result means neither the IPv4 nor the IPv6 check got an exit IP through the proxy. The proxy may have timed out, refused the connection, rejected the username and password, or sent an invalid response; refused connections, wrong credentials and other errors without a more specific reason show as "Unavailable". A line with an unsupported protocol prefix or a format the checker does not accept is marked "Invalid proxy format" and is not tested. Common causes include expired proxies, blocked ports, or the proxy server being temporarily offline. Try testing again after a few minutes if you suspect a temporary issue.
Yes. The proxy checker is completely free with no registration and no feature restrictions. It works in any modern browser with no software to install.
Each result shows whether the proxy reaches IPv4, IPv6, or both, the exit IP for each working family, and structured country, region, and city data. Failed families show the reason, such as "Timed out", "Invalid response", or "Unavailable".
The checker sends your proxy list, including any usernames and passwords, to our servers to run the test. As our Privacy Policy states, we use each request only to produce the result you see.