Skip to Content
Platform.Ontology

Legacy navigator properties (appName, appVersion, platform, vendor ...)

Frozen strings such as appName, appVersion, appCodeName, platform, product, productSub, vendor and vendorSub.

Gets silentlyDevice detailsBrowser identityWeb browsersWhen the page loadsWhile you use it

In one line

Can see old fixed labels naming your browser maker, OS family, and engine

Frozen strings such as appName, appVersion, appCodeName, platform, product, productSub, vendor and vendorSub.

Mostly frozen for compatibility, but platform and vendor still differ by OS and engine. Used for consistency checks against the user agent.

What it can and can't do

What the user does: Nothing. It happens when the page loads

It can

  • Check old browser strings like appName, platform, and vendor
  • Compare them with the user agent to spot fakes
  • Tell the engine (Chromium, Safari, Firefox) apart

It cannot

  • See your exact OS version
  • See your name, location, or accounts
  • Learn much; many values are frozen for compatibility
  • Tell similar browsers apart on their own

Browser support

BrowserStatusFirst versionReleasedNote
ChromeSupported12008-12-11None
EdgeSupported122015-07-29None
FirefoxSupported12004-11-09None
SafariSupported12003-06-23None
Safari on iPhoneSupported12007-06-29None
Chrome on AndroidSupported182012-06-27None
Samsung InternetSupported1.02013-04-27None

How a site asks for it

APInavigator.appName, appVersion, appCodeName, platform, product, productSub, vendor, vendorSub
Browser compat keysapi.Navigator.platform
api.Navigator.vendor
How access is grantednone
What the user seesNone (no browser prompt)
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsNot listed
How to take it backNot listed
Inside an iframeNot listed

Typical flow

  1. Script reads the value
  2. Value joins the fingerprint payload

Data you get

What comes back: Legacy navigator properties (appName, appVersion, platform, vendor ...)
Shape: string
How often: static

FieldTypeUnitRangePrecision
platformstringNonee.g. MacIntel, Win32, Linux x86_64Not listed
vendorstringNoneGoogle Inc., Apple Computer, Inc., empty for FirefoxNot listed
productSubstringNone20030107 or 20100101Not listed

Technical limits

  • Spec says they are legacy constants
  • Easy to spoof

The story

What it is

Old fixed text fields, like app name and vendor, that still differ a little by system and engine.

For you

You never see them. They are mostly frozen for old websites. A few still differ between systems, which lets a site cross check that you are who your browser says you are.

For makers

These strings exist so old sites do not break. Modern sites use them in consistency checks. When privacy tools or bots change one value but forget another, the mismatch stands out.

Where you see it

TypeExampleApps
securityA bot defence service checks that the vendor, platform and user agent agree and challenges those that do not.Cloudflare, DataDome
adsAn ad fraud vendor verifies that browser identity strings are consistent before counting a view.DoubleVerify
developerAn old script reads appName and appVersion to guess the browser, which still works for basic cases.None named
bankingA bank risk engine adds suspicion when two strings disagree.None named
analyticsA fingerprinting library mixes the strings into a device ID.FingerprintJS
gamesA browser games platform checks these strings to pick the right controls layout for the engine.None named

Risks

  • Low value alone, but combined
  • Can wrongly flag privacy tools

Good uses and abuse

Legitimate uses

  • Compat checks

Known abuse

  • Engine and OS fingerprint

Scores

ScoreValueMeaning
Sensitivity1 of 5How revealing the data is
Utility3 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bits1Rough identifying entropy, when known

A real example: LinkedIn

Collector key(s): appName, appVersion, appCodeName, platform, product, productSub, vendor, vendorSub.

Sources

How well checked: Based on official documentation.

On this page