User agent: what does your browser tell every website?
Shows your browser's raw User-Agent header and a plain-language breakdown of the browser name and version, rendering engine, operating system and coarse device type it implies, parsed entirely in your browser with no server round trip or third-party UA database involved.
What the result means
Treat this as a hint about the client sending the request, not a security boundary — any software can set an arbitrary User-Agent value.
Next step
Check your public IP, or see the MAC vendor lookup for device-level identification.
How it works and limits
Every request your browser makes includes a User-Agent string naming the browser, rendering engine and operating
system it claims to be. This tool reads navigator.userAgent in your browser (the same value sent to every site you
visit) and parses it with AdminKit’s own lightweight parser — no server round trip, no third-party UA database.
Reading the result
The raw string is shown first, then a best-effort breakdown: browser name and version, rendering engine (Blink, Gecko or WebKit), operating system, and a coarse device type (desktop, mobile, tablet or automated bot).
Limits
- A User-Agent string is whatever the client chooses to send — it is a hint, never a verified fact, and any software can set it to anything.
- Chrome, Edge and other Chromium-based browsers are progressively freezing and reducing User-Agent detail (“User-Agent Reduction”), steering sites toward opt-in Client Hints instead — expect this string to carry less information over time, by design.
- This runs entirely in your browser; nothing is sent to AdminKit.
Frequently asked questions
Can a site trust the User-Agent string?
No — any client can send an arbitrary User-Agent value, so it is a hint, not a verified fact.
Why are browsers sending less detail in User-Agent now?
Chrome, Edge and others are freezing/reducing User-Agent detail (User-Agent Reduction) and steering sites toward opt-in Client Hints instead, to reduce passive fingerprinting.