Reading a user agent
Start with your own
The box is filled with your browser's user agent. The four results show browser and version, engine, operating system and device type.
Paste another
Copy a string from a web server log, an analytics export, a form plugin's submission details or a support email, and paste it over yours.
Read the device line
Desktop, mobile or tablet for ordinary browsers. Crawlers and automated clients are reported as a bot.
Treat it as a hint
Browsers can change or reduce the string, so use the result to understand a report, not to make security decisions.
Example: who filled in the enquiry form?
A builder's merchant (fictional) receives two enquiries and one suspicious submission through its website form, and the form plugin records each user agent. The first is Microsoft Edge on a Windows PC, the second Safari on an iPhone. The third identifies itself as an automated crawler, which explains the nonsense in the message field.
Windows is reported as 10 or 11 because modern browsers send the same Windows version for both.
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/141.0.0.0 Safari/537.36 Edg/141.0.0.0 Mozilla/5.0 (iPhone; CPU iPhone OS 18_6 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/18.6 Mobile/15E148 Safari/604.1 Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)
Edge 141.0.0.0 Blink Windows 10 or 11 desktop Safari 18.6 WebKit iOS 18.6 mobile Unknown Unknown Unknown Bot (Googlebot)
Why user agents are less precise than they used to be
Browsers have deliberately reduced the detail in user agent strings to make users harder to fingerprint. Chrome now freezes parts of the string, so the minor version numbers and some operating system details are fixed values rather than the real ones. Safari has long reported a frozen macOS version. The parser reads what is there, but the string may simply not contain the detail you want.
Anyone can also set any user agent they like. Scrapers often pretend to be ordinary browsers, and some privacy tools make browsers look like something else. A user agent is a claim, not a proof.
Questions people ask
What is a user agent string?
It is a line of text a browser or other client sends with every web request to describe itself, typically naming the browser, its version, the rendering engine and the operating system. Websites and analytics tools use it to adapt pages and count visitors by device. It is visible in server logs and many form plugins.
Why does every browser's string start with Mozilla?
For historical reasons. In the 1990s websites sent better pages to Netscape, whose code name was Mozilla, so other browsers copied the prefix to receive them too. The habit stuck, which is why Chrome, Edge and Safari strings all start with Mozilla/5.0 and mention engines they do not use.
Can I tell if a visitor is a bot from the user agent?
Only for honest ones. Search engine crawlers and many monitoring services identify themselves, and the parser labels those as bots. Plenty of automated traffic copies an ordinary browser's string instead, so a normal-looking user agent does not prove a human was there.
Is my user agent sent anywhere by this page?
No. The page reads your browser's user agent locally to fill in the box, and the parsing happens in your browser. Nothing is sent to Map Extract or stored.
Where your data goes
Your browser's user agent is read by the page and parsed locally, as is anything you paste. Nothing is sent to Map Extract or anywhere else.
Checked against the tool on