You’ll see all the properties of a detected device.Īndroid User Agents With the Client Hints support Mozilla/5.0 (Linux Android 10 K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Mobile Safari/537.36 If you’d like to learn more on these devices, just copy and paste the UAs to our User-Agent testing tool.
Here is a list of example User-Agents for different device types that can be detected. Interestingly bots and crawlers also come with their unique UAs. For example, a Chrome browser on an iPhone 6 will introduce itself using a different UA than a Safari browser on the same phone.Įvery device type, including phones, tablets, desktops, may come with its own UA that makes it possible to detect this device for any purpose. There are millions of User-Agent combinations given that UAs change with the software and hardware. We go into a lot more detail, and examine what makes up a UA, and how you can use user-agent parsing to your advantage, in our article User-Agent Parsing: How It Works And How Can It Be Used. Of course this requires using a device detection solution which translates UAs into understandable software and hardware information. The User-Agent tells the server what the visiting device is (among many other things) and this information can be used to determine what content to return. The User-Agent (UA) string is contained in the HTTP headers and is intended to identify devices requesting online content.
