Check website status and HTTP response codes.
Server Status Checker requests a URL from our server and reports whether the site is up, the HTTP status code it returns, how long it took to respond, its SSL certificate status and the key response headers. Because the request comes from a server, it works for any public site and avoids the false results of browser-based checks.
Made for it and developers. Typical uses:
It makes a single request from one location, so it shows what our server sees, not a continuous uptime record from around the world. Only public http and https addresses on standard ports can be checked, with a few checks per minute.
Accuracy: Results reflect what the lookup returns at the moment you run it. Records and locations can change or differ between networks.
Syntax and format checks find broken markup, bad JSON and mistyped numbers, but not meaning, business rules, email deliverability or whether a URL is alive.
Three small technical SEO pieces that are easy to get wrong: what robots.txt, XML sitemaps and canonical tags each control, common mistakes, and how to test them.
A step-by-step way to find out why a site is down or misbehaving: check DNS records, then the HTTP status code and redirect chain, then domain expiry and your own IP.
Explore more in Network Tools, read the guides and articles, or see how we test our tools.
Check URL redirects and redirect chains.
Best for auditing a site's redirects for SEO after a domain migration
Look up DNS records for any domain.
Best for verifying MX records are set up correctly after configuring email
Find your public IP address and location details.
Best for verifying a VPN or proxy is actually masking your IP
Check domain registration details.
Best for checking when a domain is due to expire before it lapses
Find geographic location of IP addresses.
Best for investigating the origin of suspicious website traffic