Skip to Content
Platform.Ontology

Legacy cpuClass and oscpu

Old non-standard strings naming the CPU class and operating system CPU.

Gets silentlyDevice detailsHardwareWeb browsersWhen the page loadsWhile you use it

In one line

Can sometimes see an old CPU and OS string, mostly in Firefox

Old non-standard strings naming the CPU class and operating system CPU.

cpuClass (old Internet Explorer) and oscpu (Firefox) mostly return nothing in Chrome, which is itself a signal for which browser engine runs.

What it can and can't do

What the user does: Nothing. It happens when a page checks the old browser fields

It can

  • Get the oscpu text in Firefox
  • Notice when Chrome returns nothing, which hints at the engine
  • Use the answer to guess the browser and OS

It cannot

  • See anything useful in Chrome, Safari, or Edge
  • See your exact chip or speed
  • Get the old cpuClass value outside very old Internet Explorer
  • Learn your name or location from it

How it differs between platforms: Only Firefox returns the oscpu value. Chrome, Safari, and Edge return nothing.

Browser support

BrowserStatusFirst versionReleasedNote
ChromeNot supportedNot availableNot listedNone
EdgeNot supportedNot availableNot listedNone
FirefoxSupported12004-11-09oscpu
SafariNot supportedNot availableNot listedNone
Safari on iPhoneNot supportedNot availableNot listedNone
Chrome on AndroidNot supportedNot availableNot listedNone
Samsung InternetNot supportedNot availableNot listedNone

How a site asks for it

APInavigator.cpuClass, navigator.oscpu
Browser compat keysapi.Navigator.oscpu
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 cpuClass and oscpu
Shape: string
How often: static

FieldTypeUnitRangePrecision
cpuClassstringNonex86 or undefinedNot listed
oscpustringNonee.g. Intel Mac OS X 10.15 or undefinedNot listed

Technical limits

  • Undefined in most browsers

The story

What it is

Old strings that name your processor and system, mostly empty now, which itself hints at your browser.

For you

You never see these. Most return nothing. The fact that one is empty and another is filled in is what reveals which browser engine you use.

For makers

These came from the 1990s and 2000s browser wars. Today they are mostly a consistency test: a bot that pretends to be Firefox but returns the wrong answer gets caught. They add a few bits to a device profile.

Where you see it

TypeExampleApps
securityA bot defence service tests whether Firefox-only strings exist when a visitor claims to be Firefox, and challenges those that fail.DataDome, Akamai Bot Manager
analyticsAn old analytics script still reads the strings to label visitors by browser family.None named
adsAn ad fraud vendor checks that the strings match the claimed browser before counting an ad view as real.DoubleVerify, Integral Ad Science
developerA compatibility test page prints these values to show what an unusual browser reports.None named
gamesA browser games portal uses them to hide a feature in browsers that never supported it.None named
bankingA bank's login risk engine adds a point when old strings and the user agent disagree.None named

Risks

  • Tiny fingerprint piece
  • Mismatch can wrongly flag a person

Good uses and abuse

Legitimate uses

  • None modern

Known abuse

  • Engine and OS detection

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): cpuClass, oscpu.

Sources

How well checked: Based on official documentation.

On this page