Font Fingerprint Defender
Defending against Font fingerprinting by reporting a fake value.
Defending against AudioContext fingerprinting by reporting a fake value.
Review user movement across collected snapshots.
View collected rating snapshots from the latest 7-day window to assess rating stability.
Compare 1-day, 7-day, and 30-day net growth and growth rate.
Review publication date, version, supported languages, and crawl timestamps.
Review the store description, core capabilities, and common use cases.
AudioContext Fingerprint Defender is an extension that let you easily hide your real audiocontext fingerprint by reporting a random fake value and protecting your privacy.
This addon does NOT block AudioContext or any other web audio API methods, instead, it simply adds a small noise to the actual fingerprint and "renews" it every time you visit a website or reload a page. It is important to note that, this addon does not have any settings or options to adjust. Simply add it to your browser and start surfacing the internet. If you want to test this addon, please visit a website that shows your fingerprint (i.e. audiofingerprint.openwpm). Every time you reload the page, you will see a new fake fingerprint.
Note: depending on your browser and platform, you may need to (Shift+Refresh) a web page to renew the AudioContext fingerprint.
To report bugs, please visit the addon's homepage (https://mybrowseraddon.com/audiocontext-defender.html) and fill out the bug report form.
Inspect the latest comments and rating distribution.
Store average score: 3.8. The bars below are calculated from synced review text only, so they may be empty for extensions that have public ratings but no synced comments yet.
Review related products from the Chrome Web Store detail page.
Defending against Font fingerprinting by reporting a fake value.
Defending against Canvas fingerprinting by reporting a fake value.
Spoof websites trying to gather information about your web navigation to deliver distinct content you may not want
Easily block (nullify) undesired Web API(s) and improve your privacy.
Defending against WebGPU fingerprinting by reporting a fake value.
Prevents sites from tracking you by blocking the PING request!
Because of this browser extension, it’s no longer possible to solve the Cloudflare CAPTCHA - before, everything was working fine..
Fingerprint using OscillatorNode - Doesn't change Fingerprint using hybrid of OscillatorNode/DynamicsCompressor method - Doesn't change Implemented an additional injection layer that introduces controlled stochastic noise into the WebAudio graph to prevent deterministic AudioContext fingerprinting. The patch hooks into AudioContext.prototype.createAnalyser, createOscillator, and DynamicsCompressorNode.prototype.getReduction, modifying the generated audio buffer values before fingerprinting scripts can read them. The noise injection is performed early via a custom script (my_audio_patch.js) loaded at document_start in both MAIN and ISOLATED worlds to guarantee execution before any third-party scripts initialize a fingerprinting pipeline. This results in non-stable, non-correlatable fingerprints for: DynamicsCompressor buffer sum DynamicsCompressor full buffer hash OscillatorNode output sample patterns Hybrid oscillator/compressor fingerprinting flows If useful, I can provide the modified manifest.json and patch file so this functionality can be added as an optional “noise randomization mode” in future versions.
Worked fine before but now it seems to break pages that use cloudflare captcha, making them constantly reload.
This is just brilliant: support page of this extensions uses Cloudflare, so before going to the actual support page I see Cloudflare stub and I unable to pas the Cloudflare's checks if I am real human or not, because those three fingerprinting techniques - canvas fingerprinting, font fingerprinting, AudioContext fingerprinting are disabled by dedicated extensions, LOL.
Really good, I recommend this extension.
It's great
Ваше расширение потребляет овер много ресурсов компьютера, 0,5 гб ОЗУ и 40% ЦП https://i.imgur.com/87JzeDq.png
Does what it claims to in the most convenient way possible.
Does exactly what it should do and claims it does. Tested at: * https://audiofingerprint.openwpm.com/ - defeated all 4 types of audio fingerprinting * https://webbrowsertools.com/audiocontext-fingerprint/ - defeated all 4 types of audio fingerprinting * https://browserleaks.com/features - defeated the general "features detection" fingerprint (site doesn't have an audiocontext-specific test) I like that this is a 1-exploit fix (well, TECHNICALLY a 4-exploit fix) instead of a plugin claiming to spoof all forms of user fingerprinting, since new methods of that come up all the time. It's better to be certain that you have a particular weakness patched up because you have an extension that corresponds to it exactly, than to go without preventing a leak because you assumed it was included in some catchall extension but it wasn't. PS: Anyone who cannot figure out that they can click on the extension's icon and pick "Show|Hide desktop notifications" simply doesn't DESERVE to use this extension. Heh. Really, the developer should just turn this option off by default, since it's obviously the only thing causing unhappy feedback.
It works, guys! It DOES HAVE an option to turn off the notifications!