Is this browser real?
This page reads your device the way a fraud system does: it builds a fingerprint, checks whether that fingerprint is genuine or assembled, looks for automation, and compares the IP and timezone your browser reports against the ones your connection actually reveals.
Scanning
Running over 200 checks against this browser.
What your browser claims, and what your connection reveals
A proxy rewrites the address on your web requests, but it does not change the clock on your machine, and it does not intercept the UDP probe WebRTC sends to a STUN server. When those disagree, the disguise shows.
IP address
The left column is what your browser discovered about itself. The right column is what our server observed when the request arrived.
Your browser discovered
Our server observed
Timezone
Your operating system clock against the timezone your network address belongs to.
Your browser reports
Your IP belongs to
Network
Connection reputation
Resolving the network operator…
Is the fingerprint genuine?
A real device tells one story. Its fonts, GPU driver, speech voices, platform string and Client Hints all come from the same machine, so they agree. A fabricated identity has to keep six unrelated subsystems in sync, and usually does not.
Checking…
Cross-examining the fingerprint.
What each subsystem says about your operating system
The worker realm
Almost every stealth tool patches the page it is handed. A Worker is a different global in a different execution context, built by the browser from the same underlying data, and a patch applied to the page does not reach it. So we ask both and compare: whatever the page claims, the worker says what the browser actually knows.
Engine version
Chromium ships features on a published schedule, so the APIs actually present pin down the real engine version regardless of what the User-Agent claims.
Headless or virtual machine?
A headless browser has no screen, no sound card and no window. Retail Chrome has all three, plus licensed codecs and a real GPU that the open-source Chromium bundled with Puppeteer and Playwright does not. Every probe is listed below, including the ones you passed, so you can see exactly what the answer rests on.
Checking…
Running the environment probes.
Browser extensions
Extensions are not plugins. navigator.plugins has listed the same five
built-in PDF viewers since Chrome 57 and no extension has ever appeared there, so an
extension has to be found by what it leaves behind in the page: a script or stylesheet
served from its own origin, a global it injects, or markup it writes into the document.
Looking…
Scanning the page for injected content.
What this cannot see. An extension that only reads the page, runs entirely in its own isolated world, or works by rewriting network requests leaves nothing here to find. A VPN or proxy extension is one of those — it changes what the network sees rather than what the page contains, so it is caught by the address and timezone comparison instead, not by this list. An empty list means nothing was detectable, not that nothing is installed.
Automation and instrumentation
How you are using this page
Move the pointer, scroll and type anywhere on this page. Human input carries curvature, acceleration and timing jitter; scripted input does not. This panel updates live.
Input integrity
isTrusted separates one kind of automation cleanly: anything dispatched
from JavaScript — element.click(), a synthesised MouseEvent,
Selenium's execute_script — is marked untrusted by the browser itself.
It does nothing against the other kind. Puppeteer's page.mouse.click,
Playwright's locator.click and Selenium's own click all travel the real
input pipeline, so they arrive trusted. Those have to be caught on what the event
contains. Move the pointer and click anywhere to fill this in.
How this page was opened
Context, not accusation. A driver that navigates with
window.location, a CDP Page.navigate, or a Chrome started
with the address on its command line all arrive with no referrer, one history entry
and no user gesture — and so does a person typing an address into a fresh tab. None
of it is scored on its own.
Your fingerprint in full
| Device fingerprint | — |
|---|---|
| Canvas | — |
| WebGL | — |
| Audio | — |
| Fonts | — |
This identifier is derived only from values that survive a browser restart and a change of network. It is what lets a fraud system recognise the same device arriving from a different address.
Put this on your own site
One script tag scores every visitor and reports to your dashboard.
<script src="https://browserscan.in/t.js" data-key="YOUR_SITE_KEY" async></script>Read the integration guide for the server-side verification call, which is the part that actually blocks fraud.