> For the complete documentation index, see [llms.txt](https://docs.ipcheck.ing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ipcheck.ing/knowledge-base/connection-tools/invisibility-test.md). # Invisibility Test {% hint style="warning" %} **Available on IPCheck.ing only** — this feature is not included in self-hosted deployments. {% endhint %} ## What it does When you use a proxy or VPN, do the sites you visit really not know? The **Invisibility Test** answers that from the other side of the table. Instead of asking "what is my IP", it runs the same kinds of checks a website would run to catch you. It looks at your address, your HTTP headers, your timing, your timezone, and how your connection behaves — then reports how much evidence it found that you are using a proxy or a VPN. As the app puts it: some results may not be completely accurate, but the test is still highly informative. ## How to run it The tool lives in **Advanced Tools → Invisibility Test**. You must be signed in to use it. {% stepper %} {% step %} ### Tick the consent box The test collects your IP information, browser information and similar data, and analyses it in the background. Tick **I agree** to allow that. The run button stays disabled until you do. {% endstep %} {% step %} ### Press Run A script runs in your browser and probes your connection. It usually finishes within about ten seconds. {% endstep %} {% step %} ### Read the summary, then the details Results appear as a summary card followed by an itemised list. {% endstep %} {% endstepper %} ## Reading your results ### The summary card At the top you get the address the test used (*"Your main test IP is"*) and two percentages: * **Proxy Percentage** — how much evidence points to a proxy. * **VPN Percentage** — how much evidence points to a VPN. Each score is colour-coded, and a plain-language verdict appears underneath. | Score | Colour | Verdict shown | | ------------- | ------ | ----------------------------------------------------------------------- | | Below 30% | Green | Little to no evidence found | | 30% to 69% | Amber | Mixed signals | | 50% and above | — | *"You may be using a proxy."* / *"You may be using a VPN."* | | Below 50% | — | *"No evidence of you using a proxy was found."* / *"…a VPN was found."* | | 70% and above | Red | Strong evidence | The verdict sentence flips at 50%. The colour changes at 30% and 70%, so an amber score can still read as "no evidence found" — treat that as borderline rather than clean. ### The detail list Below the summary, fourteen individual checks are listed. A green check means the item found nothing; a red cross means it flagged you. | Check | What it looks at | | ------------------------ | -------------------------------------------------------------------------------- | | HTTP Headers | Whether your requests carry headers that announce a proxy | | Datacenter IP | Whether your address belongs to a hosting provider rather than a home connection | | Proxy List | Whether your address appears on a known-proxy list | | VPN List | Whether your address appears on a known-VPN list | | VPN Exit Node List | Whether your address is a known VPN exit node | | TOR Exit Node | Whether your address is a known Tor exit node | | TCP Fingerprint | Whether the operating system your connection looks like matches your actual one | | TCP vs Ping Latency | Whether those two timings disagree by an unusual amount | | TCP vs WebSocket Latency | The same comparison, against WebSocket timing | | Timezone Difference | Whether your device's timezone matches your address's timezone | | Network Behavior | Behavioural signals from your client | | WebRTC Detection | Whether WebRTC exposed addresses from more than one region | | Traffic Characteristics | Signals in your TCP/IP traffic | | High Latency Analysis | Whether your latency profile looks like tunnelled traffic | Flagged items often show the evidence inline — your timezone against the address's timezone, your operating system against the one your connection looks like, the two latency numbers, or the extra addresses WebRTC produced. ### What a good result looks like It depends on what you want. * **You want to be invisible.** Aim for low scores and few red crosses. Items like *Datacenter IP*, *VPN List* and *Timezone Difference* are the ones commercial VPNs trip most often. * **You just want a working VPN.** High scores are fine. They only mean sites *can* tell you use a VPN, not that your VPN is failing. For that question, use [Is My VPN or Proxy Working?](/knowledge-base/diagnose/is-my-vpn-working.md). {% hint style="info" %} A red cross is a signal, not a verdict. Some checks flag ordinary setups: corporate networks look like datacenters, and travellers often show a timezone mismatch. {% endhint %} ### If the test fails | Message | What to do | | -------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | | `The test script failed to load, so the test cannot continue.` | Something on your network or an extension blocked the probe script. Pause your content blocker and try again | | `Unable to fetch test results` | The results were not ready in time. Run the test again | | `Please sign in to use` | Sign in first; the test is only available to signed-in users | ## What to do next * Fix a WebRTC cross with the [WebRTC Test](/knowledge-base/connection-tools/webrtc-test.md). * Fix a DNS-related exposure with the [DNS Leak Test](/knowledge-base/connection-tools/dns-leak-test.md). * Reduce the fingerprint side of your exposure: [Browser Fingerprint](/knowledge-base/lookup-privacy/browser-fingerprint.md) and [Browser Fingerprinting Explained](/knowledge-base/concepts/browser-fingerprinting.md). * Work through the [Security Checklist](/knowledge-base/lookup-privacy/security-checklist.md) for the wider picture. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.ipcheck.ing/knowledge-base/connection-tools/invisibility-test.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.