Headers Checker
HTTP headers websites see
Checking…
Echoes User-Agent, Accept, Accept-Language, Referer, and IP from a check request to this site.
How to use
- Open the page — your browser sends a check request and headers appear automatically.
- Read User-Agent, Accept, Accept-Language, Referer, and IP in the table.
- Click Copy all or Refresh after changing browser, language, or VPN.
FAQ
What headers does this show?
User-Agent, Accept, Accept-Language, Referer, and your public IP — the same header names servers log on incoming HTTP requests.
Where do the values come from?
Your browser sends them to our /api/my-headers echo route when the page loads. We return what the server received — not a simulated list.
Why is Referer empty?
Referer is sent when you navigate from another page. Direct visits, strict Referrer-Policy, or privacy modes may send no Referer header.
Why is Accept */*?
This check uses fetch(), which often sends Accept: */*. Top-level page navigations usually send text/html preferences — the value here reflects the check request.
Same as HTTP Header Checker?
No. [HTTP header checker](/tools/http-header-checker) inspects response headers from any URL you enter. This page shows **your browser's outgoing request headers** to this site.
Is my IP stored?
IP is read to display the address websites see, using the same routing as other My Network tools — not stored in a tracking profile.
Introduction
Headers Checker echoes the HTTP request headers your browser sends when the page runs its check — User-Agent, Accept, Accept-Language, Referer, and your public IP. These are the same fields access logs, CDNs, and apps parse on every visit.
Developers use header checks to debug locale routing, bot rules, and referrer policies. Privacy-conscious users use them to see what leaks before cookies or JavaScript even run.
Headers explained
| Header | What it tells sites |
|---|---|
| User-Agent | Browser, engine, and OS tokens |
| Accept | Content types the client prefers |
| Accept-Language | Language priorities for localization |
| Referer | Previous page URL when navigation sends it |
| IP | Routable address of your connection (via server) |
IP is not an HTTP header in the strict sense but is always available to servers — shown here because sites combine it with the headers above.
Check request vs normal browsing
This tool triggers a same-origin API request when you open or refresh the page. Accept and Referer may differ slightly from a full document navigation (for example Accept may be */* on fetch). User-Agent and Accept-Language typically match your browser profile.
Common use cases
- Support tickets — copy User-Agent and Accept-Language for reproduction steps.
- Locale QA — confirm Accept-Language matches expected market before geo tests.
- Referrer debugging — see if Referer is stripped by policy.
- VPN check — compare IP with what is my public IP.
Best practices
- Refresh after changing browser language or VPN settings.
- Pair with what is my user agent for a parsed UA breakdown.
- For arbitrary URL response headers, use HTTP header checker.
- For full environment snapshot, open device info.