Check guide · In the browser

Browser fingerprint

Canvas, graphics and fonts: the near-unique sketch of this browser.

What this check is

Ask a browser to draw the same picture twice and it produces a result shaped by its graphics stack, its GPU and its installed fonts. This check renders those probes and hashes the output, the standard fingerprinting technique, and reports the GPU it found along the way.

What Tells reads

A canvas rendering and its hash
WebGL support, parameters and the unmasked GPU renderer string
The detectable font list and its size

How to read your result

Warning: WebGL is unavailable, or the canvas probe failed or was blocked. Real browsers almost always can do both; missing graphics is a property of stripped-down or synthetic environments.
Pass: Both probes rendered and hashed normally.

Why it matters

Fingerprints rarely accuse anyone of being a bot directly. Their power is correlation: the same fingerprint across fifty accounts ties the accounts together, and a fingerprint no real device produces marks its owner as synthetic. Bot operations care about fingerprints because rotating IPs and cookies is easy, while rotating convincing hardware stories is not.

Where this matters most

Across the platforms Blowhorn works with, rated in the platform guide (H = matters a lot, M = contributes, L = no public evidence; tags mark vendor-stated, reported, or inferred evidence):

LinkedIn (H): an encrypted device fingerprint is assembled and attached to session API requests [Reported]
X (M): device fingerprinting is reported on signup and login flows [Reported]
Reddit (M): absent canvas or WebGL on a claimed browser client is a reported detection input [Reported]

Everywhere else in the set this one rates Low.

In your report

Find it in the checks table on the tool page, with the detail in the Browser section. The same findings appear in the report JSON under verdict.reasons, and the agent guide explains how to read them programmatically.