Website Status Checker
Enter a URL or domain — the server will make an HTTP request and show the availability status, response code, response time, SSL certificate info, and server IP address.
Free online tool for checking website availability. Enter a URL or domain name and instantly find out if the site is up: HTTP response code, response time in milliseconds, SSL certificate status, and server IP address.
The tool performs a HEAD request to the specified server, allowing you to quickly check availability without downloading page content. Supports checking any public website over HTTP and HTTPS. Results are displayed with clear UP/DOWN badges.
Useful for webmasters, developers, and DevOps engineers for monitoring service availability, checking SSL certificates, and diagnosing network issues. All requests are made server-side — you get objective information about website availability from the internet.
How to use it
- Enter a URL or domain. Without a protocol https is assumed.
- The server sends a HEAD request and records the HTTP status, response time, IP address and SSL certificate details.
- 200–299 means the site responds; 301/302 is a redirect; 4xx is a client-side or access error; 5xx is a server error; a timeout means the server did not answer in time.
When it helps
- “It does not open for me”: tell whether the site is down for everyone or only for one user.
- After a deploy: make sure production answers 200 rather than a 502 from nginx.
- Partners and competitors: check an external API is up before writing to their support.
Frequently asked questions
The site opens in a browser but here I get 403 or 405. Why?
Some servers and CDNs block HEAD requests or requests without browser-like headers. That is a protection rule, not downtime.
What is a normal response time?
Up to 200–300 ms is excellent, up to a second is acceptable for server-rendered pages. More than 2–3 seconds usually points at overload or database problems.
Is the check made from your server or from my network?
From the legost.in server, so sites reachable only on a LAN or through a VPN cannot be checked.