ยังไม่มีหน้านี้ในภาษาของคุณ คุณกำลังอ่านข้อความภาษาอังกฤษ
Guides
How to check that an ad blocker works in a profile
ทีม ARMANOS7 minUpdated

In short
A one-minute check. The network tab shows whether a request was stopped.
Your own trap instead of guesses. A simple server tells you whether the request arrived.
The engine for the job. ARMANOS Browser runs the extension in full, the built-in engine runs blocking rules.
What the extensions page shows
The extensions page in any browser answers about files: the extension was downloaded, unpacked and handed to the browser at profile start.
About the fate of a single request it says nothing.
The icon in the toolbar is drawn by the extension itself, from the fact that it loaded, not from a count of stopped requests.
So a green card and a live ad on one page are not a contradiction.
So enabled is a claim about files on your disk, and blocking is a claim about the network. No screen checks the second one for you.
- 1
Files are in place
The extension folder is unpacked and read by the browser.
- 2
The toggle is on
The extension is handed to the browser when the profile starts.
- 3
Stopped requests show on the network tab
The extensions page shows the files and the switch, while stopped requests show in the developer console.
The network tab answers in a minute
Open a page with ads, switch to the network tab in the developer window and reload. The list keeps every request the page managed to send.
A stopped request has no response and carries a cancelled mark. An ordinary status code means it went out and came back.
- 1
The network tab
The developer window and the request list of the page.
- 2
A reload
The list fills again, starting from the very first request.
- 3
An ad network address
The name of a counter or an ad network in the address column.
- 4
The fate of the request
Cancelled means blocked, a status code means it went through.
Build your own trap page
On somebody else's page you cannot know in advance what should have been blocked: filter lists change every week. So the second check uses an address you picked yourself.
Start a simple server of your own, serve a page with one request to an address like /blockme, and add that address as a rule in the extension.
The server either saw the request or did not: its log answers plainly.
After that, look at the log of your own server rather than at the browser. No list update in the middle of the check can change what it says.
Which engine will really open
A profile opens on the engine that is installed on disk. If the chosen engine is not installed, the profile opens on the built-in one, and the window looks ordinary.
The difference shows before launch: the extensions section warns you when a profile will open on the built-in engine, right above the extension list.
How blockers work on the two engines
ARMANOS Browser runs the extension in full, like an ordinary browser. On the built-in engine the app reads blocking rules from the extension itself and applies them by intercepting requests.
Stopping and allowing a request work as in the list: allow rules are checked before block rules, and a rule's condition runs as a whole. For extensions with their own scripts, pick ARMANOS Browser.
| One extension and one rule | The server saw the request |
|---|---|
| Built-in engine, the extension alone | yes, the request went through |
| Built-in engine, rules applied by ARMANOS | no, the request was stopped |
| The extension counted as enabled | in both cases |
| The page asked for the same address | in both cases |
How to put a blocker into a profile
Eleven vetted extensions install with one button from a ready list. You add the others by a store link or from your own folder.
Manifest V3 extensions are accepted, up to 50 per profile.
The extension set belongs to the profile, not the computer, so on another computer it arrives together with the profile.
After installing, repeat the one-minute check: it answers for today's profile, not for the one from a month ago.
Which rules the app runs itself
On the built-in engine the app understands two kinds of rule actions: stop a request and allow it.
Allow rules are checked before block rules, as in the filter list itself.
Rules with a regular expression, tab binding or a condition on response headers are best handed to ARMANOS Browser: it runs them itself.
A rule's condition runs as a whole, so a rule never stops more than it says.
How to read the marks in rules
Two bars before a host name mean that host and its subdomains. A caret at the end means any separator or the end of the address.
Without the caret a host rule would also catch a foreign domain with the same beginning, and a path rule would miss the same path with parameters.
ARMANOS reads both marks the way the list itself does, so a rule means the same thing on both engines.
When to repeat the check
Repeat the minute after changing the engine, the filter list or the extension version.
For working profiles it pays to check the blocker once a month: the check costs exactly a minute and answers for today's profile.
How to tell which engine a profile opened on
The core version is shown on the profile card: it tells you which engine really opened.
If you expected ARMANOS Browser and the version shows the built-in engine, install the engine you need on this computer and launch the profile again.
After changing the engine, repeat the one-minute check with the same address: the server's answer confirms the result.
What to do after the check
The request reached the server, so the enabled extension did not stop it. Switch the profile to ARMANOS Browser and repeat the same minute with the same address.
The request was cancelled and the banner is still there, so the markup of the page draws it, and a network rule does not reach it.
Then it is the filter list to change, not the browser.
Repeat that minute after every change of engine or filter list. It answers about the profile you have today, not the one from last month.
If you need a blocker on every profile
The extension set belongs to a profile, so install the blocker in every profile where it is needed.
Check one profile with the one-minute check, and open the others on the same engine.
Common questions
- Why does the extension say it is enabled?
- Because it really is enabled: the files are there and the browser accepted them. Enabled and blocking are different things, and only a request proves the second.
- I installed a blocker from the store, why are the ads still here?
- Either the request goes out, and then the profile engine is at fault, or it is cancelled and the banner came with the markup. The network tab tells those apart in a minute.
- Can I tell without the developer window?
- Indirectly. If banners disappear on one profile and stay on another with the same extension, the engine is the reason, not the filter list.
- Must I change the engine of a profile?
- No, if blocking by the extension's rules suits you: ARMANOS runs them on the built-in engine too. For extensions with their own scripts, pick ARMANOS Browser: the extensions section warns you before launch.
- How many extensions can I enable on one profile?
- Up to 50 per profile. The choice belongs to the profile and arrives on another computer once you are signed in to your account.
- Where do I get the blocker itself?
- Eleven checked extensions install with one button from a ready list. Anything else you add by a store link or your own folder, and only Manifest V3 is accepted.
Keep reading
See what extensions can do in a profile
The extensions section shows which engine a profile will open on and what installs with one button.