Skip to content
On this page

Advanced

Uptime troubleshooting

When your site goes Down or Needs attention, every second counts — and so does knowing exactly what to do next. This section tells you what's happening and how to put it right, so you can get back to a green dashboard fast.

Not sure what you're looking at? The site is down page matches your symptom to the specific problem.

Connection issues

The request never reaches your server. Here's how to tell which one you've hit.

  • Connection refused — the server actively rejected the connection. Usually a stopped web server, firewall rule, or the server binding to localhost only.
  • Connection timeout — nothing replied within the timeout window. Usually server overload, a deadlocked process, or a network black hole.
  • DNS resolution failed — the domain couldn't be resolved to an IP address. Could be an expired domain, missing records, or a nameserver problem.

HTTP response issues

The server responds, but with an error code instead of your page.

  • HTTP 4xx response — the server rejected the request. Common causes are authentication requirements on the checked URL, WAF rules, or a moved page.
  • HTTP 5xx response — the server returned an error. Covers 500 application crashes, 502/504 upstream failures, and 503 service unavailable.

Performance issues

The site loads, but slowly enough that your visitors notice.

  • Site responding slowly — the site responds, but too slowly, so DomainDash marks it Needs attention. Guides you through finding the bottleneck, whether it's DNS, the server, or content delivery.

Common questions

  • Site is down — a routing page from the user-facing symptom to the specific failure causing it.

Catch this automatically

DomainDash keeps an eye on this for you — and tells you in plain English the moment something needs your attention, before your visitors notice. Set up in under a minute, no credit card.