Why my website isn’t reachable

When your website doesn’t answer, the cause is almost always one of three: nothing has been published yet, the address doesn’t point to us, or an old DNS record is in the way. The system check in your website’s overview tests this for you and says which one it is — that’s the fastest route, and for most findings there’s a button that fixes it.

The question is about the name first, not the server

With «website not reachable», the first question is whether the address resolves at all. An address without a DNS record looks exactly like a broken server from the outside — but it’s something else entirely, and fixed in minutes.

Certificate warning in the browser

That usually means the certificate couldn’t be fetched yet, and that in turn has to do with DNS: as long as the address doesn’t point to us, it can’t be issued. It catches up by itself as soon as the record is in place.

A foreign record alongside

The case that takes longest: next to the right record there is still an old one from the previous provider, often an AAAA record. Visitors and the certificate authority then end up at the wrong place. We report it together with the address it points to — deleting it is something you do at your provider.

In the chat with your assistant

Your assistant can run the same system check and start the fix. It shows you beforehand which steps will run and what they do – for example that the address moves and the old one redirects – and only goes ahead once you agree. No step changes your pages or publishes a draft; at most the version that was already live is transferred again. What can’t be fixed this way, such as a DNS record at another provider, it tells you along with the reason.

If none of this fits

Write to us, with your website’s address and what the system check says. Those are the two details that let us carry on looking straight away.