Browser Privacy Anti Tracking: 7 Quick Ways to Block

Alright, let’s cut to the chase. You’re reading this right now, and while you are, hundreds of tracking scripts are silently recording every click, every scroll, every keystroke you type into your address bar. No, I’m not being dramatic. This is literally what happens every time you load a web page.

Here’s the thing — most people don’t realize how exposed their browser really is. Every single website you visit deploys anywhere from 5 to 15 tracking scripts in the background. Google Analytics, Facebook Pixel, Hotjar heatmaps, DoubleClick ad networks, and dozens more. They’re collecting your browsing data, building interest profiles, harvesting device information, and sometimes even grabbing your approximate location. All of that gets sold to advertisers or used to build eerily targeted ad campaigns.

Now, why should this matter if you’re a NOC engineer, sysadmin, or anyone working in IT? Because an unsecured browser is an attack vector. If you can be tracked through your browser, that means scripts are running without your knowledge. And if scripts can run without your knowledge, malicious ones can too. This isn’t just about personal privacy — it’s about your attack surface. Credentials captured through browser-based keyloggers, session tokens leaked through insecure extensions, DNS queries exposing your infrastructure access patterns — these are real threats in production environments.

Okay, enough doom and gloom. Let’s get to the actual fixes. Here are 7 quick wins you can implement right now.

1. Disable Third-Party Cookies Immediately

This is ground zero. Third-party cookies are cookies planted by domains different from the one you’re actually visiting. You go to an e-commerce site, but a script from facebook.com drops a cookie in your browser. That cookie follows you across the entire internet, building a profile of everything you do online.

The fix is dead simple. In Chrome: navigate to chrome://settings/cookies and select “Block third-party cookies.” In Firefox: go to about:preferences#privacy, enable Enhanced Tracking Protection, and set it to Strict. Brave blocks them by default — you’re already covered if you’re using Brave.

Chrome: chrome://settings/cookies → Block third-party cookies
Firefox: about:preferences#privacy → Enhanced Tracking Protection → Strict
Brave: Shields panel → Trackers & ads blocking → Aggressive

Quick tip: if a website breaks after enabling this, you can whitelist specific domains. But don’t whitelist entire analytics domains — only whitelist what you absolutely need for the site to function.

2. Install uBlock Origin — Nothing Else

Seriously, don’t install any other ad blocker unless it’s uBlock Origin. Here’s why: many so-called “free” ad blockers are actually paid by advertisers to allow certain ads through. uBlock Origin is fully open source, has zero paid whitelists, and is significantly lighter on CPU and RAM than the competition.

Install it from the Chrome Web Store or Firefox Add-ons. Once installed, click the uBlock icon and hit the gear icon to open the Dashboard. In the Filter Lists tab, enable every relevant list: EasyList, EasyPrivacy, Peter Lowe’s Ad Server list, and Fanboy’s Enhanced Tracking List. Hit Apply and you’re done.

uBlock Origin Dashboard:
- Filter lists → Enable: EasyList, EasyPrivacy, Peter Lowe, Fanboy's Enhanced
- My filters → Add custom rules if needed
- Settings → Enable: I'm an advanced user (for more control)

What makes uBlock Origin special is the per-page control. Click the icon on any page and you’ll immediately see which scripts are blocked, which elements are hidden, and you can toggle blocking on a per-domain basis. Incredibly useful when you need to debug a specific site while maintaining your privacy posture.

3. Use Secure DNS — Cloudflare 1.1.1.1 or NextDNS

This one flies under the radar for most people. Your DNS is like the phone book of the internet — and if your DNS queries aren’t encrypted, your ISP can see every single website you visit. Many ISPs actively log DNS queries and sell that data to third parties.

The solution: use DNS over HTTPS (DoH) or DNS over TLS (DoT). Easiest option is Cloudflare’s 1.1.1.1. For more power, NextDNS lets you block trackers directly at the DNS level — it’s basically Pi-hole without needing to spin up your own server.

Cloudflare DoH:
Chrome: chrome://settings/security → Use secure DNS → With Cloudflare (1.1.1.1)
Firefox: about:preferences#privacy → Enable DNS over HTTPS → Max Protection

NextDNS (more comprehensive):
1. Sign up at https://nextdns.io
2. Go to Configure → copy DoH link
3. Paste into your browser DNS settings

NextDNS is genuinely excellent. You can block trackers by category, block malware domains, and even block specific domains by name. For NOC engineers who don’t want to bother setting up Pi-hole on a VPS, this is a solid alternative that gets the job done.

4. Tame JavaScript with NoScript or uMatrix

JavaScript is a double-edged sword. It makes the web interactive, but it’s also the primary vehicle for tracking. Many trackers run entirely on JavaScript — no cookies needed, no fingerprinting needed, just scripts silently exfiltrating your data.

NoScript Extension: blocks all JavaScript by default, and you manually approve which scripts can run. Yeah, it’s tedious at first. But once it’s configured, your browsing security level jumps dramatically. You’ll be shocked at how many scripts are actually running on every single page you visit.

