Virtual machines

Port scan

Free scan of the TCP ports open to the internet on an instance's public addresses, grouped by risk, with an email when a dangerous port appears.

Port scan shows which ports of your instances answer from the internet and how risky they are. hostd scans the public addresses of the instances, lists the open ports in the portal and emails the project owner when something dangerous shows up, for example a database or remote desktop left open by mistake. The feature is free. It is on by default and does not need to be set up; you can turn it off for an instance in the instance menu on the page.

What is scanned

  • TCP ports 1–1024 and the ports of common services (databases, caches, remote access, admin panels).
  • Every public IPv4 and IPv6 address of an instance that is running. An address of a stopped instance keeps its last result.
  • About once a day. Scan now on the page scans one address right away; it can be used once every few minutes.

The scan shows what the internet sees. A port blocked by the instance firewall is not listed. Ports outside the scanned set are not checked.

Categories

Every open port gets a category:

  • Critical – services that should not be open to the internet: databases and caches (MySQL, PostgreSQL, Redis, MongoDB, Elasticsearch, Memcached), remote desktop (RDP, VNC), SMB, Telnet, NFS, WinRM, Docker and Kubernetes APIs.
  • Major – services that are often open on purpose but are a common target: SSH, FTP, LDAP, MQTT, RabbitMQ, and admin panels such as cPanel, Plesk, Webmin, Portainer and Grafana.
  • Normal – ordinary public services: web (80, 443, 8080), DNS and mail ports.
  • Other – the port is open but is not on the list of known services.

Emails

The project owner gets an email (one per project) when a new open port appears on an instance address, whatever its category. A port that closes and opens again is reported again.

Instances younger than 48 hours are not scanned automatically, to leave time for setup. You can scan one at once with Scan now (a scan started by hand sends no email), and after the first scan it is scanned like the others. Otherwise the first automatic scan, after 48 hours, emails all the open ports of the address. A port that closes or no change at all sends no email. The current list is always in the portal.

View the results

  1. Open Monitoring → Port scan.
  2. The list shows the addresses of the whole project, grouped by instance, with the time of the last scan and the open ports with their category. You can filter it by instance.
  3. The ⋯ menu of an instance has Scan now, Turn off scanning (and Turn on scanning to resume) and Open VM firewall, to close a port you do not want to expose. While scanning is off the instance is not scanned automatically and no emails are sent for it.

hostd does not ask you to confirm ports: the page shows what is open and you decide what to do with it. To close a port, change the application so that it listens only on the private address, or block the port in the instance firewall with a rule or a security group. To keep a service open for chosen addresses only, add them to an IP set and allow the set for that port.

Scan source addresses

The scan comes from 38.56.199.12 and 2a0e:7d80::fc. Do not allow these addresses in the instance firewall: the scan should see the same ports as any host on the internet, and an allowed address would make a closed port look open.

On this page