ToDetect provides public pages for IP lookup and browser-network checks. Use them to collect observations, not as a guarantee of privacy, account safety or acceptance by another service.

Before you start

Have the connection details required by the selected product and intended proxy client. Keep any credentials inside that client. A public IP lookup field should receive only an IP address, never a proxy password or customer information.

Decide which of these two questions you are answering:

  • What do public databases report for a known exit IP? Use the IP lookup page.
  • Is this browser profile actually presenting the expected exit and network behavior? Configure the proxy in that profile and test from it.

Method 1: Inspect a known exit IP

Open the ToDetect IP lookup page and enter the exit IP you want to inspect. Compare the reported location and network details with your order. This lookup describes the IP you entered; it does not prove that your browser is using that proxy.

Record the test time, entered IP and the relevant location, ISP, ASN or IP-type fields. Treat these as one provider’s current observations.

Method 2: Inspect the configured browser

  1. Configure the KiloProxy proxy in the browser profile or supported client you intend to test.
  2. In that same profile, open the ToDetect homepage.
  3. Review the visible exit and compare it with the expected connection.
  4. If the result is unexpected, recheck the client’s proxy mode and authentication fields before changing the product.

Testing in another unconfigured browser does not verify the original profile.

Check DNS and WebRTC surfaces

Open the ToDetect DNS leak page and ToDetect WebRTC page in the same configured browser profile. Review unexpected network exposure as a diagnostic clue.

A particular score or “not detected” message is not a complete privacy guarantee. Results can depend on the browser, operating system, extensions, proxy mode and test implementation.

Record and interpret the result

Keep a timestamp and the specific fields that matter to the order. If a database classification differs, compare another source and the actual authorized task before drawing a conclusion. Do not average unrelated scores or treat a label as proof of physical network deployment.

If the observed exit or key order fields remain materially inconsistent after configuration checks, save non-sensitive evidence and contact support. For a fuller decision method, read proxy IP reputation and risk checks.

FAQ

Can I paste my proxy username and password into ToDetect’s IP lookup?
No. Enter only the exit IP in a public lookup field. Keep proxy credentials in the intended client.
Does an IP lookup prove my browser uses the proxy?
No. It describes the IP you entered. To inspect the browser connection, open the test in the same browser profile after configuring the proxy.
Does a DNS or WebRTC result guarantee complete privacy?
No. It is one observation from one test surface. Review the full client and network configuration for the intended task.
What if the reported location differs from my order?
Recheck that the intended proxy is active, record the exit and timestamp, compare relevant sources and contact support with non-sensitive evidence if the mismatch remains.

Need to select a fixed or rotating service before testing? Compare KiloProxy proxy services.