NoScript setup:
1. Install from official store
2. Default: Default (Sys WHITELIST) → block everything
3. Per website: click NoScript icon → whitelist only the top-level domain
4. Example: on google.com → whitelist google.com, do NOT whitelist google-analytics.com

For even more granular control, check out uMatrix (also by Nicholas Verdold, the NoScript creator). uMatrix filters by resource type — script, XHR, image, CSS, frame — and by domain. It’s incredibly powerful for anyone who wants absolute control over what runs in their browser.

5. Defeat Fingerprinting and Randomize Your User-Agent

Browser fingerprinting is how websites identify you without cookies. They combine screen resolution, installed fonts, WebGL renderer, canvas fingerprint, audio context fingerprint, and a dozen other data points. No login required, no cookie needed — just fingerprint data alone is enough to track you across sessions.

Firefox has a built-in solution: open about:config, search for privacy.resistFingerprinting, and set it to true. This randomizes multiple fingerprinting vectors simultaneously. Brave offers similar protection through its Shields panel — set Fingerprinting blocking to Aggressive.

Firefox advanced fingerprint protection:
1. Open about:config
2. Search: privacy.resistFingerprinting
3. Set to: true
4. Restart browser

Effect: Canvas, WebGL, AudioContext, fonts, timezone, and more will be randomized

Brave:
1. Click Shields icon in address bar
2. Fingerprinting blocking → Aggressive
3. Page will auto-reload

Heads up: resistFingerprinting might cause some websites to look slightly off — font sizes change, timezone might not match your actual location. If a specific site breaks, you can disable the protection per-site through uBlock Origin or NoScript.

6. Auto-Clean Browser Storage Regularly

Even with all the blocking in place, residual data lingers: localStorage, sessionStorage, IndexedDB, cache, and service workers. All of this can be used to track you without traditional cookies.

Set up automatic cleanup. In Firefox: about:preferences#privacy → History → “Firefox will” → Use custom settings → under “Cookies and Site Data,” check “Delete cookies and site data when Firefox is closed.” For Chrome: chrome://settings/cookies → “Clear cookies and site data when you close all windows.”

Firefox auto-cleanup:
Preferences → Privacy → History → Custom Settings
- Cookies and Site Data → "Delete when Firefox is closed"
- Site Data → Exceptions → whitelist only essential websites

Chrome auto-cleanup:
chrome://settings/cookies → Clear cookies and site data when you close all windows

Pro tip: install the “Cookie AutoDelete” extension for even finer control. It auto-deletes cookies the moment you close a tab, with whitelist support for sites you need to stay logged into.

7. Consider a Privacy-First Browser

If you’re serious about privacy, consider using Brave or Tor Browser for sensitive browsing. Brave comes with a built-in ad blocker, fingerprint protection, and HTTPS-upgrade enabled by default. Tor goes even further — it routes your traffic through three separate relay nodes to anonymize your IP address.

But don’t use Tor for everyday browsing (checking email, logging into banking, etc.). Tor is designed for anonymity, not daily use. For a daily driver that’s privacy-focused, Brave or a hardened Firefox setup covers most use cases just fine.

Browser privacy comparison:

| Browser   | Built-in Blocker | Fingerprint | DoH  | Speed |
|-----------|-------------------|-------------|------|-------|
| Chrome    | Basic             | None        | Yes  | Fast  |
| Firefox   | Medium            | ResistFp    | Yes  | Fast  |
| Brave     | Strong            | Aggressive  | Yes  | Fast  |
| Tor       | Strongest         | Randomize   | Yes  | Slow  |
| Vivaldi   | Medium            | None        | Yes  | Fast  |

Pro tip: if you need multiple isolated profiles, Firefox container tabs are excellent. Create separate containers for work, personal, and banking — each fully isolated from the others. Install the “Multi-Account Containers” extension from Mozilla to set this up.

Privacy Verification Checklist

Before you close this article, verify you’ve got all of these covered:

1. Third-party cookies: BLOCKED (not just “incognito”)
2. uBlock Origin: INSTALLED with full filter lists enabled
3. DNS: Cloudflare DoH or NextDNS configured
4. JavaScript: NoScript installed or uBlock Origin script blocking ON
5. Fingerprint: resistFingerprinting ON (Firefox) or Aggressive (Brave)
6. Auto-cleanup: enabled for cookies and site data
7. Browser: Firefox or Brave at minimum, not vanilla Chrome

Troubleshooting: Website Broken After Hardening

This happens all the time. You harden your browser, and suddenly half the internet stops working. The key is: don’t whitelist everything. Be surgical about it. Whitelist per-domain, and follow the principle of least privilege — only allow what’s absolutely necessary.

FAQ

There you have it — a browser that’s significantly more secure than what you started with. Start with step one and work through them methodically. If something breaks, use the troubleshooting table above — don’t just whitelist everything. That’s how engineers work: methodical, step by step, no shortcuts.

Bookmark this article (syslogsolutions.net/en/noc-article/browser-privacy-anti-tracking-block-trackers/) for future reference. Also check out our guides on Linux server hardening and iptables/nftables firewall configuration for a more comprehensive security setup. And if you manage SSH access across multiple servers, definitely read our Fail2ban setup guide to protect against brute force attacks.