Ext Ops Panel
Open dashboard
Permissions and history

Is Simple HTTP Headers Injector safe to install?

Simple HTTP Headers Injector asks for 3 browser permissions and 1 site pattern. We do not audit code and we do not judge intent; what we can show is what the listing declares and whether that has changed while we have been watching.

Simple HTTP Headers Injector

Chrome extension by realefs · Productivity · Developer

Open in the Chrome Web Store
What the developer says, and 1 screenshot

Loading from the Chrome Web Store. Open the listing if it does not appear.

At a glance

Facts, not a score: an ad blocker needs every page and a theme needs nothing, so one number would be wrong about both. Each fact links to its detail.

Site access
Access to every site
Data collection
Declares it collects none
Publisher
No store badges
Audience
404 users · 5.0/5

What data it declares

The developer declares that it does not collect or use your data.

The developer also certifies that your data is not sold to third parties outside approved uses, not used for purposes unrelated to the extension's core function, and not used to decide creditworthiness or lending.

The listing does not link to a privacy policy.

This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.

What Chrome asks you to allow

When you add it, Chrome asks you to allow it to:

Derived from the manifest by Chrome's documented rules; the dialog's exact wording depends on your Chrome version and language. Chrome asks again if an update requests more.

What it can reach

Every site you visit. This extension can read and change the content of any page you open. What access to every site means

Worth knowing

Routine for an extension

How usual this is for its category

In Productivity · Developer, 30% of extensions ask for access to every site. This one: Access to every site.

The typical extension there declares 3 browser permissions; this one declares 3 browser permissions.

Counted over the live extensions of the same category after our latest full pass of the store. A share is context, not a verdict: what is normal depends on what the extension is for.

Who uses it and how it is kept up

404 users

Users
+168 since 01.09
236-411 · 31 readings
  1. 2026-09-01236
  2. 2026-09-03244
  3. 2026-09-05250
  4. 2026-09-07244
  5. 2026-09-09245
  6. 2026-09-10249
  7. 2026-09-13265
  8. 2026-09-15280
  9. 2026-09-17297
  10. 2026-09-20305
  11. 2026-09-21309
  12. 2026-09-25315
  13. 2026-09-26312
  14. 2026-09-28314
  15. 2026-10-04330
  16. 2026-10-08333
  17. 2026-10-09346
  18. 2026-10-10345
  19. 2026-10-11355
  20. 2026-10-13364
  21. 2026-10-16391
  22. 2026-10-17389
  23. 2026-10-18390
  24. 2026-10-19391
  25. 2026-10-21393
  26. 2026-10-22403
  27. 2026-10-23411
  28. 2026-10-24408
  29. 2026-10-25409
  30. 2026-10-27404
  31. 2026-10-30404

What the store shows

The store shows none of its badges on this listing. Most listings carry none.

Has it asked for more over time?

This is the question a permission list on its own cannot answer. An extension that shipped narrow and widened later is a different proposition from one that always asked for the same thing.

The permissions this extension requests have not changed since we started watching it.

Who publishes it

realefs, who publishes 16 listings we track. This listing has been in the store since 2026-02-11 and was last updated on 2026-08-05.

Similar extensions that ask for less

Listings close to this one in what they say they do, which declare less reach. Less reach is not a verdict on either: compare what each needs for the job.

  1. HTTP Header Injector Access to every site · 2 permissions, 1 site pattern 4k users ★ 4.2
  2. HeadChanger Access to every site · 2 permissions, 1 site pattern 8 users ★ 5.0
  3. HTTP Header Injector Access to every site · 2 permissions, 1 site pattern 99 users

How to check or remove it in Chrome

  1. Type chrome://extensions in the address bar and find the extension in the list.
  2. Open its details. The site access setting shows where it can run; set it to run only on click and it reaches a page only after you press its icon.
  3. To uninstall it, choose Remove on the same page.

Questions people ask

What can Simple HTTP Headers Injector access?
Every site you visit. This extension can read and change the content of any page you open. It declares 3 browser permissions.
What data does Simple HTTP Headers Injector collect?
The developer declares that it does not collect or use your data. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has Simple HTTP Headers Injector asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Simple HTTP Headers Injector publish a privacy policy?
No, the store listing does not link to a privacy policy.

We read the public store listing up to 2 times a day and keep what it declared. We do not install the extension, do not audit its code, do not judge its intent and publish no contact details for its developer. Last read on 2026-10-30.

Back to Simple HTTP Headers Injector · Alternatives to Simple HTTP Headers Injector

Where the data comes from: how the catalog is built