Skip to content
Noroxi

Is it down? Down for everyone or just meIs it down?

Tries to open the site from two separate locations and tells you whether it's down for everyone or just for your connection.

What this check looks at

  • One HTTPS request to the home page
  • Two locations: Frankfurt and Washington
  • HTTP status code and response time
  • CDN / bot protection detection
  • Days left on the certificate
What it reads and what it doesn't

One HTTPS request to the home page from each of two locations (up to 3 redirects followed). It reads the status code, response time, IP address, CDN headers and certificate expiry. Page content isn't stored.

Is it down, or is it just me?

When a site won't load, there are two possibilities: it's really down, or the problem is your connection, your DNS cache or your browser. This check tries to open the site from Noroxi's servers in Frankfurt and Washington. If both reach it, the site is up. If neither does, the problem is the site itself. If only one does, the problem is regional.

One HTTPS request to the home page from each of two locations (up to 3 redirects followed). It reads the status code, response time, IP address, CDN headers and certificate expiry. Page content isn't stored.

How to read the result

Up
Both locations got a 2xx or 3xx response. If you still can't get in, clear your browser cache, try another network (mobile data) or flush your DNS cache.
Down
Neither location got a response, or the server returned a 5xx error. The problem is the site's server, its hosting provider or the domain's DNS.
Down from one location
The site opens from one region and not the other. That points to an outage in one CDN region, a country block or a routing problem.
Bot protection
The server answered but showed a challenge page to the automated request (Cloudflare, for example). Real visitors can usually open the site.

Common problems and how to fix them

Every issue this check can flag, why it matters and what to change in DNS.

The site is down

Why it matters: No location could connect, or the connection timed out. Your visitors can't open the site.

What to do: Check your hosting provider's status page, make sure the server is running and that the domain's DNS points to the right IP. Also check that the domain hasn't expired.

The server returns an error

Why it matters: The server is reachable but returns an error instead of the page. 5xx errors usually mean an application, database or resource problem; Cloudflare's 52x codes mean the origin server couldn't be reached.

What to do: Check the server's error logs. For 502/504 check the application server (PHP-FPM, Node); for 503 check maintenance mode and server load; for 52x make sure the origin server is up.

Regional outage

Why it matters: The site opens from one region but not the other, so visitors in that region can't get in.

What to do: Check your CDN provider's status page and review any country or IP blocks in your firewall. Check again in a few minutes; temporary routing problems often clear on their own.

Bot protection

Why it matters: The site's security layer sent the automated check to a human verification page. That's not an outage.

What to do: If it's your site and you use monitoring, you can allow your monitoring service's IP addresses or user agent.

Slow response

Why it matters: Responses slower than 3 seconds cost visitors and search rankings.

What to do: Check server load, database queries and caching; serve static files through a CDN.

Frequently asked questions

Is the site down or is it just me?
Enter the domain above. If Noroxi's two servers can open it, the problem is on your side: try another network (mobile data), clear your browser cache and flush your DNS cache (ipconfig /flushdns on Windows). If neither can open it, the site is down.
What do HTTP 502, 503 and 504 mean?
502 means the front server got no valid response from the application behind it, 503 that the server is temporarily unavailable (maintenance or overload), and 504 that the server behind it didn't answer in time. All three mean the problem is on the site's side.
Can I get notified when my site goes down?
Yes. With a free account we check one site every 30 minutes and email you when two checks in a row fail. On the Pro plan checks run every 5 minutes.
Does this check put load on the site?
No. Each location sends a single request to the home page, the same as one visitor opening it. If the same domain is checked again within a minute, the previous result is shown.

Primary sources

More quick checks

Each one answers a single question about a single record. No account needed.

  • SPF record check

    Expands your domain's SPF record through every include, counts the DNS lookups it spends and flags the mistakes that send your mail to spam.

  • DKIM record check

    Finds your DKIM signing key in DNS, reads its type and length, and flags keys that are weak, stuck in test mode or revoked.

  • DMARC record check

    Breaks your DMARC record down tag by tag: what happens to spoofed mail, where reports go and whether external report addresses are authorized.

  • MX lookup

    Shows which servers receive email for your domain, in priority order, with each server's address, reverse DNS and provider.

  • SSL expiry check

    Shows when your certificate expires, how many days are left and who issued it. Checks the apex and www separately and adds a calendar reminder.

To see every check in one report:Site monitoring