Here's what the internet can see about you right now.

Every site you visit reads some combination of these signals. Scanline reads them too, shows them to you plainly, and sends nothing to a server of ours.

Scanning your connection…

Network

IP address—
Internet provider—
Network (ASN)—

Location

Estimated from your IP address. It's usually accurate to a city, rarely to a street.

City, region—
Country—
Coordinates—

This asks your browser for GPS/Wi-Fi location. Nothing is sent to us.

VPN & proxy signal

A heuristic, not a certainty — built from your network's ownership and a couple of consistency checks.

Checking…

This can be wrong in both directions. Treat it as a hint, not a verdict.

Hosting / datacenter IP—
Timezone consistency—

Device & browser

Browser—
OS / platform—
Screen—
Color depth—
Language(s)—
Timezone—
CPU cores—
Device memory—
Touch support—
Cookies—
Do Not Track—

Graphics (WebGL)

Your graphics card identity is readable by any page — a common fingerprinting signal.

Renderer—
Vendor—

WebRTC leak test

If you use a VPN, your real IP should not appear here.

Local network address—
Public IP via WebRTC—
Compared to IP above—

Hardware address (MAC)

No website can read this, including this one. A MAC address only travels as far as your local router — it never reaches the public internet, and browsers have no API that exposes it. Any site claiming to show you a visitor's MAC address is either showing you a fake value or reading it from a network you already control.

The closest real signal is your local network address, which we do capture below in the WebRTC leak test.

Your fingerprint

A short hash made from the signals above — screen size, fonts, GPU, timezone, and more. Sites use combinations like this to recognize you again even without a cookie.

—

Changing one of these settings changes the hash; most people never clear more than a couple.