Browser identity
Reports the browser and version token exposed to websites so you can compare it with the product's official update screen.
Browser settings review
Browser Security Test: Observable Settings, Clearly Scoped
A browser security test on a normal webpage has strict limits. This page can inspect selected web-platform signals—such as cookie support, privacy requests, browser identity and an automation flag—but it cannot inspect the browser installation, extension code or files on your device.
The live result therefore reports observations, not a security grade. That distinction matters: presenting an untested malware scan, blacklist result or arbitrary trust score would create confidence that the browser has not earned.
Observable browser settings
These signals help you review configuration, but none is a complete security verdict.
- Reported browser
- Loading...
- Cookies
- Disabled
- Privacy requests
- No privacy request exposed
- navigator.webdriver
- Not exposed
- Malware / extensions / patches
- Not tested
Copied and printed output omits IP addresses, the full User Agent, exact versions, fingerprint hashes, and precise location.
What this browser security test checks
Cookie and privacy-request APIs
Reads whether cookies are reported enabled and whether Do Not Track or Global Privacy Control is exposed. These are configuration clues, not vulnerability scans.
Automation disclosure
Reads navigator.webdriver. An exposed value can be useful for test automation diagnosis, but a missing value does not prove a human user or safe browser.
What a result means
Cookies enabled is not inherently good or bad
Many sites require first-party cookies for sessions. Privacy depends on cookie scope, expiry, partitioning and third-party policies that this single API does not fully describe.
Privacy requests depend on site support
DNT and GPC express preferences. Their presence does not technically block tracking, and websites or applicable laws determine how they are honored.
Version data needs vendor verification
A reported major version is useful context. Only the browser's signed update mechanism can confirm whether the installed build is current for its release channel.
Security checks a webpage cannot perform here
- No malware, antivirus, executable, download or local-file scan is performed.
- Installed extensions and their permissions are not enumerated or audited.
- Operating-system patches, certificate stores, account compromise and router security are outside this test.
- A webpage cannot guarantee that every browser sandbox or mitigation is working correctly.
A practical browser security routine
- 1Confirm the browser family, then use its official update screen to install pending updates.
- 2Review installed extensions and remove those you no longer use or do not trust.
- 3Enable the browser's built-in phishing, download and tracking protections where appropriate.
- 4Use operating-system security tools for malware and patch checks; do not substitute a webpage for them.
Browser security test FAQ
Can a website scan my browser for viruses?
A normal sandboxed webpage cannot perform a trustworthy full-device malware scan. Claims to do so without a separately installed, trusted security product should be treated cautiously.
Does a green setting mean my browser is secure?
No. It means only that the specific observable setting matched the stated condition. Security depends on updates, extensions, the operating system, accounts and browsing behavior.
Why is there no single security score?
A score would require validated weights and many signals unavailable to a webpage. BrowserCheck shows the evidence and its scope instead of assigning an unsupported grade.
Check a specific browser surface
Use the privacy, fingerprint, version and leak tests to inspect their narrower evidence separately.