Ext Ops Panel
Open dashboard
Permissions and history

Is HTTP Header Injector safe to install?

HTTP Header Injector asks for 2 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.

HTTP Header Injector

Chrome extension by kengo071225 · 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
96 users

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 links 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 2 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

96 users

Users
+18 since 01.09
75-116 · 29 readings
  1. 2026-09-0178
  2. 2026-09-0377
  3. 2026-09-0475
  4. 2026-09-0579
  5. 2026-09-0778
  6. 2026-09-0876
  7. 2026-09-1078
  8. 2026-09-1580
  9. 2026-09-1681
  10. 2026-09-2084
  11. 2026-09-2189
  12. 2026-09-2597
  13. 2026-09-27106
  14. 2026-09-28107
  15. 2026-10-04113
  16. 2026-10-08116
  17. 2026-10-10115
  18. 2026-10-13110
  19. 2026-10-16112
  20. 2026-10-17111
  21. 2026-10-18112
  22. 2026-10-20114
  23. 2026-10-22116
  24. 2026-10-25114
  25. 2026-10-28107
  26. 2026-10-29103
  27. 2026-10-3099
  28. 2026-11-0196
  29. 2026-11-0396

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

kengo071225, who publishes 4 listings we track. This listing has been in the store since 2026-07-12 and was last updated on 2026-08-05.

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 HTTP Header Injector access?
Every site you visit. This extension can read and change the content of any page you open. It declares 2 browser permissions.
What data does HTTP Header 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 HTTP Header Injector asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does HTTP Header Injector publish a privacy policy?
Yes, the store listing links 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-11-03.

Back to HTTP Header Injector · Alternatives to HTTP Header Injector

Where the data comes from: how the catalog is built