Website Down? HTTP Status & Speed Checker
Is a website down for everyone or just you? See the HTTP status, every redirect, DNS/connect/TLS/first-byte timings and the security and caching headers.
Is the website down for everyone, or just for you? Enter an address and our server in Australia loads it like a browser would: it follows every redirect, shows the HTTP status, measures how long DNS, the connection, the TLS handshake and the server’s first byte take, and lists the security and caching headers it sent back.
How to use it
- Enter the address – just
example.comis enough; https is tried first. - Read the verdict at the top: up, an error page, or unreachable.
- Check the redirect chain, the timing breakdown and the security headers for anything to fix.
Common findings
- Slow first byte (over 800 ms) – the server takes long to build the page: add page caching, check PHP and the database.
- Several redirects – http → https → www → /home costs time on every visit. Redirect straight to the final address.
- 500 / 502 / 503 – the web server is up but the application behind it failed. Check the error log.
- Missing HSTS – browsers may still try plain HTTP first. Add
Strict-Transport-Securityonce HTTPS works everywhere.
Up here, down for you?
Your computer may still use an old DNS answer or a broken route. Run ipconfig /flushdns (Windows) or try your phone on mobile data. If it works there, the problem is your network or ISP – not the website.
अक्सर पूछे जाने वाले सवाल
It works here but not for me – what now?
The site is up, so the problem is between you and it: clear your browser cache, flush DNS (ipconfig /flushdns), try another network or phone data, and check whether your DNS still points to an old server.
What do the timings mean?
DNS is the name lookup, Connect the TCP handshake, TLS the HTTPS handshake and First byte the time until the server starts answering. A slow first byte usually means slow PHP, database or no page caching.
How many redirects are too many?
One redirect (http → https, or to www) is normal. Chains of three or more slow every visit and waste search engines’ crawl budget – point links straight at the final address.
और टूल्स
सभी टूल्स →Ping Test
Ping any website or public IP from our server: reply times, packet loss, jitter and TTL for each packet – check whether a host is up and how healthy the path is.
टूल खोलें Network troubleshootingTraceroute (MTR)
See every router between our server and a destination, with packet loss and latency per hop (MTR report) – find where a connection slows down or breaks.
टूल खोलें Network troubleshootingOpen Port Checker
Check from the internet whether ports are open, closed or filtered on a server or router – port forwarding, firewalls, mail, RDP, SSH and VPN in one test.
टूल खोलें