Website Status Checker
Check if a website is up or down right now.
How to Use the Website Status Checker?
Find out instantly if a website is up for everyone or just down for you.
- 1
Enter the website address, for example example.com.
- 2
Click the Check Status button.
- 3
See whether the site is up and running or returning an error.
- 4
Check the Status code, Response time and Server IP.
- 5
If the site is up here but not for you, try clearing your browser cache or switching networks.
Benefits of Using Our Website Status Checker
Second opinion in seconds
Check from our server to see if a problem is with the website or with your own connection.
Response time included
See how quickly the server answered, not just whether it is online.
Follows redirects
The check follows redirects to the final page, so you see the real result.
Free and unlimited
Check any website, any time, without an account.
Who Can Use This Website Status Checker?
Website owners
Confirm an outage before contacting your host.
Online shoppers and students
Check whether a site is down for everyone.
Developers
Verify deployments and DNS changes quickly.
Support teams
Confirm customer reports of a site being down.
Frequently Asked Questions
Everything you need to know about the Website Status Checker.
How do I know if a website is down for everyone?
Enter the address here. If our server can reach the site and gets a normal response, the site is up and the problem is likely on your side, such as your internet connection, DNS cache or browser. If our check also fails, the site is probably down for everyone.
What do the status codes mean?
Codes in the 200 range mean success. 300 codes are redirects. 400 codes mean a client error, like 404 Not Found or 403 Forbidden. 500 codes, like 500 or 503, mean the server itself has a problem.
The site is up here but I still cannot open it. Why?
Try a different browser or device, clear your browser cache, restart your router, or switch from Wi-Fi to mobile data. Your network or internet provider might also be blocking the site, or your DNS may still point to an old server after a recent change.
What is a good response time?
Under 500 milliseconds is good for most websites, and under 200 milliseconds is excellent. Times above 1 to 2 seconds often point to an overloaded server or missing caching.
Related Tools
All Website ToolsSSL Certificate Checker
Check SSL certificate issuer, validity and expiry date.
WHOIS Lookup
See who registered a domain, when, and where.
DNS Lookup
Look up A, AAAA, MX, NS, TXT and CNAME records.
IP Lookup
Find the location, network and owner of any IP address.