What This Browser Checker Shows
Digital Domain Kit's What is My Browser tool gives you a quick server-side snapshot of the browser name, browser version token, and operating-system family detected from the request that loaded the page. It is useful when a website, help desk, testing checklist, or bug report asks what browser you are using and you need a simple answer without opening developer tools.
The tool is intentionally narrow. The visible result is a three-column table with Your Browser, Browser Version, and Operating System. There is no manual input box, no file upload, no device scan, no extension check, and no separate fingerprint report. The current production implementation calls a PHP helper named getBrowser() during page rendering, reads the incoming User-Agent header, matches a few common tokens, and prints the parsed values in the table above the page description.
That makes the page fast and easy to understand, but it also means the answer is only as reliable as the user-agent string that reached the Digital Domain Kit server. Modern browsers, privacy settings, proxies, testing tools, bots, in-app webviews, and command-line clients may send incomplete, frozen, unusual, or intentionally changed user-agent strings. Treat the result as a practical diagnostic hint, not as a guarantee of a device's real identity.
How To Use It
- Open What is My Browser in the browser or app window you want to check.
- Read the Your Browser cell for the detected browser family, such as Google Chrome, Apple Safari, Mozilla Firefox, Opera, Edge, Internet Explorer, Netscape, or Unknown.
- Read the Browser Version badge for the version token extracted from the same user-agent string. If the parser cannot find a version, it shows a question mark.
- Read the Operating System cell for the detected platform family. The verified helper currently reports
windows,mac,linux, orUnknown. - If you need to share the result, select the table text and copy it with your browser or operating-system copy shortcut. The inspected page does not include a dedicated copy button for this table.
- If you need the full user-agent string or language header, open the related User Agent Finder instead. This browser checker does not display those extra fields.
What The Tool Reads
The active implementation reads $_SERVER['HTTP_USER_AGENT'] on the Digital Domain Kit server. If the header is missing, it uses an empty string and falls back to Unknown values. The helper then performs regular-expression checks against that string. Platform detection looks for Linux, Macintosh or Mac OS X, and Windows or Win32 tokens. Browser detection looks for older Internet Explorer MSIE tokens, Firefox, Opera's OPR token, Chrome, Safari, Netscape, Edge, and Internet Explorer's Trident token.
After choosing a browser token, the helper builds a version-matching pattern from Version, the chosen browser token, and a fallback word. It then extracts a version-like value when one appears after the matched token. In a live check with a Chrome-on-Windows user-agent string, the table showed Google Chrome, 121.0.0.0, and windows. In a live check with a Safari-on-macOS user-agent string, it showed Apple Safari, 17.2, and mac. In a command-line request with no familiar browser token, it showed Unknown, ?, and Unknown.
The result is produced on page load. There is no Convert, Detect, Refresh, or Analyze button inside the tool. To check another browser profile, another device, an in-app browser, or a custom testing client, load the page from that environment. To recheck the same environment after changing privacy settings, user-agent overrides, browser version, or compatibility mode, reload the page so the server receives a fresh request.
Inputs, Outputs, And Limitations
| Area | Verified behavior | Important limitation |
|---|---|---|
| Input | The incoming User-Agent request header received by the server. |
You cannot paste a custom user-agent into this page. Use a browser profile, developer setting, proxy, or test client if you need to send a different string. |
| Browser output | A simple browser family name selected by token matching. | New, uncommon, reduced, spoofed, or webview-specific strings may be simplified or marked Unknown. |
| Version output | A version-like token extracted from Version or the matched browser token. |
The value may not represent every engine, compatibility, app-shell, or security-patch detail. |
| Operating system output | One broad family: windows, mac, linux, or Unknown. |
The current table does not show detailed OS releases, device models, CPU architecture, mobile versus desktop, or tablet status. |
| Accept-Language | The What is My Browser table does not display the Accept-Language header. |
Use User Agent Finder when you need to see the language preference header that reached the site. |
| Copying | The result appears as selectable table text. | There is no inspected one-click copy control for this table. Browser selection, clipboard permission, and device behavior determine manual copying. |
About User-Agent Accuracy
A user-agent string is request metadata, not a proof of identity. The MDN User-Agent reference describes it as a string sent by the client that can identify the application, operating system, vendor, and version. The same general idea is formalized in HTTP Semantics, which defines user-agent information as product identifiers and comments sent by the requesting software.
In real troubleshooting, the string can still be misleading. Some browsers intentionally reduce user-agent detail to limit passive identification. Some compatibility modes include older tokens for legacy sites. Chromium-based browsers may include Chrome-like text even when the visible app is another browser. Automated clients can set almost any value. Corporate proxies, privacy tools, and testing frameworks can also alter what the server receives. For that reason, this page is best used to answer "what does this site see from my current request?" rather than "what is every true property of my device?"
The page also does not use browser feature tests. It does not check whether a specific JavaScript API, codec, CSS feature, storage API, camera permission, location permission, or WebGL capability is available. If a support issue depends on feature support, use this page as a starting note and then test the exact feature in the affected browser.
Accept-Language Handling
Accept-Language deserves a separate note because people often expect a browser checker to show it. The HTTP Accept-Language header can describe language preferences such as en-US,en;q=0.9, but the current What is My Browser page does not read or display that value in its three-column result table. Live requests with different Accept-Language values still produced the same table structure because the visible tool is driven by user-agent parsing, not language preference parsing.
If your goal is to debug localization, region defaults, translated content, or server-side language negotiation, this page is not enough on its own. Use User Agent Finder for the request-header view, and compare the browser's language settings with the value shown there. Remember that Accept-Language is a preference header, not a verified location, citizenship, keyboard layout, or identity attribute.
Privacy And Data Handling Notes
This tool does not ask you to upload a file or type personal information. The page renders from the ordinary HTTP request that your browser already sends when visiting a website. The inspected implementation passes the parsed result to a Blade view and displays it in the table. It should not be described as browser-only processing, because the parsing happens on the Digital Domain Kit server after the request arrives.
A user-agent string is still part of request metadata. It can reveal broad details such as browser family, browser version token, operating-system family, and sometimes mobile or app context. The page also loads normal site assets and Google Analytics is present in the live HTML. Do not treat the tool as anonymous browsing, a privacy audit, a fingerprint blocker, or a security scan. It simply shows a small parsed subset of one request header. If you want to understand broader browser exposure, compare it with a dedicated fingerprint or header-audit workflow and review the site's privacy policy.
Example Results
Here are real live checks made against the public page during review. A request using this Chrome-style header:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/121.0.0.0 Safari/537.36
returned Google Chrome as the browser, 121.0.0.0 as the browser version, and windows as the operating system. A Safari-style request using:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.2 Safari/605.1.15
returned Apple Safari, 17.2, and mac. These examples show the page's main strength: it can turn common browser user-agent strings into a concise support-friendly table. They also show why the table should not be overread. The Windows example does not show the exact Windows release, and the Safari example does not describe the device model or every WebKit detail.
Troubleshooting
| Problem | Likely cause | What to try |
|---|---|---|
| The browser says Unknown. | The user-agent string is missing, unfamiliar, reduced, spoofed, or sent by a non-browser client. | Reload from the actual browser you want to check, disable user-agent overrides, or inspect the full string with User Agent Finder. |
| The version is a question mark. | The parser found a browser family but did not find a matching version token in the expected pattern. | Check the full user-agent string, then confirm the browser version in the browser's About page if exact versioning matters. |
| The operating system is too broad. | The tool only maps broad Windows, Mac, and Linux tokens. | Use the browser or operating-system settings page for detailed OS build, architecture, and device-model information. |
| The result changes between apps on the same device. | In-app browsers, embedded webviews, and privacy modes can send different user-agent strings. | Open the page from the exact app or browser where the website issue occurs. |
| You cannot copy the result with one click. | The inspected What is My Browser table does not include a copy button. | Select the table text manually, or use User Agent Finder if you need a copyable full user-agent field. |
Related Tools
Use User Agent Finder when you need the full user-agent string, Accept-Language header, and additional parsed request details instead of only the three-column browser table.
Use Browser Fingerprint Audit when you want a broader browser-privacy check. Keep the distinction clear: What is My Browser only parses a request header; it does not measure fingerprint uniqueness by itself.
Use IP Information when the question is about the visible network address and approximate network metadata, not the browser family.
Use What Is My IP for a simpler IP-address check when a support team asks what public address the site sees.
Use HTTP Status Code Checker when you need to test what status code a URL returns from the server side rather than identifying your current browser.
Editorial And Technical Notes
This page is built and maintained by Digital Domain Kit. The documentation was last reviewed on September 16, 2026 against the live public page and the production Laravel source for WhatsMyBrowserController, resources/views/modules/tools/whats-my-browser/view.blade.php, and the getBrowser() helper. The verified method is server-side PHP parsing of the incoming User-Agent header followed by a Blade-rendered table with browser, version, and operating-system fields.
To report a mismatch between this documentation and the live tool, use the Digital Domain Kit contact page. For technical background on the request headers discussed here, see MDN's User-Agent and Accept-Language references.