Skip to content
OneKitly
Sign up · Sign in

Browser and User-Agent detector

Your raw User-Agent string, and what it decodes to: browser, rendering engine, operating system, device type — plus the screen, language and capability values any page can read without asking.

Related tools

All Web & network tools →
Random User-Agent GeneratorGenerate realistic desktop, mobile and bot User-Agent strings for testing and scraping setups.Flip ImageFlip an image horizontally (mirror) or vertically, and download the result at full resolution.HTTP Status Code ReferenceSearch and browse every standard HTTP status code by class, with its name and a one-line description.My IP addressYour public IP address, its version (IPv4 or IPv6) and the city-level location the network gives away — plus what your browser reports, so a mismatched time zone reveals a VPN. Nothing is stored.Htaccess redirect generatorGenerate ready-to-paste Apache .htaccess rules for the common jobs: 301/302 redirects (single or regex), forcing HTTPS, forcing www or non-www, blocking IP addresses, removing trailing slashes, image hotlink protection and GZIP compression. Pick a rule, fill the blanks and copy — remember to back up your .htaccess first.Subnet calculator (CIDR)Compute the subnet mask and number of usable hosts from a CIDR prefix.ASCII code converterConvert text to ASCII/Unicode code points and back.Number base converterConvert numbers between all 35 bases, exactly, with two's complement.

Browser and User-Agent detector is free to use as often as you like, directly from this page. It covers browser, rendering engine, operating system, device type — plus the screen, language and capability values any page can read without asking — adjust any of them and the result follows immediately.

How to use it

  1. Open the tool — no signup or install needed.
  2. Enter your input or adjust the available options.
  3. Get your result instantly, then copy or download it.

Frequently asked questions

What is Browser and User-Agent detector?

Your raw User-Agent string, and what it decodes to: browser, rendering engine, operating system, device type — plus the screen, language and capability values any page can read without asking.

What does it take into account?

It factors in browser, rendering engine, operating system, device type — plus the screen, language and capability values any page can read without asking. Change any of them and the output follows immediately.

When would I actually use this?

Getting usable data out of something that was never meant to be parsed: pulling every address out of a pasted thread, turning a column of lines into a JSON array or an SQL IN clause, renaming a hundred identifiers from snake_case to camelCase in one pass.

What is the most common mistake?

Trusting an extraction to be exhaustive. A pattern that catches every address in the sample will still miss the one wrapped across a line break, the one written with a display name, and the one an email client turned into a link — count what came out against what you expected before you use the list.

How is Browser and User-Agent detector different from Random User-Agent Generator?

They sit next to each other but answer different questions: Random User-Agent Generator is the one to open when you need it to generate realistic desktop, mobile and bot User-Agent strings for testing and scraping setups. Pick whichever matches what you're starting from — both are free.

Is there a tool for the next step?

Flip Image is the closest one after this: Flip an image horizontally (mirror) or vertically, and download the result at full resolution.

What else is worth having open alongside it?

HTTP Status Code Reference and My IP address — they come up in the same task often enough to be worth a second tab.

Where do the figures come from?

Extraction runs on patterns, not on a parser: it recognises the common shapes of an address, a URL or an IP rather than validating them against their specification. That is the right trade for a paste, and the wrong one for input you are about to store.

Further reading

All guides →
GuideHTTP Status Codes Explained: The Ones That Actually Get Confused301 against 308, 302 against 307, 401 against 403, 404 against 410 — plus what Retry-After on a 429 or a 503 actually promises. The pairs where picking the wrong code changes behaviour, not just wording.ExplainerHow Subnet Masks Work: CIDR, Network Bits, and Usable HostsUnderstand how a subnet mask splits an IP address into network and host parts, what /24 means, and how to count usable hosts.How-toHow to Read Binary and Convert It to Decimal and HexLearn how binary place values work and convert binary to decimal and hexadecimal by hand, with clear worked examples.How-toHow to Write a Cron Expression: Five Fields and the OR Rule Nobody MentionsMinute, hour, day of month, month, day of week. The traps are that a step is a stride through a range and not an interval, and that the two day fields are combined with OR — so 0 0 1 * 1 fires on the 1st and on every Monday.ExplainerHow Unix File Permissions Work: Reading 755 Without GuessingRead is 4, write is 2, execute is 1, and each of the three digits describes a different party. The part most explanations get wrong is what the execute bit does on a directory — it grants traversal, not the right to run anything.ExplainerBig O Notation for Beginners: O(1), O(n), O(n squared), and O(log n) ExplainedBig O describes how an algorithm's work grows as input grows. Here is what O(1), O(n), O(n squared), and O(log n) mean and why the difference matters.