Small utilities for working with proxies. They run in your browser or call our own API, and nothing is stored.
Tell us about your project and we will suggest the right setup.
These free proxy tools answer the questions that come up in the first hour with a new proxy: which address a website sees, how long a request to our API takes, whether a proxy list fits the layout your tool expects, and what your browser tells a page. Each tool opens in the browser, needs no installation and answers on the spot.
Only the IP checker and the latency test call our API, and neither stores your results. The converter and browser info work inside your browser, which matters when a proxy list contains passwords. How request logs are handled is explained in the Privacy Policy.
Run the IP checker twice to see what a proxy changes. First open it in a normal browser window. Then open it again in the browser or tool you have pointed at the proxy. The second run should show the proxy's address and the country you chose. If it shows your own, the traffic is not going through the proxy. The result also lists your browser language and time zone. Test in the same program or script that will do the work, because a script and a browser can take different routes. The guide to using mobile proxies covers this step in full.
The latency test makes six quick requests and reports the lowest, median and highest time in milliseconds. Compare the median, because one slow request says little. Run the test from the machine or region where your jobs will run, since distance and local network quality show up in the numbers. If the browser is set to use a proxy, the result includes that extra hop, so the test also works as a rough check of the proxy route. To see whether the service itself is healthy, open the status page.
Tools disagree about proxy formats. Some want host and port in separate fields, others one URL with the credentials inside. The converter rewrites a list into host:port:user:pass, user:pass@host:port, http://user:pass@host:port, socks5://user:pass@host:port or plain host:port. Enter one proxy per line, and the converter flags any line it cannot read. A Python script using requests expects a single URL such as http://user:pass@host:port, and the Python proxy tutorial shows where it goes.
Browser info is useful for localized testing and for support requests. It lists the language, time zone, screen size and similar details that a page can read, so you know what a site sees when you check regional content, and you can paste the details into a message to our team.
Use the free proxy tools in this order. Start with the converter if your list is not in the layout your tool expects. Enter the proxy in your browser or script, then open the IP checker; the address it shows should belong to the proxy. Run the latency test next and note the median. If something fails, check the status page before changing your setup. There is no standalone proxy checker yet, so the IP checker is the way to confirm that a proxy is in use.
When you are ready to try mobile proxies, compare the plans and per-country prices or read the setup documentation.