← Back to all tools

User Agent Checker

Inspect your browser’s reported user agent or parse a custom string.

Inspect this browser

Read the user agent reported by your current browser.

No URL lookup is needed.

Results are estimates based on reported values, not verified hardware identity.

What you can inspect

Raw User-Agent

Original reported string.

Browser

Parsed name and version.

Platform

Reported operating system.

Engine

Inferred rendering family.

Device class

Estimated category (desktop, mobile, tablet).

Bot signatures

Heuristic pattern matches.

Know where the data comes from

  1. 1
    Browser valuesRead from navigator APIs in your browser (e.g. navigator.userAgent).
  2. 2
    Parsed fieldsExtracted using a user agent parser with best-effort estimates.
  3. 3
    Request detailsServer-observed metadata, when requested (e.g. IP, headers).

Custom strings do not reveal their owner’s IP or request headers.

Frequently asked questions

Why can the OS version look outdated?

Browsers freeze or reduce the OS token. macOS 10.15.7 in a string is the reported token, not proof of the installed release. Windows NT 10.0 is shared by more than one Windows release. Feature detection is preferable when an application needs to know what the browser can do.

Does parsing identify a real bot?

No. A known token produces “Known signature matched”. Anything else is “No known signature matched”. Neither result confirms a person or a legitimate crawler.

What happens to a custom string?

Only that string is parsed. The result does not include your IP, Client Hints, referrer, language or request method.

What is included in a shared report?

A link is created only after you review the fields. The saved report keeps the original string and parsed fields. IP and the HTTP Referer are excluded. The link expires after 24 hours and shows that saved report. It does not detect the viewer’s browser.