Website status checker
Enter any domain and we will make a real request to it from our server in London — then show you the status code, how long each stage took, where it is hosted and what it is running.
What the results tell you
A website check is not one measurement, it is four, and they fail in different ways. GoodPing separates them so you can tell a hosting problem from a DNS problem from a certificate problem.
HTTP status code
200 means the page was served normally. 301 and 302 are redirects — fine in themselves, but each one adds a round trip. 403 means the server understood you and refused; on a live check that usually means a firewall or bot filter is blocking automated requests rather than the site being broken. 404 is a missing page, not a dead site. 500–504 are the ones that matter: the server itself, or the gateway in front of it, is failing.
Load time and first byte
Time to first byte (TTFB) is how long the server took to start answering. Anything under 200 ms is excellent, up to 500 ms is normal for a dynamic site, and past a second you are looking at slow database queries, a cold cache or an overloaded host. Total time includes downloading the HTML — a large TTFB with a small total means slow server; a small TTFB with a large total means a heavy page.
When there is no response at all
We report the reason rather than a blank "down". Could not resolve host is DNS: the domain has no working nameserver answer, which often means an expired domain or a broken DNS change. Connection refused means the server is reachable but nothing is listening on that port — the web server process is down. Timed out means packets are disappearing: a firewall, a routing problem, or a machine that is up but wedged. TLS error means the site answers but its certificate is expired, mismatched or misconfigured, and browsers will refuse to load it.
FAQ
The check says my site is up but I still cannot open it
Then the fault is between you and the site. Flush your DNS cache, try the site on mobile data instead of your home broadband, and try a different browser. If it works on mobile data, your ISP resolver or router is the problem.
Why does the checker get a 403 when my browser works fine?
Bot protection. Cloudflare, AWS WAF and similar services often challenge requests that are not from a real browser. It means your site is up and defended, not broken.
Do you check from more than one location?
Checks run from our London server. That is deliberate: one honest vantage point, clearly stated, is more useful than an unverifiable claim of dozens.
Related reading
Other tools
Ping test
Round-trip latency and packet loss.
DNS lookup
A, AAAA, MX, NS, TXT, SOA and CAA records.
SSL certificate checker
Expiry, issuer, chain and hostname match.
HTTP header & security check
Every response header, graded for security.
Open port checker
Which TCP ports answer from the outside.
WHOIS lookup
Registrar, age, expiry and nameservers.
Want this checked automatically?
Free monitoring every 5 minutes with email alerts when something breaks.