knowingme.appgrid.co.nz
Your browser is introducing you.
A live mirror of the IP, headers, device signals, fingerprint clues, browser capabilities and privacy posture that a normal webpage can see.
Public IPchecking…
Privacy posturechecking…
Approx locationchecking…
No database. No hidden collection. Optional GPS only runs if you press the button and approve the browser prompt.
interactive map
What talks to what
server-side request
Network identity
- IP address
- not exposed
- Host
- not exposed
- Protocol
- not exposed
- Captured
- not exposed
- URL
- not exposed
edge headers
Approximate geo
- City
- not exposed
- Country
- not exposed
- Region
- not exposed
- Latitude
- not exposed
- Longitude
- not exposed
- Timezone
- not exposed
quick read
Privacy score
—/100
- Assessment
- not exposed
- Why
- not exposed
render + combined clues
Fingerprint hashes
- Combined hash
- not exposed
- Canvas render
- not exposed
- WebGL
- not exposed
client-side signals
Browser fingerprint
- User agent
- not exposed
- Platform
- not exposed
- Vendor
- not exposed
- Languages
- not exposed
- Cookies enabled
- not exposed
- Do Not Track
- not exposed
- Automation webdriver
- not exposed
hardware hints
Screen & device
- Screen
- not exposed
- Viewport
- not exposed
- Device
- not exposed
- Connection
- not exposed
- Battery
- not exposed
local environment
Time & locale
- Timezone
- not exposed
- Offset minutes
- not exposed
- Local time
- not exposed
- Page context
- not exposed
browser gates
Permissions & media
- Permission states
- not exposed
- Media devices
- not exposed
- Precise location
- not requested
available APIs
Feature support
- Browser APIs
- not exposed
- Storage estimate
- not exposed
things a page can request
Risky capabilities
- Risk surface
- not exposed
- Important
- Camera, microphone, GPS, files, Bluetooth, USB and clipboard reads need browser permission prompts. A malicious page can still ask, trick, or fingerprint around them.
stun / ice candidates
WebRTC leak test
- Candidates
- not run
- Meaning
- If public IP, LAN IP, or .local names appear here, WebRTC revealed network clues beyond normal HTTP headers.
timing, not raw packets
Latency & packet-ish info
- Latency probes
- not run
- Navigation timing
- not exposed
- Transfer estimates
- not exposed
- Server edge/request size
- not exposed
browser safety limit
Traceroute / packet capture
- Availability
- not run
- Closest browser-safe alternative
- Measure HTTPS fetch timing and WebRTC ICE candidates. Real tracert, ping TTL, SYN packets, and packet capture require native OS tools or a privileged backend.
bot / browser clues
Automation hints
- Signals
- not exposed
raw but curated
Request headers visible to the server
loading…
export
Full report
{
"server": null,
"browser": null,
"preciseLocation": null,
"networkLab": null
}