MAC address
A page cannot read your device's network hardware address.
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
| Browser | Status | First version | Note |
|---|---|---|---|
| Chrome | Not supported | Not available | None |
| Edge | Not supported | Not available | None |
| Firefox | Not supported | Not available | None |
| Safari | Not supported | Not available | None |
| Safari on iPhone | Not supported | Not available | None |
| Chrome on Android | Not supported | Not available | None |
| Samsung Internet | Not supported | Not available | None |
How a site asks for it
| API | none |
| How access is granted | not-exposed |
| What the user sees | None |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | read fresh on every page load; nothing stored |
| How to take it back | not applicable |
| Inside an iframe | Readable from cross-origin iframes too (same values) |
Typical flow
- Page script reads the value
- No prompt is shown
Data you get
Shape: none
How often: static per session
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
proxy: WebRTC local ICE candidate | string | None | formerly local IPv4, now random mDNS name | Not listed |
proxy: Web Bluetooth device.id | string | None | per-origin opaque ID, only after user picks a device | Not 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
| Type | Example | Apps |
|---|---|---|
| ads | An ad network wanted a permanent device ID and falls back on cookies and fingerprints. | None named |
| security | A fraud team wanted to block known bad devices and uses a browser profile instead. | FingerprintJS |
| enterprise | An IT portal wanted to allow only company laptops and needs a managed agent. | None named |
| smart-home | A router setup page wanted the address of your phone and uses a sign-in on the router instead. | None named |
| shopping | A store wanted to detect in-store visits by phone signals and cannot from a web page. | None named |
| games | A game ban system wanted a permanent ID and bans accounts instead. | None named |
| analytics | A 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
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 5 of 5 | How revealing the data is |
| Utility | 2 of 5 | How useful it is to honest apps |
| Friction | 3 of 5 | How much the user has to do |
| Fingerprint bits | 0 | Rough identifying entropy, when known |
Related capabilities
Related
- Serial number, IMEI and device ID. Can't see your serial number, IMEI, or advertising ID from a web page
Sources
How well checked: Based on official documentation.