Port scan protection

Some sites knock on the ports of your computer and local network and learn from the answers what you run. The protection makes an open port look the same as a closed one. The way there: Edit profile, the Port scan protection block.

Three modes

Mask all, Mask all except ports and Do not mask. The default is Mask all, and so it is for every profile made earlier.

What masking means

A page request to the addresses of this computer and your local network is refused before it connects, the same way for an open and a closed port. The site sees nothing open.

A move you make yourself is left alone. A page opened from a local address, such as a router, loads itself as before.

Your own services

Mask all except ports opens only your ports to sites: comma separated, up to 50. Add only your own services, such as a hardware wallet bridge.

The window will not take the ARMANOS port: it must stay closed to sites.

Where you see it

The Fingerprint window has a Ports line: masked, masked except and a list, or not masked. Quick edit offers the same choice.

Both engines

The protection works in ARMANOS Browser and in the built-in engine, with one decision for both. A change takes effect at the next launch of the profile.

What this does not do

On a profile without a proxy, a TURN connection over TCP is not masked yet, and in ARMANOS Browser neither is a site name that leads to your computer or your local network. The built-in engine already masks such a name. ARMANOS Browser closes both with its next build, while in the built-in engine the TURN connection stays open: it bypasses the app, and there is nothing there to close it with.
A server you built yourself before the update does not keep the setting: then it does not travel through the account. With our server it travels through the account to your other computers and colleagues, and also with the transfer with the session, a copy and Export.
Do not mask: ARMANOS Browser asks first, like Chrome, and the built-in engine answers as is.

Where this is decided

The claims that carry the most weight, with the stand that checks each of them.

Every kind of local address is taken from the Chromium source and closed, with one decision for both engines: apps/desktop/test/порты-правила.js
On the built ARMANOS Browser and the built-in engine an open port looks the same as a closed one, and our own protection extension still reaches the loopback: apps/desktop/test/порты-живьём.js
Three modes in the window, an invalid port list refused in words, the line in the Fingerprint window: apps/desktop/test/порты-в-окне.js

Questions

Will it break my router or my own service on localhost?: No. A page opened from a local address loads itself. An outside site cannot reach it.
Does a site see that the protection is on?: It sees the same as on a machine without local services: nothing open.

Next to this

Try it on your own profiles

The free plan gives two profiles, with no time limit and no card.

Download opens at launch Knowledge base