What the Site Sees About You

Open this page in the profile you're checking and click the button. Nothing to install.

Check Fingerprint

Why Checks Matter More Than a List of Values

Every fingerprint checker shows a list of signals, and on its own the list says little. A single value almost never gives a person away: millions of machines report the same thing. What gives it away is contradictions — and we check the three that come up most often.

Proxy Country vs. Time Zone

The most common reason for a captcha, and almost never a "bad fingerprint." The proxy exits in Germany while the browser reports Moscow time: real users almost never show this combination, and the checking site notices right away.

Hence the rule: time zone, language, and geolocation should come from the country the proxy actually exits through, not at random. And they should be set once — a time zone that changes between launches is just as noticeable.

⚠️ A separate case this check won't catch: sometimes two databases report different countries for the same address. Then the check will never pass, no matter how you set it — match one database and the other shows a mismatch. This usually happens with resold datacenter addresses; the only fix is switching the proxy.

Tab vs. Background Process

Part of the data the page reads right at load, part comes from background processes that live alongside it. If a spoof reaches the tab but not the background, the site reads two different answers in one tab. That kind of contradiction tells a checking service more than any single value.

We check the same thing: we read signals in the main thread and in the background process and compare them.

Sign of a Controlled Browser

navigator.webdriver is true when the browser is controlled from outside — through a debug port, Selenium, Playwright. Any check can see it, and signing into a Google account on such a profile won't go through.

If you simply opened the page by hand and the flag is set, the browser was launched with a debug key. Don't do that for account work.

What This Doesn't Check, and Why

WebRTC leaks are a separate check, built differently: there the browser itself looks for your real address past the proxy. We'll turn that into its own page.

Fonts. We deliberately don't treat the font set as part of the fingerprint and don't recommend spoofing it: on a stock Windows machine, fonts are identical across millions of machines — they don't single you out. A random set unique to each profile would do the opposite: it would make every profile rare, and therefore noticeable.

The same canvas fingerprint across profiles on one machine isn't a bug. That's how it should be unless you spoof it on purpose: canvas is drawn by the video card, and profiles on one machine share it.

If a Check Turns Red

Country and time zone don't match — adjust the time zone and language to the proxy's country. In Morfiade this happens on its own: the program asks the proxy for its country and sets the time zone, language, and geolocation from it, and shows a light when checking the proxy — whether two independent databases agree on the address's country.

Tab and background don't match — the spoof in your tool isn't reaching background processes. This can only be fixed on the tool's side.

The automation flag is set — remove the debug key from how you launch the browser. Fingerprint spoofing works fine without it.

About the Honesty of This Page

We don't show an "anonymity score" in percent, and we don't write "you're protected." Scores like that are invented by the services themselves, every one is different, and they don't mean much: the site checking you counts matches and contradictions, not percentages.

What is an antidetect browser · What Morfiade does · Try it free for 7 days