Is google.com down?
Check whether a site is down for everyone or just for you, and exactly where it fails: DNS, the connection, HTTPS or the server itself.
Try: google.com · wikipedia.org · sitehostingfinder.com
UP google.com is up
The site answered with HTTP 200 OK in 143 ms.
Checked from our server Thu, 12 Nov 2026 14:40:15 UTC. If it's up for us but not for you, the problem is likely your connection, DNS cache or a regional block.
- HTTP status
- 200
- Server IP
- 172.253.63.100 · who hosts it?
- Server
- gws
- Timing
- connect 17 ms · TLS 22 ms · first byte 129 ms · total 143 ms
Redirects
- https://google.com/ → 301
- https://www.google.com/ → 200
How we check
- DNS: does the domain still point to a server? (Expired domains fail here.)
- Connection: does the server accept a connection on port 443 (HTTPS), or 80?
- HTTPS: does the secure handshake work?
- Response: what HTTP status comes back, and how fast? We follow up to four redirects.
What the result means
| Result | Likely cause | What to do |
|---|---|---|
| DNS failure | Domain expired, or A record deleted | Check the registrar and the DNS records |
| Connection refused / timeout | Server off, overloaded, firewall, or account suspended | Check your host's status page and account |
| HTTPS failed | Expired or wrong SSL certificate | Run the SSL checker |
| HTTP 500-504 | The application crashed, or the host's proxy can't reach it | Check error logs; on WordPress, a recent plugin update is the usual cause |
| HTTP 403 / 404 | The server is up but blocks or can't find the page | Not down: check permissions, firewall rules or the URL |
Up for us but down for you?
Try another network (phone on mobile data), flush your DNS cache, and check the propagation checker if the site recently moved hosts. A firewall or security plugin can also block some visitors or countries.
This is a single live check from our server, not a monitoring service. Sites that block automated requests may show 403 here even when they work in a browser.
FAQ
How do I know if a website is down for everyone?
Check it here. We connect from our own server, so if it works for us but not for you, the problem is between you and the site: your connection, DNS cache, or a regional block.
Why is a website down?
The most common causes are an expired domain, an expired SSL certificate, a server or hosting account problem, a crashed application (HTTP 500), or a traffic spike. The result above shows which step fails.
What does HTTP 503 mean?
Service unavailable: the server is up but can't handle the request right now, often during maintenance or overload. It usually resolves on its own.
My own site is down. What should I do first?
Check whether the domain and hosting account are paid up, then the host's status page, then your error logs. If it's a WordPress site, disabling the most recently updated plugin fixes many 500 errors.
CHANGING HOSTS?
DNS is where most migrations go wrong. Follow the hosting switch checklist, lower your TTL a day before, and use the propagation checker after the switch. Comparing new hosts? See real renewal prices.