Hostinger VPS Review 2026
3 Sept 2026
Port Monitoring: How to monitor the services on your servers
A server can be reachable in principle and yet an important service may not be functioning correctly. For example, if the web server, mail server, SSH access or a database does not respond on the intended port, it can directly affect your website, application or internal processes. With port monitoring you regularly check whether a specific network port is reachable and whether the service behind it responds at all. This allows you to recognise problems with individual services early, even if the server itself remains online. In this article you will learn exactly what port monitoring is, which issues you can uncover with it and how to set up the monitoring step by step with Hosttest Plus.
Author:
Christopher | 24 Jul 2026
Christopher | 24 Jul 2026
via Gemini
In a Nutshell
Port monitoring actively checks whether specific network ports accept connections, allowing you to distinguish between host reachability and the failure of individual services (e.g. HTTP(S), SMTP, SSH, RDP, databases). It complements ping checks with service-specific tests and enables timely alerting on timeouts or repeated connection failures.
- Function: Establish a TCP/UDP connection to an IP/domain and port; a successful connection indicates port or service availability, while a timeout or rejection points to a service outage, firewall rule or misconfiguration.
- Operation & configuration: Specify the target (domain/IP) and port, adjust the monitoring interval to match criticality (e.g. 1–5 minutes for production services), plan retries before alerting and configure notifications (escalation channels).
- Limits & best practices: A reachable port is not a functional content check — combine with HTTP, SSL/TLS, DNS and keyword monitoring; secure administrative ports and monitor firewall/security group rules and load balancer/proxy configurations as well.
Port Monitoring
Port Monitoring: Targeted monitoring of server services
A server can be online while individual services no longer function correctly. Port Monitoring checks whether a specific network port is accepting connections and whether essential services such as HTTP, HTTPS, SMTP, IMAP, SSH or RDP are fundamentally reachable.
🔌
When only a specific service fails
The website does not load, e-mails do not arrive or an application cannot connect to the intended system. At first glance it may appear that the entire server has failed, even though only a single service may be affected.
This is exactly where Port Monitoring comes in. It not only checks whether a server is generally reachable, but whether a particular network port is accepting connections. That way you can determine whether a specific service such as HTTP, HTTPS, SMTP, IMAP, SSH or an application interface is fundamentally reachable.
Basics
What is Port Monitoring?
Port Monitoring regularly checks whether a specific port on a server is reachable. A port can be thought of simply as the access point for a particular network service.
Targeted service checks
While an IP address or domain describes the target system, the port specifies which service on that system is being addressed.
Establishing a connection
Port Monitoring attempts to establish a connection to a specific port. If successful, the port is generally considered reachable.
Detecting timeouts
If the connection attempt fails or times out, this can indicate an outage, a firewall rule, or a misconfiguration.
More accurate than ping
Ping monitoring only checks whether a server is reachable at all. Port Monitoring, on the other hand, verifies whether a specific service accepts connections.
Important for server services
Web servers, Mail servers, databases, SSH access, APIs and gateways can be monitored via their respective ports.
Helpful for troubleshooting
If a server is still reachable but an individual service fails, Port Monitoring helps to narrow down the problem more quickly.
Well-known ports
Which services use common network ports?
Many well-known services use standardised ports. This makes it possible to check specifically whether a particular service is reachable in principle.
| Service | Typical ports | What the service is used for |
|---|---|---|
| HTTP | Port 80 | Unencrypted website requests over HTTP. |
| HTTPS | Port 443 | Encrypted website requests over HTTPS. |
| SMTP | Port 25, 465 or 587 | Email delivery and sending. |
| IMAP | Port 143 or 993 | Retrieval and synchronisation of emails. |
| POP3 | Port 110 or 995 | Retrieval of emails from the mail server. |
| SSH | Port 22 | Administration of Linux servers. |
| RDP | Port 3389 | Remote access to Windows servers. |
| MySQL | Port 3306 | Database connections to MySQL systems. |
| PostgreSQL | Port 5432 | Database connections to PostgreSQL systems. |
Why it matters?
Why port monitoring matters
A server often consists of multiple services that can operate or fail independently. The server may be running while individual services are no longer reachable.
Without port monitoring
- A server may appear reachable even though important services have failed.
- Ping monitoring may continue to report a successful check.
- Website, mail server, SSH access or APIs may nevertheless not function.
- Troubleshooting often starts too broadly, focusing on the entire server.
- Service issues remain undiscovered for longer.
With port monitoring
- You can specifically determine whether a particular service is reachable.
- Problems with HTTP, HTTPS, mail, SSH, RDP or APIs become apparent more quickly.
- Firewall and configuration errors can be narrowed down more effectively.
- Failures of individual services are not mistaken for a complete server outage.
- Technical root-cause analysis is much more precise.
Typical situations
When is port monitoring particularly helpful?
Port monitoring is particularly useful when the server is generally running but a specific service is no longer functioning as expected.
Website not loading
The server is online, but port 80 or port 443 is not accepting connections.
HTTPS is down
HTTP still works, but the encrypted connection over port 443 is unreachable.
Email problems
SMTP, IMAP or POP3 are unreachable, preventing emails from being sent or retrieved.
SSH or RDP not reachable
Administrative access to the server is blocked or the relevant service is not running.
Application cannot connect
An application or API cannot establish a connection to a required service.
Service stopped after update
After an update a service was not restarted correctly or is no longer listening on the expected port.
Failure scenarios
What problems does Port Monitoring detect?
Port Monitoring primarily detects whether a service on a particular port is reachable or whether the connection attempt fails.
01
A service has crashed
A common scenario is a service that is no longer running on the server. The server itself remains active, but the affected service no longer accepts connections.
- the web server service has been stopped
- the mail server process is no longer running
- a database service has crashed
- the SSH service has been disabled
- an application is no longer listening on the expected port
- a proxy or gateway has failed
- a service was not restarted after an update
02
A firewall is blocking the port
Not every unreachable port means the service itself has failed. Often access is blocked by a firewall or security rule.
- new firewall rule
- changed network access
- hosting provider block
- security plugin
- incorrect security group on cloud servers
- IP-based access restriction
- changed rules on routers or load balancers
03
A port is no longer reachable after a change
Many port issues occur after technical changes. During a migration, services are moved, ports are changed, firewalls adjusted, or new systems integrated.
- server migration
- operating system update
- change in web server configuration
- mail server change
- switch from HTTP to HTTPS
- enabling a load balancer
- setup of a new cloud firewall
- application migration
04
A service responds slowly or intermittently
Depending on the monitoring used, not only the basic reachability of a port can be checked, but also the duration of the connection establishment. If this takes unusually long or timeouts occur regularly, this can indicate an unstable system.
- server overload
- insufficient resources
- network issues
- faulty service configuration
- too many concurrent connections
- issues with an upstream proxy
- load spikes in an application
05
The wrong port is open or closed
Port Monitoring can also help detect unexpected changes. It's not only about whether a required port is open; an unintentionally reachable port can also be a security risk.
- A required port has been closed.
- A service was accidentally started on a different port.
- After a server migration, an access rule was forgotten.
- A port that should not be public is reachable.
- An old application is still listening on a port.
- An administration service is publicly accessible even though it should be restricted.
Process
How does Port Monitoring work?
Port Monitoring runs automatically in the background. The website or server operator specifies which domain or IP address and which port should be monitored.
1
Establish a connection to the port
The monitoring system attempts to establish a connection to an IP address or domain on a specific port.
2
Check the target server's response
The target server accepts the connection, rejects it, or does not respond at all.
3
Assess reachability
The monitoring evaluates whether the port is fundamentally reachable.
4
Measure connection time
Optionally, the time taken to establish the connection can be measured.
5
Confirm failures
If the service is unreachable or times out, a recheck is performed so that short-term network fluctuations do not immediately trigger false alarms.
6
Trigger a notification
If the fault persists, a notification is sent so the affected service can be checked promptly.
ℹ️
A reachable port is not a full functional check
Port Monitoring initially only shows that a connection is possible. Whether the application behind it is functioning correctly must be verified with further checks depending on the service.
Practice
Which ports should be monitored?
Which ports should be monitored depends on the specific project. A simple website requires different checks than a mail server, a customer portal or a complex application.
80
443
443
Ports for websites
For traditional websites, Port 80 for HTTP and Port 443 for HTTPS are particularly relevant. Since professional websites are typically delivered via HTTPS today, Port 443 is especially important.
25
587
587
Ports for mail servers
For mail servers several ports are relevant because different protocols are used for sending and retrieval. These include SMTP, IMAP and POP3.
- Port 25 for SMTP server-to-server delivery
- Port 465 or 587 for SMTP submission
- Port 143 or 993 for IMAP
- Port 110 or 995 for POP3
22
3389
3389
Ports for server administration
For server administration Port 22 for SSH and Port 3389 for RDP are often used. These ports are important for system management but, for security reasons, should not always be openly accessible from the entire Internet.
API
Ports for applications and APIs
Many applications use their own ports or run behind a proxy, gateway or load balancer. You can monitor individual application ports, API endpoints, load balancer ports, proxy or gateway ports and communication ports between multiple systems.
DB
Ports for databases
Databases such as MySQL or PostgreSQL also use specific ports, for example Port 3306 for MySQL or Port 5432 for PostgreSQL. However, database ports should, in most cases, not be publicly reachable on the Internet.
Interval
How often should Port Monitoring take place?
The appropriate check interval depends on how important the monitored service is and how quickly you need to respond to an outage.
Less critical services
For less important services, an interval of around 5 to 15 minutes may be sufficient.
Business websites and mail services
For production websites, HTTPS availability and mail servers, intervals of 1 to 5 minutes are often appropriate.
Critical applications
For important APIs, customer portals or business-critical services, it may be appropriate to check every minute.
Configure alerting correctly
Short connection issues should not immediately trigger unnecessary alerts. It is often sensible to notify only after several failed checks.
Checklist
What should be checked when a port alert occurs?
In the event of a port alert, first determine whether the service itself has failed or whether the connection is being blocked from outside.
Initial checks
- Is the affected service running on the server?
- Is the correct port configured?
- Has the firewall been changed?
- Has the service been restarted after an update?
- Is there an outage with the hosting provider?
- Is the monitored IP address or domain correct?
Check for other causes
- Is the port only reachable from certain networks?
- Are there new security rules?
- Has a load balancer or proxy been changed?
- Is the service working locally on the server?
- Has the service been moved to a different port?
- Has there been maintenance or a migration?
💡
Service runs locally but is not reachable externally?
If the service works locally on the server but is not reachable from outside, the cause is often firewall rules, network permissions or upstream systems. If the service does not respond locally either, check whether the process is running and whether error messages are present in the logs.
Context
Limitations of Port Monitoring
Port Monitoring checks the reachability of a port. It therefore shows whether a connection to a specific service is possible in principle. However, this does not amount to a complete functional test.
Port Monitoring primarily detects
- whether a particular port is reachable
- whether a service will accept connections in principle
- whether a timeout occurs during connection establishment
- whether firewall or network issues are likely
- whether individual services fail even though the server is online
Not fully tested
- whether port 443 serves a website without 500 errors
- whether port 25 delivers emails correctly
- whether port 3306 allows successful database logins
- whether port 80 serves the correct website
- whether port 22 allows a login
- whether an API port returns functionally correct data
ℹ️
Port Monitoring is an availability check
A reachable port does not automatically mean that the application behind it is operating without errors. For websites, combining it with HTTP Monitoring is therefore useful. For HTTPS connections, SSL Monitoring should additionally be employed.
Combination
Combine Port Monitoring with other checks
Port Monitoring is particularly useful when combined with other types of monitoring via website monitoring tools. Each check examines a different technical layer.
Ping Monitoring
Checks whether a server is reachable over the network. It does not, however, indicate whether individual services are functioning.
HTTP Monitoring
Checks whether a website is reachable via a specific URL, which status code the web server returns and how quickly it responds.
SSL Monitoring
Checks whether the certificate for an HTTPS connection is valid and is renewed in time.
DNS Monitoring
Checks whether a domain resolves correctly and points to the expected destination.
Keyword Monitoring
Checks whether a website contains the expected content. This helps when a page responds technically but serves incorrect content.
Improved root-cause analysis
If Ping is successful but port 443 is not reachable, the issue is likely the web server service, the firewall or the HTTPS configuration. If port 443 is reachable but HTTP Monitoring reports an error, the connection is fundamentally working but the website application has a problem.
HOSTtest Plus
Port Monitoring with HOSTtest Plus
With HOSTtest Plus you can monitor individual ports at regular intervals. Website and server operators can specify which IP address or domain and which port should be checked.
This allows you to verify whether important services are generally reachable. If a port fails or a timeout occurs, a notification can be triggered. This helps you recognise issues more quickly before they remain unnoticed for an extended period.
Port Monitoring
Checks whether specific services and network ports are reachable.
Ping Monitoring
Checks basic network reachability.
HTTP Monitoring
Checks availability, status code and response time.
SSL Monitoring
Monitors certificates, expiry dates and HTTPS connections.
DNS Monitoring
Checks domain resolution, DNS records and expected values.
Keyword Monitoring
Checks whether the expected content is served.
Step by step
How to use HOSTtest Plus as a port monitoring tool
A port monitor can be set up quickly in HOSTtest Plus. After logging in, create a new monitor, select the appropriate monitor type and then specify which domain or IP address should be checked on which port.
1
Create an account or log in
First, create a free HOSTtest Plus account or log in with your existing credentials.
2
Create a new monitor
Open the Pulse → Monitors section in the menu. There you can create a custom monitor for a domain, an IP address or a specific service.
Screenshot: Creating a new port monitor in HOSTtest Plus
3
Select Port as the monitor type
Select Port as the monitor type. This causes HOSTtest Plus to check whether a specific network port on the chosen target system is reachable.
4
Enter domain or IP address
Enter the domain or IP address to be monitored. This could be, for example, a web server, mail server, gateway, load balancer or application system.
5
Specify the port
Specify which port should be checked. For websites, ports 80 and 443 are often relevant; for mail servers, for example, SMTP, IMAP or POP3 ports.
6
Choose the check interval
Choose how often the port should be checked. The more critical the monitored service, the shorter the interval should be.
7
Configure notifications
Decide how you want to be notified in case of a timeout, a failed connection or repeated outages.
8
Activate port monitoring
Enable port monitoring by clicking "Create monitor". From that point, HOSTtest Plus will automatically check the selected port at the set interval.
Screenshot: Status and results of your port monitor
✅
Conclusion: Port monitoring checks the availability of individual services
Port monitoring is an important complement to classic server and website monitoring. It shows whether a particular service is reachable on a specific network port.
This makes port monitoring more precise than a simple Ping. A server may be online in principle, while individual services such as web servers, mail servers, SSH, RDP or applications no longer function. Such cases can be detected more effectively with port monitoring.
At the same time, port monitoring does not replace a complete functional check. An accessible port does not automatically mean that the underlying application is working correctly. For reliable monitoring, port monitoring should therefore be combined with HTTP, SSL, DNS, Ping and keyword monitoring.
Write a comment
- Monitoring
Tags for this article
More web hosts
More interesting articles
Uptime and Downtime in Web Hosting Offers
If you are looking for a suitable web hosting provider, you will quickly come across information about the uptime or dow...
Set up Ping monitoring: How to keep an eye on your server
A website is unreachable, emails aren't working, or a server service has stopped responding? Ping monitoring regularly c...
Set up SSL monitoring: Keep track of your certificates
An expired or incorrectly configured SSL certificate can cause visitors to see a security warning, make logins appear in...
Monitor websites for free: A comparison of free website monitoring tools
In this article we look at the best-known free website monitoring tools and compare which features they offer in their f...
Server Monitoring: Uptime always in view
The permanent accessibility of your own server with fast response times is crucial for every commercial operator.
Server Outage - Prevention and Immediate Measures
A server outage is the worst possible news for a company. We show what can and should be done.
Media Partner:
