Website Uptime Checker
Check if any website is up right now. Get HTTP status code, response time, full redirect chain, server header, and content size in seconds.
By Deepak Shukla — Founder & CEO, Pearl Lemon
Part of Uptime monitoring — the full answer, the facts and the alternatives in one place.
What This Tool Checks
- Whether the site responds with a 2xx or 3xx status (counts as "up")
- Final HTTP status code after following redirects
- Response time in milliseconds (TTFB-ish, server-side from our edge)
- Full redirect chain (every hop with its status code)
- Server header, content-type, and content-length
Why This Matters
A site being "up" isn't binary — it can return 200 OK and still serve a broken page, or redirect 7 times before settling, or take 12 seconds to respond. This tool surfaces all of that in one shot, with the actual data Google's crawler sees: status code, redirect chain, response time, and server header. For real ongoing uptime monitoring across multiple sites you need our paid product, but for one-off "is this site dead?" questions, this is faster than any monitoring dashboard.
How to Fix Issues
- 1.If you see a 5xx error, check your hosting provider's status page first, then your server logs
- 2.If response time is over 1500ms, you almost certainly need a CDN (or you have a database query problem)
- 3.A long redirect chain (>2 hops) is a CWV killer and an SEO disaster — collapse it to a single 301
- 4.If the site is up here but down for users, suspect a regional CDN issue, DNS propagation lag, or geo-blocking
- 5.For 24/7 monitoring, multi-region checks, and alerts on changes, sign up for LemWatch paid monitoring
"Is the site up?" is asked thousands of times a day across every engineering team in the world. Most of those checks could be answered faster than the asker can open their monitoring dashboard. This tool is the fast answer.
What "up" actually means
A site is "up" if it responds with an HTTP status code in the 2xx or 3xx range within a reasonable timeout (we use 12 seconds). 200 OK = perfectly up. 301/302 redirects = up but redirecting. 401/403 = up but requires auth. 404 = up but page not found. 5xx = down (server error). Connection refused / timeout / DNS failure = down (server unreachable).
What this tool returns, in plain language
- Status code: the final HTTP code after we follow all redirects. 200 is the only one that means "working normally for everyone."
- Response time: end-to-end time from when our edge function fires the request to when the response body is fully received. Note: this is measured *from our server*, not from yours — your latency may differ if you're in a different region.
- Redirect chain: every URL the site bounces through.
https://example.com → https://www.example.com → https://www.example.com/en/is three hops, two redirects. - Server header: what the origin (or CDN) admits it's running.
nginx,cloudflare,Vercel— useful for spotting infrastructure changes. - Content-type / content-length: confirms what was returned (HTML page? JSON API? Image?) and how big it is.
Common patterns you'll see
The www-canonicalisation redirect: example.com → www.example.com. One hop. Normal. Caching makes this nearly free.
The HTTPS upgrade redirect: http://example.com → https://example.com. One hop. Mandatory in 2026.
The geo-language redirect: example.com → example.com/en/ → example.com/en/home/. Two hops. Adds latency for every first-visit user and tanks LCP. Replace with server-side detection or a single 301.
The tracking-parameter redirect: site adds ?utm_* then strips it again. Pointless hop. Eliminate.
When response time looks bad
Anything over 600ms TTFB is uncomfortable; anything over 1500ms is a problem. Common causes, in order of frequency: shared hosting under load, no CDN, blocking database query in the request lifecycle, server in the wrong region for the user base, plugin/middleware overhead (WordPress especially). The fix sequence is usually: CDN first (free Cloudflare), then move to better hosting, then optimise queries.
One-shot check vs. continuous monitoring
This tool answers "is it up right now?" in real time. For "was it up at 3am last Tuesday?" or "alert me when it goes down," you need continuous monitoring: scheduled checks every 1-5 minutes from multiple regions, SLA tracking, incident timeline, on-call alerting. That's what LemWatch's paid product does — this free tool is the one-shot version.
Methodology
From our edge function (US-East region), we send a GET request to the URL with User-Agent: LemWatchUptime/1.0, a 12-second timeout, and redirect: manual so we can capture every hop. For each redirect we record the URL and status code, follow up to 8 hops, and consume the body (to avoid resource leaks). We measure total wall-clock time from request fire to body received and report it as response_time_ms. We capture the Server, Content-Type, and Content-Length headers from the final response. The is_up verdict is true if the final status is 200-399, false otherwise (including timeouts, DNS failures, and connection refused). Single-region by design — for multi-region uptime checks, use our paid monitoring tier.
Frequently Asked Questions
This tool also answers
Is it just me or is the website down for everyone?
This check runs from our servers, not your network. If it reports the site as up while your browser cannot reach it, the fault is local — DNS cache, VPN, ISP route or firewall — rather than the site being down.
How do I check if a website is up right now?
Enter the domain and the tool makes a live HTTP request immediately, returning the status code and response time. A single check tells you the state right now; continuous monitoring is what catches the outage you are not watching for.
Related Free Tools
SSL Checker
Check if your SSL/TLS certificate is valid, properly configured, and when it expires. Get instant results for any URL.
DNS Lookup
View all DNS records for any domain — A, AAAA, CNAME, MX, TXT, NS records. Verify DNS configuration instantly.
Malware Checker
Check any site for malware, phishing and unwanted software using the Google Safe Browsing list. Instant result, no signup.
HTTP Status Code Reference
Understanding HTTP status codes helps you diagnose issues found by this tool: