| Your Browser | AppleWebKit |
| Browser Version | 537.36 |
| Your OS | |
| User Agent | Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com) |
The What Is My Browser tool helps you identify the browser information presented by your current web request. When you open the page, your browser sends a User-Agent header as part of the request. The tool reads that string and attempts to display useful details such as the browser family, browser version, operating system and complete user-agent value.
This information can be helpful when a support team asks which browser you are using, a website behaves differently on one device, or a developer needs a quick description of the current browsing environment. The result is based on information reported by the browser. It is not a malware scan, security certificate, device fingerprint or guarantee that the browser is fully updated.
Web browsers normally attach a User-Agent header to HTTP requests. This header contains a structured text string that may include product names, version tokens, operating-system information and compatibility identifiers. The server receives that value, and this tool passes it to a user-agent parser. The parser looks for known patterns and converts them into readable fields.
No website address needs to be entered because the tool examines the browser making the current request. To check another browser or device, open this tool directly in that browser or device. Copying a result from one browser does not describe every browser installed on the same computer.
The browser name identifies the product family inferred from the User-Agent string, such as Chrome, Firefox, Edge, Safari or another browser. Many browsers share rendering technology and include compatibility tokens for other products, so the parser must interpret the complete pattern rather than simply returning the first name it finds.
The version is the number exposed by the current browser request and recognised by the parser. Depending on browser privacy choices and User-Agent reduction, the reported version may be less detailed than the version shown inside the browser's About or Help screen. Use the browser's own settings when an exact build number is required.
The operating-system field is inferred from tokens included in the User-Agent string. It may indicate a general platform such as Windows, macOS, Android, iOS or Linux. The value may not include an exact edition, release or device model, and a browser can intentionally report a simplified platform for compatibility or privacy.
The full User-Agent string is the raw value supplied with the request. It is useful when documenting a compatibility problem because it preserves the tokens used by the parser. It can also explain why two parsing services display slightly different labels: each service may use different pattern rules or update schedules.
The page should be opened normally rather than viewed through a saved screenshot or copied result. If you switch browsers, refresh or reopen the tool in the new browser so that a new request is sent.
Browser and operating-system details give support staff a starting point when investigating display, login, upload or form problems. Include the page affected, the time of the issue, the steps that produced it and any visible error message. Browser information alone rarely explains the complete cause.
Developers can record the environment in which a defect appears and compare it with a working browser. This helps reproduce a problem and determine whether it relates to browser support, an extension, cached data, device settings or the website itself. Proper testing should still use real target browsers and feature-based checks.
On a shared or unfamiliar computer, the tool can provide a quick label for the active browser. It does not prove that the device is trustworthy. Avoid entering sensitive information on a device you do not control, even when its browser name and version appear normal.
The page reports parsed request information. A browser with a familiar name can still have unsafe extensions, weak settings or missing updates. Conversely, an unfamiliar or simplified label does not automatically indicate a security problem.
User-Agent strings developed over many years and contain compatibility wording that can be confusing. Some browsers include tokens associated with other browsers so websites will serve compatible content. Mobile apps and embedded web views may also use customised strings. Therefore, parsing is an informed interpretation rather than direct access to the browser's internal configuration.
Browsers increasingly limit some User-Agent details to reduce passive fingerprinting and improve privacy. Privacy extensions, automation tools, proxy services and manual settings can also modify the reported value. If the browser sends a generic or altered string, the tool can only analyse that supplied string and may return a broad or incorrect classification.
User-Agent parsers rely on recognition rules. A newly released or uncommon browser may not yet match those rules. Different tools can consequently report different names or versions for the same request. When accuracy is critical, compare the result with the browser's built-in About page and the device's system settings.
A browser product and its rendering engine are related but not identical. Several browsers may use the same underlying engine while providing different interfaces, privacy controls, update systems and features. A website may behave similarly in those browsers, but extensions, policies and release versions can still produce differences.
Do not assume that a browser is fully compatible merely because another browser using a similar engine works. Test the actual browser versions used by your audience and design pages with progressive enhancement and standards-based feature detection.
Modern browsers normally provide update controls in an About, Help or Settings section. Some install updates automatically and complete them after a restart. The version detected by this page can help you begin a check, but the authoritative update status should come from the browser's official update interface or your organisation's device-management system.
Download updates only through the browser vendor, the operating system or an approved application store. Unexpected pop-ups claiming that a browser is infected or urgently requires a special updater may be deceptive. This tool does not display third-party update packages and does not certify downloads.
The request may contain compatibility tokens, a modified User-Agent string or an uncommon product the parser does not recognise. Disable user-agent-changing extensions temporarily if appropriate, refresh the page and compare the result with the browser's About screen.
The browser may intentionally reduce exposed version details, or the parser may not understand a new version pattern. A simplified value does not necessarily mean that the browser is outdated. Check the installed version through the browser itself.
Compatibility settings, embedded browsers and privacy protections can affect platform tokens. Some devices deliberately report a desktop-style or generic value. Confirm the operating system in the device settings if the exact platform is important.
The User-Agent header may be empty, blocked or formatted in a way the parser cannot interpret. Reload the page without an unusual proxy or privacy override if appropriate. If the result remains empty, provide the browser name from its settings when requesting support.
A User-Agent string is normally sent to websites as part of browsing and does not contain your passwords or complete browsing history. However, browser and platform information can form one small part of broader device-identification techniques when combined with other signals. Use reputable websites and review browser privacy controls according to your needs.
No. The tool reads the User-Agent information attached to the request used to open its own page.
It can display a parsed version when that information is available, but it does not compare every browser build with a live vendor release database. Use the browser's official update screen for a reliable update check.
It can analyse the User-Agent sent by a mobile browser, although mobile browsers and in-app web views may provide simplified or customised details.
No. It only displays interpreted browser information. Device security also requires trusted software, timely updates, careful browsing, secure accounts and appropriate protection.
They may use different parsing rules, browser databases or labels. The raw User-Agent can be ambiguous, reduced or modified, so interpretations can vary.
What Is My Browser gives you a quick description of the current request's browser environment. It is most useful for support notes and compatibility troubleshooting when combined with the affected URL, error details and steps to reproduce the issue. Treat the reported browser, version and operating system as parsed information, and verify exact system or update details through the browser and device settings.