dangermouse what this site collects and why

Dangermouse grades whether a visit looks like a real person on a real device. Every page here is a report card about the visit that requested it, so what it collects is the visit itself. It is a measurement site: nothing is sold, shared for advertising, or joined to an identity.

What is collected

Why

Each item feeds a check on the card: does the TLS library match the browser the User-Agent claims, do the headers arrive in that browser's order, does the device the script measures match the one the headers describe, has this address or device been seen many times. Counts across visits (population facets) are kept so that a burst of visits from one device or address can be recognised.

The one cookie

The site sets exactly one cookie, dm: a random value, first-party (host-only, no Domain attribute), HttpOnly, Secure, SameSite=Lax, kept for 365 days. It is set only on the report page, never on files, the beacon or other paths. It is a population key: it lets the population facets tell a returning browser from a new one. The server stores only a keyed hash of the value, never the value itself. Clearing it makes your next visit look like a first visit and changes nothing else.

How long it is kept

Privacy browsers

Some browsers lie about the device on purpose to resist fingerprinting. When the page script detects Brave or Firefox's resist-fingerprinting mode, the card applies an allowance so that privacy protection is not graded as fraud:

Knowledge base

The checks compare each visit with a knowledge base built from public sources. Knowledge base 2026.11.3, built 2026-11-01.

GPU renderer data from opengles.gpuinfo.org by Sascha Willems, CC BY 4.0

AppleDB, © 2022 emiyl, MIT License, https://github.com/littlebyteorg/appledb

AppleDB credits portions of its data to The Apple Wiki (theapplewiki.com, CC BY-SA) and hack-different/apple-knowledge (MIT)

Software 647e249. Back to a report card for this visit.