Finding it
Availability answered from the registry at the moment you ask, with the alternatives worth considering beside it rather than a page of upsells.
Buying a domain is the easy part. What follows is usually a week of records, nameservers, certificates and a support thread with somebody who did not sell you the hosting. Here the name arrives attached to the thing it points at.
Availability is checked against the registry itself, not a cached list.
What people bring here
A domain is only useful once it resolves, proves itself and renews. Each of those is a separate chore at most providers, and each is a separate way to be down.
Availability answered from the registry at the moment you ask, with the alternatives worth considering beside it rather than a page of upsells.
The records are written for you when you attach the name to something you are running. There is no zone file to hand-edit and no propagation to guess at.
Certificates are issued and renewed without being asked. The common outage — a certificate that quietly expired on a Sunday — is not a failure mode here.
Renewal is automatic and the expiry is shown long before it matters. A name does not lapse because an invoice went to somebody who left.
Most organisations do not know how many domains they own. They know about four providers, three corporate cards and one spreadsheet that is out of date. This replaces all of that with a list that is true because it is the system of record.
That gap is where launches slip. Not because anything is difficult, but because it is spread across three vendors and two teams, and each one is waiting on the other.
A name is checked against the registry when you ask about it. A cached answer is how two people register the same brand on the same afternoon and one of them finds out at checkout.
Point as many as you need at as many deployments as you need, without a ticket.
Both resolve and both hold a certificate, which is the detail most often missed.
Bring a name you already own and attach it without re-registering it.
A registration is paid at the point of purchase for the term you choose. A name is too easy to lose to a failed card to be billed any other way.
We launched on a Thursday because the name was available on a Thursday. Previously that sentence would have ended with the following month.
It is answered against the registry at the moment you ask. A cached list is how two people are told the same name is free, and one of them discovers otherwise at the point of payment.
No. A name registered here can point anywhere. Attaching it to something you run on the platform is simply the case where the records and the certificate are handled for you.
Yes. You can attach an existing name by pointing it here, and you can transfer the registration itself if you would rather hold everything in one place.
They are issued when the name is attached and renewed before they expire, without anyone asking for either. The common failure — a certificate that lapsed unnoticed — does not apply.
Upfront, for the term you choose, at the price shown before you confirm. Registrations are not metered and are not part of a free allowance, because a lapsed name is not a recoverable mistake.
Renewal is automatic by default and the date is surfaced well in advance. If you deliberately let a name go, the registry’s own grace and redemption periods apply.
Check what is available, register it, and point it at what you are building — in one sitting.
Paid upfront for the term you choose. Nothing to transfer afterwards.