Network activity

Every outbound connection a Recon Essentials installation makes, and the privileges its scans need.

A self-hosted scanner is only deployable if the network team can see what it will talk to. This page is that list, in full. The same table is shown inside the product under Scan configuration → Network activity, where the optional entries can be switched off, and it ships in the README beside the install scripts — all three come from one definition in the product, so they cannot drift apart.

Your own assets are scanned from this machine's address. There is no Vulmon scanner in the path.

Outbound connections

TargetPortsPurposeFromCan be switched off
Your own assets (the seeds you add and what they resolve to)allScanning: DNS, ports, HTTP(S), TLS certificates. Two of these can leave your own addresses without leaving your assets: a page's icon is fetched from the address the page itself gives, which may be a content delivery network, and an HTTP request follows redirects (up to ten), which may end on another domain.EngineNo
Public DNS resolvers 1.1.1.1, 1.0.0.1 (Cloudflare), 8.8.8.8, 8.8.4.4 (Google), 9.9.9.9 (Quad9)53/udp, 53/tcpDNS discovery: subdomains and MX/NS/TXT/CAA records. Public resolvers so results match what the internet sees and your own DNS server does not carry thousands of lookups. These providers see the names being resolved. If your network allows DNS only to its own resolver, these scans cannot run.EngineNo
crt.sh5432, 443Certificate Transparency log search (subdomain discovery). The routine query uses the Postgres interface on 5432; if 5432 cannot be reached at all, it falls back to the HTTPS interface on 443 and asks only for the subdomains of the domain being scanned. Either way at most one request every two seconds, identifying itself as recon-essentials. Switching it off stops subdomain discovery from CT logs.EngineYes — Scan configuration → Network activity
recon.vulmon.com (registered installations only)443License renewal (every day, registered installations only). It also reports how many domains and IP addresses are in scope, out of scope and pending, and how many seeds there are — numbers only, never names. A registered installation keeps working for 7 days without renewal, then scanning pauses until the license server is reachable again.EngineNo
recon.vulmon.com443Registration with Vulmon — once, from Settings → License, made by the web server. No call is made unless you register.Web serverOnly if you register
recon.vulmon.com443Signed product manifest: revocation list, minimum supported versions, the latest release (for the update notice), announcements. Contains nothing about your installation. Tolerates short outages.EngineNo
WHOIS servers (IANA, registries, registrars, whois.cymru.com)43/tcpDomain and IP WHOIS records. whois.cymru.com tells which network (ASN) an IP address belongs to. Switching it off leaves the WHOIS fields as "not measured".EngineYes — Scan configuration → Network activity
RDAP servers (data.iana.org, rdap.db.ripe.net, pubapi.registry.google and the other registries)443RDAP lookups (the HTTPS successor of WHOIS), also used for domain extensions that publish no WHOIS server. Switching it off leaves the RDAP-sourced fields as "not measured".EngineYes — Scan configuration → Network activity

Inbound: Only the web UI port you publish in docker-compose (default 8080).

Installing, starting and upgrading

The table lists what the running installation does. The scripts that install, start and upgrade it run on the computer itself, so they are listed here instead:

  • Installing and upgrading download the scripts, docker-compose.yml and .env.example from raw.githubusercontent.com (the distribution repository), and the images from Docker Hub: the web, the engine and PostgreSQL.
  • Starting downloads nothing, unless an image is missing. It can offer an upgrade, but the offer adds no connection: it reads the latest release from the signed manifest in the table above, which the engine has already fetched.

What the three Vulmon entries actually carry

Two of them exist only if you register, and one runs regardless. It is worth being precise about which is which.

The signed product manifest is fetched whether or not you registered. It carries the revocation list, the minimum supported versions, the latest release and product announcements — and nothing about your installation. The latest release is what lets the product show "update available" without a call of its own: the notice rides on this one fetch, so no update check is added to the list above. The request sends no identifier of any kind, and the response is identical for everyone, which is why it can sit behind a CDN cache. An installation cannot learn that its license was revoked without asking, so this one call is the price of that.

Registration happens once, only if you start it, and only from Settings → License. It sends your email address, the installation id and the product versions.

Renewal happens about once a day and only once you are registered. It also reports how many domains and IP addresses are in scope, out of scope and pending, and how many seeds there are. If the license server is unreachable, everything keeps working for 7 days; after that scanning pauses — nothing is deleted — until a renewal succeeds.

Those counts are numbers only. Asset names, scan results and the inventory itself never leave the machine. How Vulmon handles the personal data it does receive, and your rights, are in the privacy policy.

Network privileges

For full scanning — SYN port scans, the full port range, ICMP reachability — the pipeline container needs raw sockets. The compose file grants NET_RAW and runs the engine as root inside its own container. That is the Docker default; no --privileged is involved.

On a rootless runtime (rootless Docker, Podman rootless, a restricted Kubernetes profile) the engine still runs. It detects the missing privilege at start and scans with what it has: TCP connect scans of the common ports instead of SYN, and no full port range. UDP scanning does not need the privilege. Scan configuration → Scanning reports exactly which of the three capabilities it has, and the affected fields say "not measured" rather than reporting an empty result as a clean one.

The engine checks its capabilities each time it starts, and that page shows when it last checked. After you change the compose file or your network, restart the engine with docker compose restart pipeline to see the new answer.

Three capabilities are reported separately on purpose, because a container can hold one and not the others:

  • Raw sockets — decides SYN and full-range port scanning.
  • ICMP (ping) — a container can hold NET_RAW and still be unable to ping, because an egress filter drops ICMP. Then reachability is inferred rather than measured.
  • Public DNS — subdomain discovery and the MX, NS, TXT and CAA lookups go to public resolvers. If your network allows DNS only to its own resolver, those scans are skipped; A records, reverse DNS and the HTTP and TLS checks still use this machine's resolver.

Endpoint security

The engine performs port scans and sends ICMP from this machine. Some EDR and IDS products flag that as reconnaissance. Add an exception for the recon-essentials containers, or for this host, before scanning large ranges.