Is my website down?
One-click check for HTTP status, SSL expiry, DNS, and response time. No signup. No ads. Clean answer in under five seconds.
Checked from our us-east region. We follow redirects and verify the full TLS chain.
Paste a URL above. We'll run HTTP, SSL, DNS, and timing checks in one go. Nothing is stored.
How it works
Four passes, 2–5 seconds, zero storage.
Step 1
Resolve DNS
We look up A, AAAA, and CNAME records for the domain and verify that nameservers return consistent answers.
Step 2
Open the TLS connection
We handshake over TLS on port 443 and read the full certificate chain — issuer, expiry, chain validity. We run this check for every host so you can spot a cert problem even if you entered the URL as http://.
Step 3
Send an HTTP HEAD request
We request the URL with HEAD (to avoid pulling the response body), a ten-second timeout, and up to three redirects — then record the final HTTP status, final URL, and response headers.
Step 4
Break down the timing
We split total response time into DNS, TCP, TLS, TTFB, and download. Most performance problems surface in one specific stage — the breakdown tells you which.
We check from a single region (us-east) via Cloudflare Workers. If you need multi-region monitoring, set up a Drumbeats monitor — it checks from up to 6 regions every minute.
Coverage
What the check covers
We check
- HTTP status code + response body size
- Final URL after redirects (up to 3 hops)
- TLS certificate issuer, expiry, chain validity
- DNS A/AAAA/CNAME records + nameserver consistency
- Total response time + DNS/TCP/TLS/TTFB/download breakdown
- Basic WAF/firewall block signals
We don't check (yet)
- Security headers (HSTS, CSP, X-Frame-Options)
- Multi-region availability
- Content-level checks (keyword present, JSON schema match)
- Historical uptime — this is a snapshot, not a record
- Browser-rendered checks (JS execution, Core Web Vitals)
Multi-region checks, content monitoring, and historical uptime are available with a Drumbeats monitor.
Examples
Try it on one of these
Mix of working sites and deliberately broken ones — so you can see what each state looks like.
FAQ
Common questions
Yes, entirely free. No signup, no account, no rate limit for reasonable use. We limit to 10 checks per minute per IP to keep it fair, but that's the only ceiling.
We check from a single server region (us-east). If the issue is on your ISP, a specific geographic region, or your own network, we won't see it. Our check tells you whether the public internet can reach your site — not whether you can. If you need multi-region checks, set up a Drumbeats monitor with checks from multiple regions.
The most common causes are: (1) the site is blocking our check IP or user agent (WAF rules), (2) the site was briefly down at the exact moment we checked, or (3) there's a DNS or SSL problem that affects our region but not yours. Hit Check again to rule out a flake.
We open a TLS connection to your domain on port 443, read the server's certificate chain, and report the issuer, subject, expiry date, and chain validity. We don't store the certificate. If expiry is within 30 days we flag it as warning; if already expired, we flag it as critical.
We flag total response time over 1.5 seconds as slow. TTFB (time to first byte) over 800 ms also triggers a slow warning even if total load time is OK — because high TTFB almost always means a backend issue. These thresholds are conservative; Google's recommendation for good TTFB is under 800 ms.
You can, but this tool checks the technical status of a single URL from our region. For crowdsourced outage reports on major services where thousands of users are reporting simultaneously, Downdetector is the right tool. We're built for checking your own sites and services.
TTFB — Time To First Byte — is the time between the HTTP request being sent and the first byte of the response coming back. High TTFB means your server is slow to respond, which is almost always a backend problem (database, app server, middleware). Separating it from total load time tells you whether to blame the network or the backend.
We keep an anonymized count of check volume for rate-limiting and capacity planning. We don't store the URLs you check, the results, or any association between your IP and the URL. If you want a persistent record of checks for your own sites, that's what a Drumbeats account is for.
Those are continuous monitoring products — they check your site every N minutes and alert you on failures. This page is a one-shot diagnostic. If you want continuous uptime monitoring, Drumbeats does that with multi-region checks and SSL expiry alerts built in.
From one-shot to continuous
A single check tells you what's happening right now. Drumbeats tells you the moment it changes.
The down checker runs once. Drumbeats runs every minute from multiple regions, alerts your team within seconds of an outage, and turns each monitor into a public status page in one click — free for up to 50 sites.
Free for up to 50 monitors · Setup in 60 seconds · No credit card required
More free tools