Is your browser sharing your history? Our referrer leak test shows exactly what URLs and private data you are leaking to other websites.
AI Overview
An HTTP Referer Leak happens when your browser tells a new website the exact URL of the page you just left. This can expose private search terms, session tokens, or personal info. Setting a strong Referrer-Policy (like no-referrer) is essential for modern web privacy and security.
Leak Status
✅ NO LEAK
Detected Header
None (Direct Visit)
[HTTP Header Capture]
> Analyzing Referer header...
> No referrer data sent. User privacy is high.
An HTTP Referer is a header sent by your browser to a web server. It contains the address of the webpage that linked to the current site. While useful for analytics, it is a privacy risk because it tells the owner of the new site exactly where you were browsing previously.
Pro Tip: If your URL contains sensitive info (like ?reset_token=123), a referrer leak will send that secret token to any third-party script or external link on that page.
Leaks occur during cross-domain navigation. If you click a link from Site A to Site B, Site B sees Site A’s URL. Similarly, every third-party ad or tracker on a page automatically gets your full URL through this header unless you block it.
To secure your data, we recommend using these privacy-first policies on ZKB Tracking:
<a> tags to stop leaks on specific links.Does a VPN stop referrer leaks?
No. A VPN hides your IP, but the referrer header is sent by your browser. You must change your browser settings or use extensions to stop it.
What is the difference between noreferrer and noopener?noreferrer stops the URL leak. noopener prevents the new site from controlling your original tab (stops tab-nabbing attacks).
Is my search history leaked?
If you click a link from a search engine result page, the search terms are often visible in the referrer URL unless the search engine hides them.