Skip to content
EnterraHost
Products
Tools
Hosting Email Support Client Area Find a domain
Easy utilities

Server Check

A comprehensive health audit that verifies server reachability, SSL validity, and CDN performance. It ensures your site is correctly configured and accessible across both modern and legacy IP versions.

Checks both address families and reports each separately. Public domains only.

Lists the security headers the server sends, such as HSTS, CSP and X-Frame-Options, and whether each one is present.

Email me this result

The same result, sent to your inbox.

We use the address to send this result. It is not stored after the message goes out, and nothing is added to a list unless you tick the box.

Need somewhere to put the site? Hosting from $4.95 a month, with free DNS on every domain you own.

What comes back

Four answers in one request.

Does it answer

The HTTP status the server returned, and the address family it used. A response of any kind proves the web server is alive, which is a stronger claim than a ping.

How fast

Total time for the request, with the TLS handshake broken out separately. A slow handshake and a slow application are different problems with different fixes.

Is the certificate sound

The TLS version, who issued the certificate and how many days are left on it. An expired certificate turns a working site into a browser warning.

Which family works

IPv4 and IPv6 are tested separately. One can work while the other fails, and the failing one is only visible to the visitors unlucky enough to be on it.

Two traps

What an outside check cannot see.

A CDN hides the origin

If the site sits behind a CDN, the request never reaches your server. Every number here describes the edge nearest the region you chose. Your origin can be down and this check will still look healthy if the edge has a cached copy.

A blocking firewall looks like a failure

A request refused by a firewall can come back as a 403 or a 429 rather than as a connection error, and a network that drops the packets silently can look like a dead server. Read the status code before assuming the machine is down.

Next

When the server is fine but it still feels slow.

A clean result here means the server answered quickly and the certificate is sound. If visitors still wait, the delay is either distance or the page itself.

The full walkthrough is in how to read a server check result, including what an outside check cannot see.

Questions

Questions about a server check.

Can I get the result by email?
Yes. Run the check, then press the paper plane beside the result and give it an address. The message carries the same figures the page shows, any table the result produced, and on the map tools the diagram itself as an attached vector file. Nothing is stored unless you tick the box asking to hear about new tools and trials, and if you do, the message carries a link that removes you again.
What does this check that a ping does not?
A ping only proves a machine answers ICMP. This makes a real HTTP request, so it proves the web server responds, reports the status code, reads the certificate as a browser would, and measures how long the request took. A host can ignore ping and still serve a website perfectly.
Why does the result show a CDN instead of my server?
Because a request to a site behind a CDN is answered by the edge closest to the region running the check, not by your origin. That is the design working correctly. The measured response time therefore describes the edge, and a problem on your origin can be invisible from outside.
What is a TLS handshake and why is it a separate number?
It is the negotiation that establishes the encrypted connection before any page data moves, covering the certificate exchange and the key agreement. It is reported apart from the total because a slow handshake and a slow server are different faults. A fresh connection always pays it, and a resumed connection mostly does not.
How long should a certificate last?
That is set by the certificate authority, not by you or us. Public certificates are issued with a validity period chosen by the issuer, and shorter lifetimes have become the direction of travel across the industry. What matters in practice is that renewal is automated, so expiry never depends on someone remembering a date.
What does HTTP/3 mean here?
It means the server negotiated HTTP/3 for this request, which runs over QUIC rather than TCP. It mainly helps on lossy or mobile connections, where the older transport slows down more sharply. A site without it still works, it simply gives up some resilience on bad networks.
Why do IPv4 and IPv6 show different results?
Because they are different paths to the same place. One family can connect while the other fails, which is exactly the misconfiguration worth finding, since visitors on the broken family see an error and visitors on the working one never notice. A failing IPv6 route with a published AAAA record is the worst case, because it sends some visitors to a dead end.