Wirelet: Modify HTTP Headers & User-Agent Switcher extension
Security at a glance
Automated estimate from our latest scan (malware, permissions, obfuscation) — not a security audit. Higher safety score is better.
See the full security reportEdge listing ID: eakjkekgdahclbmojnbiilneemmkgjeh
Permissions (4)
- Block requests with host access
- Store local data
- Schedule tasks
Related extensions
HeaderWright — Modify HTTP HeadersDeveloper
ModHeader — [by modheader.app]Developer Tools
Rewire – Modify Headers, Cookie Editor & Network InspectorDeveloper
Header Editor – Modify HTTP HeadersDeveloper Tools
Headerwise: Modify HTTP Headers & CORSDeveloper
Headerbench - Modify HTTP Headers & RequestsDeveloper Tools
Frequently asked questions
Is Wirelet: Modify HTTP Headers & User-Agent Switcher safe to use?
Our latest automated scan rates the Edge listing of Wirelet: Modify HTTP Headers & User-Agent Switcher at 77/100 (some risk) — malware, permission and obfuscation checks combined. The full report lists every finding behind the number. This is an automated estimate, not a guarantee of safety.
What permissions does Wirelet: Modify HTTP Headers & User-Agent Switcher require?
Wirelet: Modify HTTP Headers & User-Agent Switcher requests 4 permissions. The most significant: Block requests with host access, Store local data, Schedule tasks. See the full breakdown in the security report.
Who develops Wirelet: Modify HTTP Headers & User-Agent Switcher?
Wirelet: Modify HTTP Headers & User-Agent Switcher is published by Wirelet. Impersonators copy popular extension names, so always verify the developer line and listing id on the store page before installing.
What this assessment covers
- Store listing
- Edge
- Checked version
- 1.0.2
- Current listed version
- 1.0.2
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 1 critical and 0 high severity. Read the finding details before interpreting the score; automated flags are not proof of malicious behaviour.
Automated analysis looks for suspicious code, permissions and other risk signals. It does not observe every runtime behaviour or independently audit the publisher’s servers. A low-risk result is not a guarantee of safety. How our checks work.