Skip to content

Blog

Your profile gives itself away by window size first

You maximise a profile window on your own monitor, and the profile meanwhile tells the site its screen is smaller. The window ends up wider than the screen it claims, and no real machine looks like that. Across a pool of 900 profiles that mismatch turns up for about six profiles in ten.

The ARMANOS team6 min

A site finds it in one line

Any page reads the screen your browser claims and the window it is looking through. Both are ordinary values, and a site's script needs no permission for either.

On a page that declares a viewport, a window wider than the screen describes a machine that does not exist. Without that line a real phone lays out wider than its screen too, so a site only draws its conclusion after it.

  1. 1

    Asks for the screen

    Width and height of the display the browser reports.

  2. 2

    Asks for the window

    Width and height of the area the page is drawn in.

  3. 3

    Compares them

    A window larger than the display is a contradiction inside one browser.

What screens profiles get

Your profile takes its screen from its seed, and across 900 desktop profiles of the current fingerprint generation the pool looks like this.

Eighteen distinct screens appear, from 1280 by 720 to 3840 by 2160. That spread works for you: a pool of one size would be a signal of its own.

Measured on 900 profilesShare
Screens narrower or shorter than 1920 by 1080about 6 in 10
Screens shorter than a 820 point window16 percent
Distinct screens in the pool18
Narrowest and widest1280 by 720 and 3840 by 2160

Why the mismatch is this common

You work on the display you own, and a common one is 1920 by 1080. Maximise a window there and it fills that size regardless of what the profile inside it claims.

So the profiles that disagree are the ones whose screen is smaller than the display in front of you. On a larger display there are more of them, on a smaller one fewer.

A phone makes it obvious

On a phone profile the gap is impossible to hide: a handset claims 360 points across, and a window stretched by hand would be three times that.

That is why a phone profile opens at the size of the handset, and a remembered size is not restored. The desktop case is the same contradiction with smaller numbers.

What size your profile window opens at

Your window opens no wider than the screen the profile claims. A smaller window stays small: the claimed screen is a ceiling, not a requirement.

The ceiling sits on the outer size of the window, and a page reads the inner area, always smaller. The margin works in your favour.

  1. 1

    One rule for every window

    Every window of a profile opens by the same rule.

  2. 2

    The claim is the ceiling

    Width and height never go above the screen the profile reports.

  3. 3

    A phone is exact

    A handset window equals the handset screen rather than merely fitting inside it.

The Fingerprint self-test stays quiet about it

The app carries the Fingerprint self-test (profile menu > Test fingerprint): it opens a page and checks line by line that the browser answers what it was told to. The line about the window is in there too.

On a desktop profile that line does not run. It is grouped with the phone ones, next to touch points and screen orientation, and on a desktop fingerprint the whole group is skipped.

So a person sees a report where everything matched and learns nothing about the gap. Until that line moves to the common group, the window is something to check by eye.

Why a ceiling rather than advice

Advice does not work here: window size is something people drag with a mouse every day without thinking about numbers. The gap appears from one pull towards the edge of the screen.

So a profile window does not open wider than the screen it claims. Smaller is fine, wider is not: the claimed screen is a ceiling and it holds by itself.

What this means for two profiles on one machine

Two profiles on one monitor each get their own claimed screen, and usually a different one: across two thousand pairs they matched in twelve cases out of a hundred. Different widths of maximised windows are not a fault but the very thing profiles exist for.

Equal widths on two windows would tell a platform more than unequal ones. Matching sizes read as one machine rather than two.

The bigger your monitor, the more often the gap

A maximised window takes the width of your monitor, while the screen a profile claims has nothing to do with it. So the ones that disagree are the profiles whose claimed screen is narrower than yours.

Across nine hundred draws it looks like this: on a 1366 monitor roughly one profile in twelve disagrees, on 1920 six in ten, on 2560 almost eight, and on 3840 nearly all of them.

The conclusion is plain: a person with a large monitor is more exposed while doing nothing unusual.

Your monitor widthProfiles with a narrower screen
13668 in 100
153633 in 100
192062 in 100
256078 in 100
384096 in 100

What happens to profiles you already have

The ceiling applies when a window opens, so older profiles are covered as well: their remembered size is trimmed to the claimed screen on the next launch.

Nothing needs moving by hand. If a window was already smaller than the claimed screen, it stays that way: the ceiling never stretches anything.

Height gives way before width

A profile window opens eight hundred and twenty points tall. On the 1280 by 720 and 1280 by 800 screens the claimed height is smaller than that.

So on those profiles the window is taller than the claimed screen before anyone drags it. The ceiling trims height as well, not only width.

Why not simply claim a bigger screen

The temptation is there: give every profile 3840 by 2160 and the window never runs past the edge. That would turn the set of screens into a marker of its own.

Eighteen kinds with uneven shares look like what a platform sees among ordinary people. One size for everyone would be spotted sooner than the gap.

Where these numbers come from

Every share in this entry was counted the same way: take nine hundred profiles of the three desktop kinds on the current fingerprint generation, read the claimed screen width of each, and count how many are narrower than the chosen monitor.

You can repeat it: the numbers come out of the same code that builds a profile's fingerprint rather than from a table written by hand. We recounted with three different sets of profile names, and the share came out between fifty-nine and sixty-three percent on a 1920 monitor.

That is why the text says about six in ten rather than one exact figure. An exact figure here would mean one sample passed off as a property, and we have been there.

How to check your own

Open any browser console and read the screen and the window side by side. The comparison takes one line and needs nothing installed.

Do it in a maximised window and in a small one. A profile that answers honestly gives a window no larger than the screen in both.

What this does not claim

  • It does not claim that matching sizes make a profile safe. It removes one contradiction out of many, and behaviour, payment details and the history of the account remain untouched by any browser.
  • It does not claim that every site checks this. Some do, some never look, and none of them publish what they check.
  • The self-test inside the app runs this comparison for a profile with touch, not for a desktop one. Extending it to desktop changes the number of checks the app reports, so it waits for the next acceptance run on a built engine.
  • The numbers above describe our pool of screens, drawn on the generation current today. A different pool gives different shares.

Where you can see this yourself

Every number above comes out of code you can open and run.

The screens are drawn from the profile seed
packages/shared/src/index.js
The size of a profile window is decided in one place
apps/desktop/src/lib/окноПрофиля.js
The rule is executed against real fingerprints, not read as text
apps/desktop/test/окно-не-шире-экрана.js
A phone window is sized to the handset
apps/desktop/src/lib/mobileEmulation.js · apps/desktop/src/lib/mobileWindow.js

Questions

Why not give every profile the largest screen?
One size for everyone is a signal of its own, and a screen far from the machines a platform usually sees stands out on its own.
Do you lose the window size you chose?
Only the part above the claimed screen. A window smaller than the screen opens exactly as you left it.
Is this about full screen mode?
No. Full screen makes the window equal to the display, and the contradiction appears only when the window is larger than what the profile claims.
Can a site tell how the numbers were capped?
It reads two ordinary values and cannot see what produced them. What it can see is whether they agree.
Does a proxy change any of this?
No. The address arrives from elsewhere, and both of these numbers are produced on the machine in front of you.

See what your own browser answers

The check reads 12 values and sends nothing anywhere.