Free Proxy Checker & Tester
See which proxies work over IPv4 and IPv6, and where each one exits.
ColdProxy's free online proxy checker tests a whole list with no signup. It shows whether each proxy works over IPv4, IPv6 or both, its exit IP and that IP's country, region and city, or why it failed. It checks HTTP, HTTPS, SOCKS4 and SOCKS5 proxies, with or without a username and password.
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.
How to Use the Proxy Checker
Paste your proxies one per line, start the test, and read each proxy's IPv4 and IPv6 result as it arrives.
Paste your 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 the check
Click "Check proxies" to start. Longer lists run as automatic batches, and results update live as IPv4 and IPv6 checks finish for each proxy.
Read the results
Working proxies show the exit IP and location for each IP family that works; dead ones show why the check failed, such as a timeout or an invalid response.
To check a proxy from code or the command line, follow how to test a proxy.
What Our Proxy Checker Reveals
Each test shows which IP family works, what exit IP websites see, and where that exit IP is located.
IP Family Reachability
Shows whether the proxy works over IPv4, IPv6, or both, so you catch proxies that only work on one family. A failed status usually means the proxy is offline, blocked, or misconfigured.
Exit IP Address
Shows the IP address a destination server sees when a request goes through the proxy, for IPv4 and IPv6 separately.
Geographic Location
Reports the country, region, and city where each working exit IP is located. Useful for checking geo-targeting before running location-dependent tasks. Before a city-level job, read how accurate proxy location data is.
Failure Reason
Shows why a family failed, such as timed out, invalid response, or unavailable, so you can sort out unusable proxies quickly.
203.0.113.10:8080WorkingIPv4203.0.113.10Ashburn, Virginia, United StatesIPv62001:db8::10Ashburn, Virginia, United States198.51.100.7:3128FailedIPv4 and IPv6Timed out
When You Need a Proxy Checker
Check proxies before any job that depends on them working from the right place: scraping runs, price and ad checks, multi-account work, localized QA and rank tracking.
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
Give each account its own exit IP. Test the whole list and drop proxies that return the same exit IP. 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
Check that each proxy works and exits in the country you need before you route a social workflow through it. See how social media proxies fit your workflow.
SEO and SERP Tracking
Track rankings from the cities you target. The checker shows the city each exit IP is located in, so you can drop proxies that exit elsewhere. See SEO monitoring proxies, or how ColdProxy compares with other proxy providers.
Need reliable proxies for your next job?
Pay for speed with unlimited traffic, or buy a monthly GB pack, on a network with a 99.9% success rate for working proxy connections and exit IPs. Start from one hour on hourly plans, then check your new proxies here.
Choose from the four public plans
Start with the proxy type and billing model that matches your workflow.Not sure which plan fits?
Need a different speed or traffic allowance? Contact us through the channels on our website so we can assess whether a custom plan is possible. Contact us about a custom plan
Explore more free tools
Check your own connection, or test whether a website supports IPv6.
Proxy Checker: Frequently Asked Questions
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.
Paste your list and start the test: each working proxy shows its exit IP and location, and each dead one shows why it failed. Enter each proxy as HOST:PORT or HOST:PORT:USER:PASS, where HOST is an IP address or hostname. The checker sends a request through each proxy over IPv4 and over IPv6 and 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 an exit IP. Run your full list before production so you only deploy proxies that respond and exit from the location you expect.
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.
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.
Yes. Add socks5:// before the proxy, for example socks5://203.0.113.10:1080. The checker also accepts http://, https://, socks4://, socks4a:// and socks5h://. Lines without a prefix are tested as HTTP proxies, and the checker does not detect the protocol for you, so add the prefix that matches your proxy.
Yes. Every proxy is checked over IPv4 and IPv6 separately. When a check finishes, the result shows each family that works with its own exit IP and location; if neither works, it shows the reason for each.
Paste the proxy and start the test. For each family that works, the result shows the exit IP and the country, region and city it is located in. Compare them with the location your job needs before you run it.
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 tool submits your proxies in batches of up to 25 and runs the batches one after another. For each proxy, it sends a request through the proxy over IPv4 and over IPv6, then returns the exit IP plus country, region, and city for every working family. Results appear in real time as each family finishes.
The list you paste isn't saved or logged; it's used only to produce the result you see. To run the check, the checker sends the list, including any usernames and passwords, to our servers, as our Privacy Policy explains.
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 the checker cannot read is marked "Invalid proxy format" or "Unsupported protocol" and is not tested, and "Check did not finish" means the checker itself could not run the test, so run the check again. Common causes include expired proxies, blocked ports, or the proxy server being temporarily offline. The check runs from ColdProxy's servers, not from your device, so a proxy that accepts only allowlisted IP addresses shows as failed here even when it works from your own machine. If the proxy also accepts a username and password, check it here in HOST:PORT:USER:PASS form instead. Try testing again after a few minutes if you suspect a temporary issue. If a ColdProxy proxy still fails, message support on Telegram or open a ticket; support is 24/7 in English and Arabic.