Browser security
Compatibility & evidence
The evidence desk

Inspect supplied evidence.

Paste response headers or open a structured evidence file. Check which settings are present, which need attention, and where the supplied pages disagree. Analysis runs on this device; it does not visit your website or prove that a protection works in production.

One response at a time

Read the headers

Response headers are instructions a website sends to the browser. Paste a set below and ControlCurrent will look for recognised security settings. It does not visit the URL, save the text, or send it anywhere. Replace cookie values and other secrets with REDACTED first.

Which browsers does this need to work in?

Add a browser plan to show compatibility beside each header finding. A recognised declaration does not prove that a browser enforced it.

Create a browser plan

Header review also works without a browser plan.

Paste response headers only. Login credentials such as Authorization and Cookie are refused. If redirects produced several blocks, only the final response is checked.

Advanced: review evidence from several pages and signed reportsUse this only when you already have a structured evidence file or an approved CI report.
Advanced check

Review evidence from several pages

Load a structured JSON file when you need to compare headers, page markup, local resource checks, request information, or passkey settings across several parts of an application. ControlCurrent analyses the file on this device without running the markup or loading its resources. The exported report leaves out the original page content and resource bytes.

Or paste and edit JSON

Use non-identifying labels instead of URLs or personal data. Remove secrets, route locations, unnecessary page content, passkey challenges, user IDs, and relying-party IDs before loading the file.