Connecting a domain is where most projects quietly die. Someone sends you a support ticket, someone else asks for a screenshot of your DNS panel, and a week later the site is still on a subdomain. It should be a form: you type the domain, you get told exactly which records to create, and something checks them until they resolve.
| The usual experience | 54 | |
|---|---|---|
| Adding the domain | A support ticket, or a plan upgrade first | A field in the panel |
| The DNS records | Generic documentation you have to interpret | The exact records for your domain, copyable |
| Knowing if it worked | Reload and hope | It checks and tells you what is still missing and why |
| SSL certificate | Sometimes manual | Issued automatically once DNS resolves |
| www and apex | A frequent source of "it does not load" | Both are served, whichever one you connected |
Written from each product's public documentation. Products change: check theirs before you decide. No prices here for the same reason.
Yes, from any registrar. You keep owning it — you are only pointing it here.
The setup is a minute. DNS propagation is usually under an hour, occasionally longer, and the panel keeps checking so you do not have to.
The panel shows the exact ones for your domain, including the verification record, ready to copy.
Yes, issued automatically and renewed automatically. There is nothing to buy or install.
Both the apex and www are served, whichever one you connected, because entering by the other one is the most common way a new site appears broken.
Yes.
The panel says which step failed — verification pending, DNS not pointing here, certificate still being issued — instead of a generic error. It tells you the record that is missing.
No. 54.wtf/your-name keeps working.
Yes, whenever you want. Change the DNS and take your files with you.
Yes: publishing, versions and one-click rollback. Publishing on a 54.wtf address is free; your own domain is part of a paid plan.