Know what a checker sees before you paste in a proxy, and how to test without exposing your own address.
Any checker site, ping0 included, sees the address your connection arrives from, the headers your browser sends, and whatever its page scripts can read from the browser. If the proxy is set up correctly, the address is the proxy exit, not your home IP. If something goes around the proxy, such as a WebRTC request or a second app, the site can see the other address too.
Whether a particular site keeps those details is something you cannot verify from outside. We could not read any privacy statement for ping0.cc (the policy we found belongs to ping0.xyz, a different domain), so plan as if a checker may log what it sees, and test in a way that makes that harmless.
| Item | Can it see this? | Why |
|---|---|---|
| Address the connection comes from | Yes | It is the source of the request: the proxy exit if the browser uses the proxy, your own IP if it does not. |
| Browser details (language, time zone, screen size) | Yes, through page scripts | A checker page can read them like any web page. Mismatches with the IP location are what such tools flag. |
| WebRTC addresses | Possibly | WebRTC asks a STUN server for the address it is reachable on from outside; depending on browser and network this can differ from the proxy exit. Test it on its own. |
| Proxy username and password | Normally no | They go to the proxy server to authenticate, not to the sites you open through it. Do not type them into any web form. |
| Other tabs, other apps, files | No | A web page cannot read them. Other apps that do not use the proxy simply connect from your real address. |
Based on how HTTP proxies and browsers work and on the MDN description of STUN candidates (read 13 November 2026). The policy of ping0.xyz, a different domain, lists IP, browser, OS, screen, time zone and fingerprints as collected data.
Open a fresh browser profile with no logins, saved passwords or account cookies. Do not test in the profile you use for real accounts.
Run curl through the proxy (below). This shows the exit IP without a browser, so no page script and no WebRTC are involved.
Expected result The response shows the proxy country and network, not your own.
Open the checker only after the browser is set to the proxy. Compare its IP with the curl result.
Expected result Both show the same exit address.
If the page shows a second public address, or a time zone and language that do not match the exit country, fix those before using the profile for anything else.
Expected result No second address, and the time zone matches the exit location.
Never log in to an account or paste proxy credentials on a checker page. Close the profile when done.
Before continuing A checker only needs the connection, not your passwords.
# HTTP proxy
curl -x http://LOGIN:PASSWORD@HOST:PORT https://ipinfo.io/json
# SOCKS5, DNS also resolved through the proxy
curl -x socks5h://LOGIN:PASSWORD@HOST:PORT https://ipinfo.io/jsonExample only: replace LOGIN, PASSWORD, HOST and PORT with your own values.
Check Is the browser really using the proxy? Look at the system proxy settings, extensions and any VPN or second proxy app running on the same computer.
Fix Fix the proxy setting, restart the browser, repeat step 3. If curl shows the proxy IP but the browser does not, the browser is not using it.
Stop when If curl itself shows your real IP, the proxy address or port is wrong; see the connection guide.
Check Open the WebRTC test and read which address is listed.
Fix Follow the WebRTC guide; do not use the profile for accounts until only the exit address appears.
Check Is the host, port and protocol right? HTTP uses port 2222 and SOCKS5 uses 3333 on proxy.proxy302.com.
Fix Re-copy the values and test with curl; the connection guide lists the checks in order.
Stop when If curl also times out, the problem is the proxy or the network, not the checker.
Open My assets and copy HOST, PORT, USERNAME and PASSWORD of the IP. The protocol is shown with the asset: HTTP uses port 2222, SOCKS5 uses port 3333.
Run the curl command above and look at the country and network in the answer.
Open the IP purity check page through the proxy to see network type, native or broadcast, time zone and WebRTC in one place.
Testing the exit IP is low risk if you use a clean profile and never enter logins or credentials. We could not read a privacy statement for ping0.cc, so assume a checker may log the IP and browser details it sees.
A site only sees your real IP if something connects to it without going through the proxy, for example a WebRTC request or another app. Run the curl check and the WebRTC test to see which address is exposed.
No, they are different domains. The privacy policy we could read belongs to ping0.xyz, so it should not be treated as a statement about ping0.cc.
Normally not: the password is sent to the proxy to authenticate. The risk is typing it into a web page yourself, so never do that.
Use curl for the exit IP, then one or two public checkers for network type and location. When they disagree, the checkers guide explains why.
Test your IP as soon as the page opens: network type, native or broadcast, the SpamCop blacklist, time zone, language and WebRTC, plus how to read each result.
IDC, broadcast, native and home broadband on ping0.cc: usual meanings and a 5-step way to confirm them.
Test as soon as the page opens whether WebRTC exposes a public IP other than the one websites see, and how to fix it in AdsPower, Chrome and Firefox.
Check the exit IP, country and ISP your proxy really gives you in 30 seconds — and why IP databases disagree on the city. With our own test of three lookup services.
Five IP checkers, five different things measured: how to compare them in 5 steps before you buy.
Official documentation · Confirmed on:
Read on 13 November 2026: a STUN server returns a "server reflexive" candidate, an address reachable from outside the local network; the page gives no privacy advice.
Third-party source · Confirmed on:
Read on 13 November 2026: the policy of ping0.xyz, last updated November 2025, lists IP addresses queried, browser type, operating system, screen resolution, time zone and device fingerprints (canvas, WebGL) as collected data, and says data is kept as long as necessary.
This is another domain. We found no privacy policy for ping0.cc.
Third-party source · Confirmed on:
Opened ping0.cc with a page reader on 13 November 2026: no readable content came back, and a web search found no official statement on what the site stores. This guide therefore makes no claim about what ping0.cc logs.
Product observation · Confirmed on:
Product facts file of the site, checked 13 November 2026: HTTP port 2222 and SOCKS5 port 3333 on proxy.proxy302.com, static IP prices, no free trial.
Create an account, top up once, then pick rotating residential, static ISP or datacenter IPs and have one running in your browser within minutes.
