Glowing Web Network
Glowing Web Network

Browser
Fingerprint Checker

A deep fingerprint & tamper / bot diagnostic — canvas, WebGL, audio, fonts, navigator, timezone, math, codecs and features, plus lie detection and a trust score. 100% client-side; nothing is sent to our servers.

100% client-side • No registration • Nothing leaves your browser

See also: Fingerprint Generator · TLS Fingerprint Checker

/ 100
Checking…

Trust score

How a fingerprinting vendor would likely grade this browser, based on tamper signals, automation markers and signal coherence. See headless browser detection.

Composite fingerprint
Computing in your browser…

Roughly 1 in — visitors share a profile like this.

Lies / tamper detection

Checks whether native APIs or navigator/screen properties have been overridden — the kind of inconsistency a vendor flags as spoofing.

Analysing…

Headless / automation markers

Looks for navigator.webdriver, Chromedriver hooks, software rendering and other automation tells. See headless detection.

Analysing…

What this tool reads

This diagnostic reads the high-entropy signals fingerprinting and anti-bot vendors use to identify a browser: the 2D canvas, WebGL GPU and render, the AudioContext render, installed fonts, navigator and screen properties, timezone / locale, a math battery, supported media codecs, and platform features. It then cross-checks them for tampering and automation markers and rolls everything into a trust score.

It is the diagnostic companion to the Browser Fingerprint Generator. Learn more in our glossary entries on browser fingerprinting, canvas fingerprinting, WebGL fingerprinting, AudioContext fingerprinting, TLS fingerprinting, and fingerprinting evasion.

For diagnostic and developer use only — run checks on sites you are authorised to access. The lie and automation panels show what a vendor would see; they are not instructions for spoofing.

Screen & Display

Checking…

Resolution, available area, color depth, device pixel ratio and matchMedia preference queries.

Computing…

Timezone & Locale

Checking…

Intl resolved options, timezone offset and locale coherence checks.

Computing…

Fonts

Checking…

Installed fonts detected via offscreen text measurement against generic fallbacks.

detected
0 of 0 probed
Computing…

Math / Float battery

Checking…

A fixed set of Math operations whose low-order bits vary across JS engines, libm and CPU architecture.

Computing…

Media & Codecs

Checking…

canPlayType / MediaSource codec support, speech-synthesis voices and media-device kinds.

speech voices
0
Computing…

Canvas

Checking…

A fixed text + shape recipe drawn to a hidden canvas, then toDataURL() hashed.

Rendering…
Computing…

WebGL

Checking…

GPU vendor/renderer metadata (including unmasked renderer) plus a rasterised render hash.

Vendor
Renderer
Unmasked vendor
hidden
Unmasked renderer
hidden
WebGL version
Max texture size
Computing…
Computing…

Audio

Checking…

An OfflineAudioContext renders an oscillator through a dynamics compressor; floating-point output is the entropy.

Buffer magnitude sum
Computing…

Platform Features

Checking…

Presence and shape of notable APIs: WebGL2, WebGPU, OffscreenCanvas, WebAssembly, storage quota, permissions and more.

Computing…

Frequently Asked Questions

What is a browser fingerprint?

A browser fingerprint is a combination of device and browser characteristics — canvas rendering, WebGL GPU info, audio processing, fonts, screen size, navigator properties and more — that together can identify a browser without cookies.

What is lie / tamper detection?

Lie detection cross-checks signals for contradictions that reveal spoofing: a native function whose source is no longer "[native code]", a navigator getter that has been overridden, a user agent that claims Windows while navigator.platform says macOS, or a Web Worker that reports a different userAgent than the main thread. Genuine browsers are internally consistent; spoofed ones leak these mismatches.

How is the trust score computed?

The score starts at 100 and subtracts weighted points: patched native functions (-18), overridden prototype getters (-14), worker/window mismatches (-16), hard automation markers like navigator.webdriver (-25), softer headless markers (-8 each), software GPU rendering such as SwiftShader (-12), each randomised active fingerprint (-6), and missing high-entropy APIs or locale mismatches (-4). The result maps to Trusted (80–100), Suspicious (50–79) or Likely bot/spoofed (0–49).

Why am I flagged as a bot?

Common triggers are navigator.webdriver being true, a HeadlessChrome user-agent token, Chromedriver artefacts on the document, an empty navigator.plugins list on Chrome, zero outerWidth/Height, or a software renderer like SwiftShader/llvmpipe instead of a real GPU. Each appears in the automation-markers panel with an explanation.

