Is it up or down?
Enter any website to find out if it’s working right now.
Recent checks
How it works
1. Enter a site
Type or paste a domain like example.com or a full URL. We handle the rest.
2. We check it
Our server connects to the target directly — no browser tricks, no CORS workarounds. A real HTTP request from our server to theirs.
3. You get the answer
A clear result: it’s up, it’s erroring, or it’s down. Plus timing, status codes, redirects, DNS, and TLS details if you want them.
What the results mean
The website responded with a successful HTTP status (like 200 OK or a clean redirect). It’s working normally from our perspective.
The server responded, but with an error code (like 404 Not Found or 503 Service Unavailable). The server exists and is online, but something is wrong with that specific page or resource.
We couldn’t reach the site at all. This could mean DNS failure (the domain doesn’t resolve), a connection timeout, connection refused, or a TLS/SSL error — the server simply isn’t responding.
What extra info do you get?
- Response time
- How long the request took from our server, in milliseconds.
- HTTP status code
- The exact status code returned (200, 301, 404, 503, etc.) with a short explanation.
- Redirects
- Whether the site redirected and where it ended up. Useful for spotting misconfigurations.
- DNS & IP
- The IP address(es) the domain resolves to. Helps confirm DNS is working.
- TLS certificate
- For HTTPS sites: who issued the certificate, when it expires, and how many days are left.
- Response headers
- Selected server headers like Server, Content-Type, and security headers.
Good to know
- We check from our server, not your browser. If a site is down for you but up here, it might be a local network issue, a regional outage, or IP-based blocking.
- Some sites return different responses to automated requests (bots) than to browsers. A 403 from our check doesn’t always mean the site is broken for you.
- We do not store or log what you check. Recent checks are saved only in your browser’s local storage.
- For security, we only check public websites. Requests to private IPs, localhost, or internal networks are blocked.
- HTTPS is tried first when you enter a bare domain. If that fails, we’ll try HTTP as a fallback and let you know.