See the HTTP headers your browser sends
Inspect a privacy-filtered view of the request headers received by this page. IPCheckHQ shows useful browser and language headers while excluding cookies and infrastructure-specific values.
Headers received for this request
Computed for this visit- User-Agent
- Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)
- Accept
- */*
- Accept-Language
- Not sent
- Accept-Encoding
- gzip, br, zstd, deflate
- Sec-CH-UA
- Not sent
- Sec-CH-UA-Mobile
- Not sent
- Sec-CH-UA-Platform
- Not sent
- Sec-Fetch-Site
- Not sent
- Sec-Fetch-Mode
- Not sent
How this signal works
Every page request includes HTTP headers describing acceptable content, languages, browser behavior and sometimes structured Client Hints. Servers use them for content negotiation, compatibility and security. The exact set depends on the browser, protocol, extensions and any proxy between you and the site.
Headers are only one view of a connection. A user agent can be changed and a proxy can add or remove fields. Security systems therefore compare header claims with JavaScript behavior, TLS characteristics and network context rather than assuming every value is authentic.
What this result cannot tell you
- This page intentionally omits cookies, authorization values and internal forwarding headers.
- A reverse proxy or content delivery network may normalize values before the application receives them.
- Headers can help explain a request but should not be treated as a permanent device identifier.
Use browser and network signals in your app
The verification API collects the broader fingerprint, binds it to the network request and returns the result to your backend.