What is my user agent?

See your browser's User-Agent string and its parsed browser, operating system, and device details. Copy the raw string for a bug report, or paste another User-Agent to identify the client it describes.

Reading your browser…

Send a useful browser report

Copy support summary gives you the detected browser, operating system, reported device and original User-Agent in one block. Paste it into a bug report when a page behaves differently on your device. Version and model details appear only when the supplied evidence includes them.

You can also paste a string from a server log to identify that client. Back to my browser returns to the request sent by your own browser.

Why a User-Agent contains several browser names

Browsers include compatibility tokens, so a Chrome string may also contain Mozilla, AppleWebKit, and Safari. Those names do not mean you are running several browsers. The parser considers the combination of tokens to identify the client.

Why some details are unknown

Browsers can reduce version and device information in their User-Agent, and clients can change the string they send. A missing device model may simply be absent from the input. Browser and bot labels describe the supplied string rather than proving a device or person's identity.

Build a User-Agent checker

Pass the browser’s or a pasted User-Agent string to the SDK on your server. Display the returned browser, OS, device, and bot fields with the original string.

  1. Read navigator.userAgent in the browser or accept a pasted string.
  2. Pass that string to your server’s useragent SDK call.
  3. Treat parsed labels as descriptions of the supplied string, rather than proof of identity.

Installation steps are included in each example. Set PARSEAPI_KEY on your server. Swift and Kotlin use an app key restricted to your app ID.

// npm install @parseapi/sdk@1.14.0
import { parseAPI } from '@parseapi/sdk';

// Set PARSEAPI_KEY on your server.
const parse = parseAPI();

// Paste a browser's User-Agent here, or pass it from your request handler.
const useragent = 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 Chrome/131.0.0.0 Safari/537.36';
const row = await parse.useragent(useragent);
console.log({ useragent: row.useragent, browser: row.browser?.name ?? null,
  os: row.os?.name ?? null, device: row.device?.type ?? null, bot: row.bot });

Read the browser’s User-Agent before sending it to your server

browser-user-agent.js
const useragent = navigator.userAgent;
console.log(useragent);
// Pass this string to your server’s parse.useragent(useragent) call.

User-Agent API documentation

How do I find my User-Agent?

The page reads the header sent by your browser and displays the raw string. Copy it for a bug report or paste a different string into the parser.

Why does Chrome’s User-Agent also say Mozilla or Safari?

Browsers retain compatibility tokens used by websites. The combination of tokens identifies the client; those names do not mean several browsers are running.

Why is my device model or version unknown?

Browsers can reduce the details they expose. A parser cannot recover a model or version that the supplied string does not contain.

Can a User-Agent be changed or faked?

Yes. Clients can send a different string. Browser, device, and bot labels describe that claim and should not be used as proof of identity.

Is a User-Agent the same as an IP address?

No. It describes the requesting software. The IP address is the network address used for the connection.