Does spoofing my user agent help?

On its own it usually hurts. Overriding only navigator.userAgent leaves dozens of other signals — platform, Client Hints, Worker-scope navigator, codec support, fonts — pointing at the real browser, which produces exactly the inconsistencies this tool flags as lies. Coherent profiles matter more than any single value.

Is my fingerprint really unique?

Usually yes, especially in combination. Any single signal might be shared by many people, but the combination of canvas, WebGL renderer, audio output, fonts and navigator properties is unique for the large majority of visitors.

Can I disable fingerprinting?

Brave and Firefox with resistFingerprinting randomise canvas and audio output, which this tool flags as "Randomised". That helps against tracking, but a randomised signal is itself a detectable signal to some vendors.

Does Scrappey randomise fingerprints?

Scrappey browser sessions generate consistent fingerprints that match the device profile being used, so canvas, WebGL, audio and navigator signals stay coherent across a session rather than contradicting each other.

footer-frame

Start building with Scrappey

Try It For Free. No Subscription Required. No Credit Card Required. Instant Set-Up. 150 Free Requests Are Waiting For You!

Frequently asked questions

What is Scrappey.com?

Scrappey.com is a web scraping API that handles all the complex aspects of web scraping, such as handling dynamic content, rotating proxies, advanced request handling, headless browsers, and verification processing. It offers an all-in-one solution for extracting publicly available data from websites.

How does Scrappey.com work?

Scrappey.com provides a web scraping API that allows you to send requests to extract publicly available data from websites. It handles dynamic content and modern website complexity, including rotating proxies, advanced request handling, and verification processing. You can easily extract publicly available data from websites using their built-in features like headless browsers and AI-powered data extraction.

Can I customize the proxies used for scraping?

Yes, with Scrappey.com, you have the option to use Sticky Rotating Proxies for seamless scraping. Alternatively, you can also set your own proxies if desired.

Is there a free trial available?

Yes, Scrappey.com offers a free trial where you can try it out without a subscription or credit card. Instant setup is provided, and you get 150 free scrapes to explore the capabilities of the platform.

What happens if a request fails?

We only charge for successful requests. Failed requests are not counted towards your usage, so you only pay for what works.

I need to scroll or click on a button on the page I want to scrape

No problem, you can pass any JavaScript snippet that needs to be executed by using our JavaScript scenario parameter. This allows you to interact with dynamic content, scroll pages, click buttons, wait for elements, and perform any custom JavaScript actions before extracting the data.

What is the pricing structure for Scrappey.com?

Scrappey.com offers simple and transparent pricing: €0.20 per 1,000 direct HTTP requests and €1.00 per 1,000 full-browser requests. Residential proxies are included on both tiers — no separate proxy billing, no hidden fees, no complicated pricing tiers. You only pay for successful requests.

Are there any usage restrictions or limitations?

Scrappey.com provides scalable access for extracting publicly available data. Whether you need to extract data from a few pages or a large dataset of publicly accessible content, you can do so with flexible usage options. Please note that Scrappey.com only supports scraping publicly available data, and users must comply with applicable laws and website terms of service.

What support channels are available?

Scrappey.com provides various support channels for assistance. You can refer to their documentation, frequently asked questions section, blog, and uptime status page. Additionally, you can get in touch with them via email or join their Discord community for further support.

I'm not a developer, can you create custom scraping scripts for me?

We don't create custom scraping scripts, however we will gladly write some code snippets helping you to use our most powerful features: AI-powered data extraction and JavaScript scenario. Our documentation includes examples in multiple programming languages to get you started quickly.

What is a request and how are they counted?

Each API call to Scrappey counts as one request. Our pricing is based on successful requests. By default, JavaScript rendering is enabled, which allows you to extract data from modern websites with dynamic content. All features including proxies, CAPTCHA solving, and advanced web access handling are included in each request.

How fast is Scrappey's API and what if a site is hard to scrape?

Scrappey's API is optimized for fast response time, even when dealing with complex or protected websites. If other scrapers struggle with sites that have advanced security measures, Scrappey is designed to handle these challenges efficiently, ensuring reliable data retrieval. Our advanced web access handling, residential proxies, and intelligent retry logic work together to maximize success rates.