Skip to Content
Platform.Ontology

MAC address

A page cannot read your device's network hardware address.

Blocked for appsDevice detailsHardware IDsWeb browsersWhen the page loadsWhile you use it

In one line

Can't see your device's network hardware address (MAC)

A page cannot read your device's network hardware address.

MAC addresses never reach the web platform. Proxies are weak: WebRTC local candidates (mDNS now) and Bluetooth device IDs after a prompt are per-origin and randomized. iOS and Android also randomize Wi-Fi MACs per network.

What it can and can't do

What the user does: Nothing. Pages have no way to ask for this

It can

  • See random per site IDs from some features, such as Bluetooth after you approve
  • See a masked network address from WebRTC
  • See your IP address on the server side

It cannot

  • See your real MAC address
  • See Wi-Fi addresses; iPhone and Android randomize them per network
  • Link one site to another using a MAC
  • Get a stable ID from Bluetooth across sites

Browser support

BrowserStatusFirst versionNote
ChromeNot supportedNot availableNone
EdgeNot supportedNot availableNone
FirefoxNot supportedNot availableNone
SafariNot supportedNot availableNone
Safari on iPhoneNot supportedNot availableNone
Chrome on AndroidNot supportedNot availableNone
Samsung InternetNot supportedNot availableNone

How a site asks for it

APInone
How access is grantednot-exposed
What the user seesNone
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsread fresh on every page load; nothing stored
How to take it backnot applicable
Inside an iframeReadable from cross-origin iframes too (same values)

Typical flow

  1. Page script reads the value
  2. No prompt is shown

Data you get

Shape: none
How often: static per session

FieldTypeUnitRangePrecision
proxy: WebRTC local ICE candidatestringNoneformerly local IPv4, now random mDNS nameNot listed
proxy: Web Bluetooth device.idstringNoneper-origin opaque ID, only after user picks a deviceNot listed

Technical limits

  • Stable cross-site identifier

The story

What it is

A page cannot read your device's network hardware address.

For you

Your device's hardware address stays hidden from websites. It never leaves your device through the browser. That makes you harder to follow from one network to the next.

For makers

The hardware address is a permanent ID that trackers love. The web never exposed it. Weak stand-ins exist, but they are random or per site.

Where you see it

TypeExampleApps
adsAn ad network wanted a permanent device ID and falls back on cookies and fingerprints.None named
securityA fraud team wanted to block known bad devices and uses a browser profile instead.FingerprintJS
enterpriseAn IT portal wanted to allow only company laptops and needs a managed agent.None named
smart-homeA router setup page wanted the address of your phone and uses a sign-in on the router instead.None named
shoppingA store wanted to detect in-store visits by phone signals and cannot from a web page.None named
gamesA game ban system wanted a permanent ID and bans accounts instead.None named
analyticsA measurement vendor wanted to connect two devices and uses logins.None named

Risks

  • Other signals still help tracking

Good uses and abuse

Legitimate uses

  • None: the browser deliberately withholds it

Known abuse

  • Sites attempt proxies to recover it

Scores

ScoreValueMeaning
Sensitivity5 of 5How revealing the data is
Utility2 of 5How useful it is to honest apps
Friction3 of 5How much the user has to do
Fingerprint bits0Rough identifying entropy, when known

Sources

How well checked: Based on official documentation.

On this page