Skip to Content
Platform.Ontology

Wi-Fi name, BSSID and signal strength

Sites cannot read your Wi-Fi network name, router ID or signal bars.

Blocked for appsDevice detailsNetworkWeb browsersWhen the page loadsWhile you use it

In one line

Can't see your Wi-Fi name, router ID, or signal bars

Sites cannot read your Wi-Fi network name, router ID or signal bars.

Wi-Fi identity is a location tracker (BSSID databases map to street addresses). Browsers expose none of it. Proxies: Network Information type on Android, server-side IP geolocation, and the Geolocation API which uses Wi-Fi servers behind its prompt.

What it can and can't do

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

It can

  • See if you are on Wi-Fi or cellular in Chrome on Android
  • Guess your area from your IP address
  • Use your location only after you allow it in the browser

It cannot

  • See the Wi-Fi name (SSID)
  • See the router ID (BSSID)
  • See signal bars
  • See nearby networks

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: navigator.connection.typestringNonewifi or cellular, Chromium Android onlyNot listed
proxy: effectiveType and rttstringNonelink quality bucket, not identityNot listed
proxy: Geolocation APIstringNoneuses nearby Wi-Fi inside the OS and returns lat/long only after a prompt, accuracy 10 to 100 mNot listed
proxy: WebRTC ICE candidatesstringNonelocal IPs hidden behind mDNS .local names since Chrome 75 and Firefox 78Not listed

Technical limits

  • Wi-Fi BSSID to location lookup enables physical tracking

The story

What it is

Sites cannot read your Wi-Fi name, router ID or signal bars.

For you

A site does not know which Wi-Fi you use. That matters since Wi-Fi names and router IDs can pin down your home or workplace. Only your internet address and connection type are visible.

For makers

Router IDs can be matched in databases to street addresses, so they are location data. Browsers keep them hidden. Sites use IP address lookups and a rough connection type.

Where you see it

TypeExampleApps
adsAn ad network wanted your Wi-Fi name to place you in a venue and uses IP location.None named
shoppingA store wanted to know when you are in the shop and cannot from a web page.None named
gamesA game site wanted Wi-Fi strength for matchmaking and runs a speed test instead.Xbox Cloud Gaming
videoA video call tool wanted signal strength and measures packet loss instead.Zoom, Google Meet
securityA fraud team wanted to match known networks and uses IP reputation.None named
travelA hotel site wanted to detect that you are on its Wi-Fi and uses a login page.None named
enterpriseA company portal wanted to allow only office Wi-Fi and uses VPN or sign-in.None named

Risks

  • IP address still shows rough place

Good uses and abuse

Legitimate uses

  • None: the browser deliberately withholds it

Known abuse

  • Wi-Fi geolocation of a person's home or workplace

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