The site is down and nobody knows who hosts it
The first hour of an outage is spent finding out who can fix it, not fixing it. Here is how to find the host, the DNS and the registrar from outside, in the order that gets the site back fastest, and what to say when you reach them.
Last changed 26 October 2026, about 6 minutes to read
Minute 0: confirm it is down, and how
Open the site from a phone on mobile data, not the office network. Then note what you see, because the failure names the layer:
- “This site can’t be reached” or a DNS error: the name does not resolve. DNS or the registrar.
- A connection timeout or refusal: the name resolves, the server does not answer. Hosting.
- A certificate warning: the server answers, the certificate has expired or is wrong. Hosting, the certificate specifically.
- An error page from the site (500, “error establishing a database connection”): the server is up, the application is broken. Hosting or the application.
- A parking page, or someone else’s site: the domain has lapsed or been taken. The registrar, now.
Minute 5: find the layers from outside
Nothing here needs a login. Run the who-hosts check on the domain. It gives you the nameservers (so who serves the DNS), the mail records, and whose network the site’s addresses belong to. If the addresses belong to Cloudflare, the host is behind it and you need the Cloudflare account too.
Run the domain expiry checker. It names the registrar and says whether the domain has run out or is on hold. A domain that expired last week explains everything, and the fix is a payment, not a server.
If the error was a certificate warning, the certificate checker says when it expired and who issued it, which tells you whether the host or a separate service renews it.
Minute 15: find the person
You now know the companies. You need the accounts. Ask, in this order: the person who last worked on the site; whoever pays the invoices (finance will have the host’s name on a statement, and the registrar on another); the previous agency. Search the client’s shared inbox for the host’s name: welcome emails, invoices and renewal notices all carry the account email address.
If nobody has the login, hosts and registrars have account-recovery procedures, but they are built to refuse strangers: expect to prove you are the registrant with company documents, and expect a day. Start that process now, in parallel with everything else.
What to say to the host
Support queues move faster with specifics. Give them the domain, the exact error text, the time it started, and what you have already checked: the name resolves to their address, the certificate is valid, the server refuses connections on port 443. Ask two questions: is there an incident on their side, and is the account in good standing. An unpaid invoice suspends more sites than hardware failure does.
What to say to the registrar
If the domain has lapsed, ask for the renewal and the grace period in writing. Most registries allow a renewal at the normal price for a period after expiry, then a redemption fee, then deletion. If the domain is on hold, ask why: usually an unanswered verification email or a disputed payment.
When it is back
Before the relief wears off, write down what you learned: the host and its account holder, the registrar, who held the DNS, what the error was and what fixed it. The next outage should start at minute 15, not minute 0.
Stackbrace keeps that record for every site you look after, checks it against the world every day, and when a site goes down sends one message that names the layer that failed and who holds its login, with the first steps you wrote for it. See how it works, or check a site now.