User Agent Checker

See your exact browser, OS, engine & full user-agent string.

Instantly reveal what your browser tells every website about you — browser name and version, rendering engine, operating system, device type and the complete raw User-Agent string. Runs a best-effort automation/headless-browser signal check, exports the full snapshot as JSON, and parses any preset or pasted User-Agent, including bots like Googlebot. 100% client-side — reads navigator.userAgent locally, nothing is sent anywhere.

About User Agent Checker

User Agent Checker features

How to use User Agent Checker

  1. Open the page

    Your browser's User-Agent is read automatically the moment the page loads — no button to press.

  2. Read the headline result

    The dark card at the top is the one answer that matters: your browser, OS, engine and device type in one glance, plus an automation-signal badge.

  3. Copy or export

    Copy the raw UA string, or download the whole snapshot as JSON for a bug report, support ticket or analytics filter.

  4. Test another User-Agent (optional)

    Pick a preset (iPhone Safari, Googlebot, Android Chrome…) or paste any raw string and click Parse to see how it breaks down.

Best practices

How websites use your User-Agent

Servers read the User-Agent header on every request to decide what to send back — a mobile-optimised layout, a legacy-browser warning, or blocking known bot patterns. It's also logged in analytics to report visitor browser/OS/device breakdowns.

User-Agent spoofing & privacy

Any browser lets you override its own UA string (DevTools' device toolbar, extensions, or automation frameworks). That's exactly why the string alone should never be trusted for security decisions — it's a courtesy header, not a verified identity.

For genuine bot verification (e.g. confirming a request really is Googlebot), sites should do a reverse-DNS lookup on the IP — the UA string can be faked by anyone.

Client Hints — the modern replacement

Chromium browsers are gradually 'freezing' the classic User-Agent string for privacy and instead expose structured Client Hints (navigator.userAgentData) that a site must explicitly request — which is also how this tool refines 'Windows 10 / 11' into an exact version when your browser supports it.

Popular use cases

Bug reports

Paste the exact UA into a support ticket so devs can reproduce your issue.

Verify a bot

Check a crawler's claimed identity (Googlebot, Bingbot…) against a real UA string.

Responsive testing

See how your site's UA-based logic reads a phone, tablet or desktop string.

Automation checks

Spot whether navigator.webdriver or other automation signals are present.

Analytics filters

Confirm the exact string format before writing a UA-based segment or filter.

Outdated browsers

Confirm your own browser version before reporting 'this site looks broken'.

Frequently asked questions

What is a User-Agent?

The User-Agent is a short text string your browser sends with every web request, identifying the browser, its version, the rendering engine and your operating system. Websites use it to serve the right layout, block outdated browsers, or detect bots.

What is my browser?

Look at the dark headline card above — it shows the exact browser name and version this page detected from your live User-Agent string, e.g. 'Chrome 128' or 'Safari 17.5'.

Why does it say 'Windows 10 / 11' instead of a specific version?

Windows 10 and 11 both report the identical 'Windows NT 10.0' in the plain User-Agent string by design (a Microsoft privacy change) — they can't be told apart from the UA alone. When your browser supports Client Hints, this tool automatically refines the answer to the exact version.

What does the 'automation signals' badge mean?

It's a best-effort check for signs that the page is being driven by automation software (Selenium, Playwright, Puppeteer) rather than a person — primarily the standardised navigator.webdriver flag, plus a few weaker corroborating signals. It's informational, not a security guarantee: a real, privacy-hardened browser can occasionally trip the weaker signals too.

Can a website fake or spoof its detected browser?

Yes. Any browser lets you override the User-Agent it sends (developer tools, extensions, or the custom parser above). That's exactly why security-sensitive checks should never rely on the User-Agent alone.

Is my User-Agent unique enough to identify me?

On its own, no — many people share the same browser/OS/version combination. But combined with other signals (screen size, fonts, timezone) it can contribute to browser fingerprinting, which is why privacy-focused browsers sometimes generalise it.

Is anything sent to a server when I use this tool?

No. Your live User-Agent is read directly from navigator.userAgent in your own browser and parsed locally in JavaScript. Nothing about your browser or device is uploaded or logged.

Why would I need to check my User-Agent?

Common reasons: pasting it into a support ticket or bug report, verifying a bot (like Googlebot) is really who it claims to be, debugging browser-specific CSS/JS issues, or testing how your site behaves for a specific device without owning one.

Related tools — Site diagnostics