Browser Information

This page answers the simple question "what browser am I using?" and then goes a step further. Alongside the browser name and version it shows the engine underneath, your operating system, language and timezone settings, and a live check of which modern web features your browser supports. It is a quick, honest snapshot of the environment every website you visit is working with.

Identifying a browser reliably is harder than it sounds, because the user-agent string is easy to change and full of legacy tokens. This test uses it as a starting point and then confirms the answer with capability checks that are much harder to fake.

• Parse the string. The browser, version, engine and OS are extracted from the user agent, handling the quirks of Edge, Opera, Samsung Internet and the rest.
• Probe real features. Support for Service Workers, WebAssembly, WebGL, WebRTC and more is tested by asking whether each API exists in your browser right now.
• Cross-check. If the string claims one browser but the feature set clearly belongs to another, the features win. This is why simply spoofing a user agent does not fool a careful detector.

Most browsers on the desktop are not built from scratch. Edge, Opera, Brave, Vivaldi and Samsung Internet all run on Chromium, and Chromium uses the Blink engine, so pages behave almost identically in all of them and their user agents all contain a Chrome/ token. What separates them is a small marker appended to the string: Edg/ for Edge, OPR/ for Opera. Brave omits its own token and reports plain Chrome, which is deliberate.

That is why the engine field here will read the same for several different browsers, and why a site that only looks at the engine can mislabel you. The real differences sit above the engine, in what each vendor adds: Brave’s shields, Edge’s own APIs, Opera’s built-in proxy. Firefox reports Gecko and Safari reports WebKit, so those two stand apart from the Chromium group entirely.

The feature list is more than trivia. For developers it decides whether a site can rely on a given API or needs a fallback, and it is why a page can offer a modern chat widget to one visitor and a plain form to another without asking. For you, it is a way to see how modern and capable your browser is, and whether privacy settings, an extension or an old version are quietly disabling things.

It also feeds into fingerprinting. The exact set of features a browser supports, combined with its version and platform, helps narrow down which browser you are, one more signal on top of everything else. A browser kept up to date and left near its defaults tends to share its feature profile with millions of others, which is the safer place to be. The fingerprint test shows how all these signals stack up, and the client hints test shows the newer channel browsers use to report the same details.

Your language preferences and timezone are set once and then sent, or readable, everywhere. They are genuinely useful, a site can greet you in the right language and show times that make sense, but they are also quietly revealing. A rare language ordering or an unusual timezone narrows the crowd you blend into, and the timezone is one of the values that changes least often, which is what makes it worth a fingerprinting script’s attention.

The cookies and online indicators are more practical. They tell you whether this page can store a cookie and whether your browser currently believes it has a network connection, which is reported by navigator.onLine and can be wrong. If cookies show as blocked and you did not expect that, the storage test will show you exactly which storage mechanisms are affected, and the timezone test drills into the clock.

None of these details identify you by name, and most are shared by huge numbers of people. The privacy question, as always, is about combination. Browser, version, engine, platform, language list, timezone and feature support are each common on their own, but stacked together they form a recognisable profile that helps trackers tell one visitor from another without a single cookie or any local storage. The engine and platform do most of the narrowing, splitting visitors into a few large groups, and the language list and timezone cut each group down again.