Anonymity Checker
Check your browser risk score, Device ID, VPN or proxy signals, and the evidence visible to a website.
Try changing something
Change one thing and check again. Compare your identifiers, connection and risk signals across visits. Rapid cookie resets can also surface as automation in the demo.
Clear your cookies
- 1.Clear cookies for this site, then check again.
- 2.The Cookie ID changes. Compare the Device ID and Visitor ID to see what remains recognizable.
Open a private window
- 1.Load this page in a private window and check.
- 2.Compare the new Cookie ID with the device and visitor results.
Turn on a VPN
- 1.Switch a VPN on, then check again.
- 2.Compare the IP address, location, network signals and Risk Score.
That was one visit. You can read every visit to your own site.
Same snippet, over an API and webhooks. 99.9% identification accuracy and 99.9% risk signal detection accuracy.
Frequently asked questions
- What does the Anonymity Checker test?
It runs the ShieldLabs snippet on your own visit and shows what a website can learn from it: a Risk Score from 0 to 100, the risk signals that fired (such as VPN, proxy, Tor, anti-detect browser, browser automation and timezone mismatch), your Device ID and Visitor ID, and your IP address, country and connection type.
- Can websites detect my VPN?
Often, yes. A VPN changes your IP address, but a website can still recognize a VPN connection or a mismatch between your browser time zone and IP location. ShieldLabs shows VPN, proxy, Tor and privacy relay as named signals. A VPN alone is not proof of abuse; the risk band depends on the full visit assessment.
- What is a Risk Score?
The Risk Score combines the risk signals on one visit into a number from 0 to 100, in three bands: Trusted (0 to 29), Suspicious (30 to 59) and Dangerous (60 to 100). A website reads the score and the named signals behind it to decide whether to allow an action, ask for verification, or stop it.
- Does incognito mode hide me from websites?
Not necessarily. Incognito mode starts without your regular cookies, so the Cookie ID changes. Device intelligence can still recognize a returning browser and connect activity across visits. Run the checker in a regular and a private window to compare the IDs and signals.
- Can an anti-detect browser be detected?
Yes. Anti-detect browsers change the fingerprint a website sees, and those changes leave traces a real browser does not. ShieldLabs raises the Anti-detect Browser signal, which weighs 60 and puts a visit in the Dangerous band on its own.
- Why is my Risk Score high?
Look at the risk signals on your result: each one names what raised the score, for example a VPN or proxy, a browser time zone that does not match your IP location, signs of browser automation, or an IP address with a history of abuse. Turning off a VPN or proxy, or using a regular browser without automation, usually brings the score down.
It runs the ShieldLabs snippet on your own visit and shows what a website can learn from it: a Risk Score from 0 to 100, the risk signals that fired (such as VPN, proxy, Tor, anti-detect browser, browser automation and timezone mismatch), your Device ID and Visitor ID, and your IP address, country and connection type.
Often, yes. A VPN changes your IP address, but a website can still recognize a VPN connection or a mismatch between your browser time zone and IP location. ShieldLabs shows VPN, proxy, Tor and privacy relay as named signals. A VPN alone is not proof of abuse; the risk band depends on the full visit assessment.
The Risk Score combines the risk signals on one visit into a number from 0 to 100, in three bands: Trusted (0 to 29), Suspicious (30 to 59) and Dangerous (60 to 100). A website reads the score and the named signals behind it to decide whether to allow an action, ask for verification, or stop it.
Not necessarily. Incognito mode starts without your regular cookies, so the Cookie ID changes. Device intelligence can still recognize a returning browser and connect activity across visits. Run the checker in a regular and a private window to compare the IDs and signals.
Yes. Anti-detect browsers change the fingerprint a website sees, and those changes leave traces a real browser does not. ShieldLabs raises the Anti-detect Browser signal, which weighs 60 and puts a visit in the Dangerous band on its own.
Look at the risk signals on your result: each one names what raised the score, for example a VPN or proxy, a browser time zone that does not match your IP location, signs of browser automation, or an IP address with a history of abuse. Turning off a VPN or proxy, or using a regular browser without automation, usually brings the score down.