Free Tool
Website Uptime Checker
Check if any website is online and healthy. Get a full health report covering DNS, SSL, security headers, performance, and content - with grades for each category.
What You Get
Here's an example of the health report this tool provides. Try it above with any website.
Website is Up & Healthy
https://example.com — 187ms response time
Category Grades
Key Findings
The uptime checker performs a deep analysis of your website across seven categories. DNS resolution verifies your domain resolves correctly and measures lookup speed. SSL/TLS checks certificate validity, expiry, and protocol version.
Security headers evaluate protection against common web attacks — HSTS, CSP, clickjacking prevention, and more. Performance measures response time, TTFB, content size, and compression. Content health checks that your page has proper HTML structure (title, meta description, favicon) and isn't returning an error page.
How It Works
Enter URL
Type any website URL. We'll resolve the domain, follow redirects, and analyze the full response.
Deep Health Analysis
We check DNS, SSL, redirects, response time, TTFB, security headers, compression, and page content in parallel.
Get Your Report
View grades for each category with detailed explanations. Copy, share, or download the full report.
Website Health Glossary
The terms behind every grade in your health report — without the marketing fluff.
Uptime
Percentage of time a service responds correctly. Three nines = 99.9% (≈ 8.7 hours of downtime per year). Four nines = 99.99% (≈ 52 minutes per year). The number sets your engineering budget — every additional nine costs roughly an order of magnitude more.
TTFB
Time To First Byte. The wall-clock time from request sent to first response byte received. Includes DNS, TCP, TLS, and server processing. A core Web Vitals input — Google considers under 800 ms 'good' and over 1.8 s 'poor'.
HSTS
HTTP Strict Transport Security. A response header that locks the browser to HTTPS for the configured max-age. With the preload directive, your domain ships in browser binaries, so even the first connection is HTTPS.
CSP
Content Security Policy. The most effective in-browser defence against XSS. Restricts which sources can load scripts, styles, frames, and connect-src endpoints. Best deployed in report-only mode first, then enforced.
Core Web Vitals
Google's user-experience metrics that influence ranking. LCP (Largest Contentful Paint) measures load speed; INP (Interaction to Next Paint) measures responsiveness; CLS (Cumulative Layout Shift) measures visual stability. TTFB feeds into LCP.
Compression (gzip / brotli)
Compresses HTTP responses before sending. gzip is universal; brotli is newer and ~15% better for text. Mandatory for HTML, CSS, JS, and JSON. Already-compressed payloads (images, video) should not be double-compressed.
Status page
A public page that reports current operational status. Communicates incidents transparently to users without overwhelming support. exit1.dev includes managed status pages on every plan.
Common Issues That Hurt Your Grade
The findings that drag the overall score down — what each one means and how to fix it.
Connection timeoutServer did not respond in time
Either the host is overloaded, a firewall is dropping packets, or the path is broken. Test with the ping tool to see if TCP can connect at all. If TCP connects but HTTP times out, the application layer is the problem.
DNS resolution failedDomain does not resolve
NXDOMAIN, SERVFAIL, or no answer. Check that the domain is registered and that nameservers respond. If you just made a change, propagation can take from minutes to 48 hours depending on TTL.
SSL certificate expiredTLS certificate has passed its expiry date
Browsers block the page completely. Renew immediately. The SSL Checker tool shows exact validFrom/validTo and which CA issued the certificate. Modern setups (Let's Encrypt, Caddy, Cloudflare) auto-renew — re-enable it.
5xx server errorsApplication is broken
500/502/503/504 mean the server reached you but the app failed. Check application logs and your error tracker. Recent deployments are the most common cause.
Slow TTFB (> 600 ms)Server is slow to first byte
Hurts perceived performance and Core Web Vitals. Common causes: slow database query on the home page, no CDN, unoptimised render path, or under-provisioned servers. Profile the slow request to find the bottleneck.
Missing HSTSNo HTTPS enforcement
Without HSTS, the first request after typing http:// is vulnerable to a downgrade attack. Add Strict-Transport-Security with at least max-age=31536000 once you are confident in your HTTPS setup.
Missing CSPNo Content Security Policy
CSP is the strongest defence against stored and reflected XSS. Without one, any injected script can run with full page privileges. Start with a report-only policy, watch the violations, then enforce.
No compressionResponses sent uncompressed
Without gzip or brotli, text payloads are 4–10× larger than they should be. Hurts bandwidth costs and load time. Enable at the CDN or origin — almost every server framework supports it with one flag.
Frequently Asked Questions
Learn More About Website Monitoring
Guides on uptime monitoring, security headers, and website performance.
How to Check If a Website Is Down
Step-by-step guide to verifying outages, checking status codes, and diagnosing server issues.
HTTP Security Headers Explained
Complete checklist of security headers: HSTS, CSP, CORS, and how to implement them.
API Endpoint Monitoring Playbook
Build a comprehensive API monitoring strategy with validation, alerts, and global coverage.
API Observability Automation Toolkit
Automate API monitoring with payload validation, status automation, and incident response.
Last updated · Built and maintained by exit1.dev — uptime, SSL, and domain monitoring with instant alerts.
Need Continuous Uptime Monitoring?
Stop checking manually. exit1.dev monitors your websites 24/7 with checks every 2 minutes from multiple regions. Get instant alerts via email, Slack, Discord, or webhooks when something goes wrong.
Start Free Monitoring