Antidetect & browser fingerprint test
Is this browser detectable as a bot? Kitsune reads every layer — TLS, HTTP/2, TCP/IP, GPU, JavaScript, behaviour — and checks whether they tell one consistent story. A stealth or antidetect browser can fake any single layer; making them all agree is the hard part. You get the real verdict a site would reach, live.
Scanning your browser…
Behavioral layer — live
Type a sentence and move your mouse — or swipe on a touch screen. Your mouse/touch dynamics and keystroke timing are measured live and re-score the verdict automatically once there's enough input.
Predicted browser — from feature detection, independent of the User-Agent
Network / wire layer — TLS/JA4, HTTP-2, QUIC, TCP/IP, read from your raw connection by Kitsune’s edge
Fingerprint surfaces — every enumerated value · tamper status
How Kitsune detects bots & antidetect browsers
Most fingerprint testers list signals. Kitsune flags incoherence across layers — the contradictions a real browser cannot produce but a spoofed or automated one does. The User-Agent, the TLS handshake, the HTTP-2 frames, the TCP/IP stack, the GPU and the JavaScript feature-set all have to describe one coherent device. When they disagree, that is the tell.
It scores seven layers: TLS/JA4, HTTP-2, QUIC/HTTP-3 and TCP/IP-OS read from the raw connection by Kitsune's edge; canvas, WebGL, audio, fonts and Client Hints in the browser; mouse and keystroke dynamics; and IP reputation. Every rule is data in a public registry — the same rules the server runs.
An antidetect browser can spoof the User-Agent and patch navigator.webdriver, but making the JA4, the frame order, the TCP stack, the GPU renderer and the JS surface all agree on one real device is much harder — and that is exactly what this page measures.
FAQ
What is a browser fingerprint?
The combination of signals a site reads from your browser — canvas/WebGL rendering, fonts, screen, audio, Client Hints and more — that together identify your device without cookies. Kitsune enumerates them and scores how coherent they are.
Can antidetect browsers beat fingerprinting?
Stealth/antidetect browsers (Camoufox, undetected-chromedriver, multilogin, …) spoof many signals, but making every layer agree — TLS JA4, HTTP-2 frame order, TCP/IP stack, GPU renderer and the JS feature-set all consistent with one real device — is far harder. Kitsune flags the contradictions that remain.
What is JA3 / JA4 TLS fingerprinting?
JA3 and JA4 fingerprint the TLS ClientHello your browser sends on connect. They identify the TLS stack, which often betrays an automation tool even when the User-Agent looks normal. Kitsune's edge reads yours from the raw connection.
Is my browser detectable as a bot?
Run the test above: Kitsune scores your browser across network, browser, behavioral and reputation layers and returns a live verdict — human, suspicious, or bot — with the exact signals that fired.
Does this send my data anywhere?
No. Your signals are scored by Kitsune's detector at this origin to compute the verdict you see, and held only in memory for that — they are never written to disk, never retained after the response, never sold, shared, or used to track you across visits. The store runs in-memory and is empty again on restart. There are no third-party trackers on this page. See the privacy notice.