How does port monitoring work?¶
A port monitor watches one port of one server, such as a mail server's IMAP port or an SSH port, rather than a web page. We connect to the port and, where the service speaks first, read the first line it says. We never send it anything: we do not log in, send mail or type a command. Port monitors come with the Plus plan and up (what each plan includes). On the Free plan, Port is shown on Add a monitor with a lock and the plan that has it, and cannot be chosen; a port monitor made before is paused, with its settings and history, and runs again after a move to a plan with port monitors.
Port monitors are checked from the same servers as every other check. If a firewall in front of the server lets only some addresses in, allow our checks on the port you watch.
Add a port monitor¶
- Open Monitors in the side menu and click Add a monitor.
- Under Monitor type, choose Port.
- Under The port, type the Server address: its name or address, such as
mail.example.com. Type the name only, withouthttps://, a port, a path or a user name. - Type the Port, one number, for example
993. A mail, FTP or SSH port fills in its Greeting for you. - Check the Greeting (below): what the service must say first, or None: connect only.
- Optional: give it a Name. Without one, the list shows the server and the port, such as
mail.example.com:993. - Optional: a Group and Tags, then check Who gets alerts and Check interval, as for any monitor.
- Click Add monitor.
One monitor watches one port. To watch IMAP and SMTP on the same server, add two monitors. You can watch at most 5 ports of one server; the same port of the same server can be in the list once.
The ports we check¶
| Service | Ports |
|---|---|
| FTP | 21, and 990 over TLS |
| SSH and SFTP | 22 |
| Mail (SMTP) | 25 and 587, and 465 over TLS |
| Mail (POP3) | 110, and 995 over TLS |
| Mail (IMAP) | 143, and 993 over TLS |
| Web | 80, 443, 8080, 8081, 8443, 8880, 8888 |
| Search (Typesense) | 8108 |
| Control panels | 2083, 2087 and 2096 (cPanel, WHM and webmail), 2222 (DirectAdmin), 10000 (Webmin) |
| Databases, on paid plans | 3306 (MySQL), 5432 (PostgreSQL), 6379 (Redis), 9200 (Elasticsearch), 27017 (MongoDB), 1433 (SQL Server) |
Any other port is refused with Port 9000 cannot be checked. and a pointer to this list. A range or a list of ports is never accepted. Need a port that is not here? Click Need another port? Ask us beside the Port field, or write to us, and tell us the service and the port.
Database ports¶
A port monitor can watch a database server's port: 3306 (MySQL), 5432 (PostgreSQL), 6379 (Redis), 9200 (Elasticsearch), 27017 (MongoDB) and 1433 (SQL Server). Database ports come with every plan that has port monitors.
We only connect: we never log in, send a query or read anything from the database. Its Greeting is None: connect only; any other greeting is refused.
A database should not be open to the whole internet. When you choose a database port, the app says Allow only our checking servers in this server's firewall. Let our checking servers in on that port and keep it closed to everyone else.
On 465, 993, 995 and 990 the service speaks TLS from the first byte, so we check its certificate too. A certificate that is expired, not trusted or made for another name is SSL certificate problem, as on a website.
Greetings¶
Many services say a first line as soon as you connect. The Greeting says which one we expect:
| Greeting | A healthy first line starts with |
|---|---|
| Mail server (SMTP) | 220 |
| Mail server (IMAP) | * OK |
| Mail server (POP3) | +OK |
| FTP server | 220 |
| SSH or SFTP server | SSH- |
| None: connect only | Nothing is read: the port is up when it accepts the connection |
We read at most one line and wait at most 5 seconds for it. A web server, a search engine or a control panel says nothing first: choose None: connect only for those ports.
What the results mean¶
| Result | Counts as | What it means | What to do |
|---|---|---|---|
| Up | Up | The port accepted the connection, and the service said what it should | Nothing |
| Port closed | Down, once a second place agrees | The server refuses connections on this port | Check that the service is running and listens on this port |
| No answer from the port | Down, once a second place agrees | The connection got no answer within 10 seconds | Allow our checks in the firewall, or check that the server is running |
| Server name not found | Down, once a second place agrees | The server's name has no address | Check the name, and that it still points to the server |
| Server name lookup got no answer | Down, once a second place agrees | The name servers of the server's domain did not answer, so we could not find its address | Check that the domain's DNS hosting is up |
| Server not reachable | Down, once a second place agrees | No route to the server: its network did not answer | Check that the server is running and its network is up |
| The connection was cut | Down, once a second place agrees | The connection closed before it was set up | Check that the service is running and listens on this port |
| No secure connection on this port | Down, once a second place agrees | On a TLS port, the service does not speak TLS | Check that the port is the TLS one, such as 993 rather than 143 |
| Answers, but not as a mail server should: 421 ... | Down, once a second place agrees | The service said something else first; its line is shown, at most 80 characters | It may be busy or refusing work; its logs usually say why. If another service runs on this port, choose its greeting in Settings |
| Answers, but not as an FTP server should: ... or ... as an SSH server should: ... | Down, once a second place agrees | The same, for the FTP server and SSH or SFTP server greetings | The same |
| Connects, but the service says nothing | Down, once a second place agrees | The port is open, but no first line came within 5 seconds | It may have hung; a restart usually helps. If this service never speaks first, choose None: connect only in Settings |
| SSL certificate problem | Down, once a second place agrees | On a TLS port, the certificate is expired, not trusted or for another name | Renew or fix the service's certificate |
| Private or internal address | Needs attention | The server's name points to a private network, which we never check | Use the server's public name or address |
As for every monitor, a monitor is Down only once a second place agrees (Down only when a second place agrees). A port monitor on port 22 (SSH) is the exception: only Newark checks it, so it turns Down after 3 failures in a row from Newark, without a second place.
Settings¶
On a port monitor's Settings page, The port holds its Server address, Port and Greeting. A changed server address or port is checked as when you add one, and starts its checks again; the past results stay. A mail, FTP or SSH port fills in its greeting, as when you add one, until you choose another. A port monitor has no Basic Auth, staging, keyword or status settings: it reads no page. The field Server under The monitor is the server it runs on, such as web-03, as for any monitor.
Websites on other ports¶
A website or an address can be watched on 80 and 443, and on the web ports of the list above: 8080, 8081, 8443, 8880,
8888, 8108 (Typesense's health address, such as https://search.example.com:8108/health) and the control panels'
2083, 2087, 2096, 2222 and 10000. Add it as an HTTP(S) or Keyword monitor with the port in its address. An
address written with its own scheme's port, such as https://example.com:443, is the same monitor as without it.