Is My Website Down?
Check if a website is down for everyone or just you. You get an up or down verdict, the status code, response time, IP address, redirects and whether HTTPS is valid. Enter a site such as example.com.
- Free
- No signup required
- Live HTTP check
Common reasons a website is down
The site is up here but down for you
This check runs from TinyPing's server. If it says up and your browser says otherwise, the problem is probably local: a stale DNS cache, your ISP, a company firewall, a VPN or a browser extension. Try another network (for example mobile data) and flush your DNS cache.
DNS does not resolve
The domain has no A or AAAA record, the nameservers changed, or the domain itself expired. Look up the records with a DNS lookup and check the registration with a WHOIS lookup.
502, 503 or 504 errors
The web server or proxy answered, but the application behind it did not. 502 usually means the app crashed or is not listening, 503 means it is overloaded or in maintenance, and 504 means it took too long. Check your app process, its logs and the server's memory and disk.
Connection times out
Nothing answered in time. The server may be off, a firewall or security group may block ports 80 and 443, or the host may be overloaded. If only some visitors are affected, look at rate limiting or a web application firewall rule.
HTTPS fails but HTTP works
The certificate expired, does not cover this hostname, or the server is not sending its intermediate certificate. Browsers show a warning page, which visitors read as the site being down. Run an SSL check to see which one it is.
403 Forbidden for everyone
A security plugin, Cloudflare rule or wrong file permissions can block every visitor, including this checker. Review recent firewall and permission changes.
How to check if a website is down
- Enter the domain or full URL, for example example.com or https://example.com/login.
- Click Check website.
- Read the verdict, then the status code and response time.
- If it is up here but not for you, try another network and clear your DNS cache.
What does "website down" mean?
A website is down when a visitor cannot load it. That can happen at several layers: the domain does not resolve, the server does not accept the connection, the HTTPS handshake fails, or the server answers with an error status such as 500 or 503.
This checker makes one real request the way a browser would. It resolves the domain, connects, completes the TLS handshake, follows redirects and reads the final status code. A 2xx or 3xx final answer means up. A 4xx or 5xx answer, a timeout or a failed connection means down.
Because the request comes from TinyPing's server, it tells you whether the site is down for everyone or just for you. It is one location, so a problem limited to one country or ISP can still be missed.
GET / HTTP/1.1 Host: example.com HTTP/1.1 503 Service Unavailable Retry-After: 120
When to use a website down checker
A customer says your shop will not load
Check your Shopify or WooCommerce store from outside your office network before you start restarting things.
After a deploy or DNS change
Confirm the site answers with 200 and the right final URL after a Vercel, Netlify or nginx change, or after moving DNS to Cloudflare.
A third-party service seems broken
See whether an API or SaaS dashboard is down for everyone before you debug your own code.
WordPress shows a blank page
Check the status code: a 500 points to a plugin or PHP error, a 503 to maintenance mode or an overloaded host.
Check something else
- HTTP Status Code CheckerCheck the HTTP status code any URL returns, with response time and every redirect on the way.
- Website Response Time TestMeasure how long a website takes to respond, split into DNS, connect, TLS, server wait and download.
- SSL CheckerCheck a site's SSL certificate, expiry date and whether the intermediate certificate is installed.
- DNS LookupLook up A, AAAA, CNAME, MX, TXT, NS, CAA and SOA records for any domain, with TTLs, from public resolvers.
Frequently asked questions
Is the site down for everyone or just me?
If this checker says up, the site answers from the internet and the problem is likely on your side: DNS cache, ISP, firewall or VPN. If it says down, other visitors are very likely affected too.
Where does the check run from?
From TinyPing's server, one location. A site that is blocked or broken only in some regions can look fine here.
Does a redirect count as down?
No. The checker follows redirects and judges the final page. A redirect loop, or a chain that ends in an error, counts as down.
How do I flush my DNS cache?
On Windows run ipconfig /flushdns. On macOS run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. In Chrome you can also clear the host cache at chrome://net-internals/#dns.
Why is the site slow but not down?
A slow answer is still an answer. Use the response time test to see whether DNS, the connection, TLS or the server itself is taking the time.
Can I get told automatically when my site goes down?
Yes. A TinyPing HTTP monitor runs this check every 5, 15 or 30 minutes and alerts you by email, Slack, webhook or Google Chat after two failed checks in a row, then again when the site recovers.
Stop checking manually
Outages rarely happen while you are looking. TinyPing checks your site every 5, 15 or 30 minutes and alerts you when:
- the site returns an error status or times out
- the domain stops resolving
- an expired certificate breaks HTTPS
US$6.99 a month or US$47 a year per 50 monitors, team members free. 7-day free trial, no card needed.
Want alerts in team chat? Follow the guide for Slack or Google Chat.