1 item
Per-domain HTTP header editor. Set, append, or strip any request or response header, scoped to the sites you choose. NoRefer 2 lets you rewrite HTTP headers on the sites you choose — the modern successor to the original NoRefer extension, rebuilt on Manifest V3. WHAT YOU CAN DO • Set, remove, or append any header • Edit both request headers (sent by your browser) and response headers (sent back by the server) • Scope each rule to specific domains — subdomains included automatically — or apply it everywhere • Match by the target host, by the page the request comes from, or by a URL filter like ||example.com/api/* • Order rules to control which one wins when two touch the same header • See a per-tab badge counting the rules active on the current site, and flip everything off with one master switch COMMON USES • Strip the Referer header for privacy • Send Do-Not-Track / Global Privacy Control signals • Spoof a User-Agent on a specific site • Drop Content-Security-Policy or set Access-Control-Allow-Origin while developing locally • Add an Authorization or custom header to an internal API you're testing FAST AND PRIVATE Headers are rewritten by the browser's own declarativeNetRequest engine, so edits apply natively without any extension code sitting on your traffic. Everything is stored locally on your device. No accounts, no telemetry, no servers, no data collection. Presets get you started in one click, and you can import/export your rules as JSON — including an importer for configs from the original NoRefer. Open source (MIT): https://github.com/c475/NoRefer2
Jul 23, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.