Utility

Is It Down?

Check whether a website is reachable from outside your network, and interpret the result.

Last reviewed by the Radiatus Cloud team

Need this done properly for your business?

Radiatus delivers secure cloud, DevOps & compliance engineering.

Book a free consult

Down for you or down for everyone

A check from an independent network distinguishes a site-wide outage from a local problem. If the site responds elsewhere and not for you, the fault is between your device and the site — DNS cache, ISP routing, a firewall, a VPN, or a block applied to your address. Establishing which side the fault is on takes seconds and saves an hour of the wrong troubleshooting.

What each response means

Connection refused means a host answered and nothing was listening on that port. Timeout means no reply at all, typically a firewall dropping packets silently or a host that is unreachable. DNS failure means the name did not resolve, which is a different outage entirely — often an expired domain or a nameserver problem rather than a server one. A 5xx status means the server is running and the application is failing.

200 does not mean working

A site can return 200 while serving an error page, an empty template or a maintenance notice. Availability checks that only look at the status code miss the most common form of partial outage, which is why real monitoring asserts on page content rather than the code alone.

Regional outages are common

CDN and DNS problems frequently affect some regions and not others, so a single external check can report healthy while a whole continent cannot reach the site. Checking from several locations is the only way to see this.

Rule out the cheap causes first

A stale DNS cache after a record change, a VPN routing traffic through a blocked exit, an expired certificate producing a browser refusal that looks like an outage, or an IP-based rate limit from earlier testing. Each is far more common than an actual site failure and each takes under a minute to eliminate.

Related tools

  • User Agent Parser — Parse a User-Agent string into browser, engine, operating system and device. Explains why UA strings are unreliable and what to use instead.
  • QR Code Generator — Generate QR codes for URLs, text, Wi-Fi and contact details. Adjustable error correction and size, produced entirely in your browser.
  • Credit Card Validator — Validate a card number with the Luhn algorithm and identify the issuing network from its prefix. Runs locally, nothing is transmitted.
  • Text Case Converter — Convert text between camelCase, PascalCase, snake_case, kebab-case, CONSTANT_CASE, Title Case and sentence case. Runs entirely in your browser.

Frequently Asked Questions

How do I tell if a site is down for everyone?

Check from an independent network. If it responds elsewhere but not for you, the fault is local — DNS cache, routing, firewall, VPN or an IP block.

What is the difference between refused and timeout?

Refused means a host answered but nothing was listening on that port. Timeout means no reply at all, usually a firewall dropping packets silently.

Does a 200 response mean the site works?

No. A site can return 200 while serving an error page or maintenance notice, which is why real monitoring asserts on content rather than status code.

Can a site be down in only some regions?

Yes, and it is common with CDN and DNS problems. A single external check can report healthy while a whole continent cannot connect.

Privacy & Security

Runs in your browser. Nothing you enter is uploaded or stored.

Data: None
Server-side-Side
Active
v1.0

About This Tool

This tool runs entirely in your browser. No data is sent to any server, ensuring complete privacy. Simply use the interface above to get started — no registration or login required.

Disclaimer: This tool is provided "as is" without warranty of any kind. Results are for educational and utility purposes.