Cookie headers are hidden for privacy. Some headers are added by Cloudflare (the cf-* ones) before the request reaches this page.
What is shown above?
Every line is one HTTP header your browser (or the layers between your browser and our server) sent with the request that loaded this page. Each header is a name and a value. Browsers send a standard set automatically; some are added by proxies and CDNs along the way.
Headers worth knowing
- user-agent — identifies your browser, OS, and device. Most-checked header for client fingerprinting. See the User Agent Lookup tool.
- accept-language — the languages your browser prefers, in priority order. Many sites use this to localize content.
- accept-encoding — which compression formats your browser can read. Almost always includes
gzipandbr. - cf-connecting-ip — your true public IP, added by Cloudflare. Servers behind Cloudflare use this instead of the TCP source.
- cf-ipcountry — your country, looked up from your IP by Cloudflare.
- referer — the URL of the page you came from, if any. Browsers omit this for direct loads.
Why this matters for proxies and scraping
The headers your client sends are how target sites profile your traffic. Scrapers that send minimal or mismatched headers (no accept-language, no referer, an old user-agent) stand out from real browsers. Replicating the full header set a real browser sends is one of the cheapest ways to make a scraper look more human.
When developing or debugging an HTTP client, comparing what your code sends versus what a real browser sends (using this page) is a fast way to identify the gap.
Need Proxies?
Dedicated and shared datacenter proxies across the USA, Spain, and Italy. Instant activation.