Confirming the server itself is listening
Beyond the page loading, we confirm your server is actually accepting connections on the ports that matter — catching a network-level failure a page check alone might miss.
A plain-language note on naming
You might see this called "ping monitoring" elsewhere — that usually means an ICMP ping, which is a different, lower-level check we don't run. What we do run is a TCP connection check: confirming a real connection can be opened on a given port, which is a more useful signal for a web server anyway.
- Ports 80 and 443 checked as critical, on every cycle
- SSH (22) and SMTP (25/587) checked as an informational signal only
- Only flagged if both web ports are closed — an HTTPS-only site with 80 closed isn't a false alarm
The details
- Runs alongside the main page check, same cycle
- Not a security or vulnerability scan — a connectivity confirmation only
- A single closed informational port (like SSH) is logged, not alerted on
Questions people ask
80 and 443 are checked as critical for every site; 22, 25 and 587 are checked informationally.
Not as a per-site configurable option today. If a specific port matters for your setup, tell us.
No — it's a simple connectivity confirmation, not a security audit or vulnerability scan.
See a real port check.
Bring a domain — we'll show you exactly what the connectivity check returns.