Domain search
Check a name before you commit: availability and price are resolved through the provider abstraction, not read from a static list.
DOMAINS
Your domain. Registered in your name.
Search, register, transfer, renew and manage DNS for your domain inside the same platform that runs your project — with the registrant record in your name, never the platform’s.
In development: the domain provider adapter runs sandbox-stage until provider credentials are connected, so no domain can be bought here today. Everything on this page is the design contract being built — and the ownership rule we will not bend.
One interface for the whole life of a domain.
The platform implements a domain provider abstraction, so the same actions work across registrars instead of locking you into one back office.
Registration
Create a new registration from the account you already deploy with, using the registrant contact you supply.
Transfer in
Bring an existing name across, including the auth code step and the approval that belongs to a registrar transfer.
Renewal and auto-renew
Manual renewal or auto-renew, with notifications sent ahead of the renewal date instead of after it.
Contacts
Registrant, admin, technical and billing contacts are stored per domain and editable in one place.
Auth code
Retrieve the transfer code for a name you own. It stays yours to move at any time.
DNS records
Manage records through one API across providers, so changing provider does not mean learning a new workflow.
DNSSEC
Enabled where the provider supports it. The abstraction exposes the capability only when the backend actually has it.
Ownership updates
A change of registrant is recorded as a real, auditable update — not a ticket you cannot follow.
Expiry notifications
Timed reminders before a name expires, rather than a surprise after the grace period.
Own-brand nameservers and DNSSEC are capability-gated: they appear for providers that support them, never as a promise the backend cannot keep.
Ownership is not negotiable.
The customer is the registrant. A customer domain is never registered as Hostingsurge property.
Domain ownership is the part of hosting people get burned by, so it is written down as a rule rather than a policy: the registrant contact on a domain bought or transferred here is you, or your organization — not the platform.
- The registrant field carries your name, your organization and your contact details.
- Hostingsurge acts as the registrar connector: search, purchase, renewal and DNS are provider operations performed on your behalf.
- Own-brand nameservers are displayed where the provider allows it, so the domain can look like your brand instead of ours.
- Transfer away is designed in from the start: auth code retrieval and standard transfer support are part of the adapter.
- If the platform ever changed hands, the names would still be registered to you.
Registrant record
- RegistrantYou or your organization
- Platform roleRegistrar connector only
- NameserversOwn-brand where supported
- Transfer awayAuth code on request
- Platform-owned customer namesNever
Connect the domain you already own.
A domain does not have to be bought here to be used here. This is the path being built for pointing an existing name at a project.
- Add the domain to your projectAdd the domain to a project in your account and see the records that are expected, before you change anything.
- Point DNS your wayKeep your current DNS provider and add the records yourself, or move the domain to the platform nameservers — your choice, not ours.
- Certificate issuedA certificate is requested and issued for the hostname as part of the attach flow, so HTTPS is never an afterthought.
- Preview before productionThe domain resolves to a preview first, so the real site can be checked on the real name before it becomes production.
- PublishPublishing moves the name to production for your project, with DNS and certificate state shown as its real state.
In development: attaching a custom domain end to end goes through the deployment executor, which is still open work. DNS records and certificates are real platform pieces today, but the customer-side attach-and-publish flow is not finished — treat this path as early access.
Billing rules that can be checked.
Domain margin is deliberately not the same as hosting margin, and every charge is a separate, confirmed action rather than a side effect.
- A purchase requires customer payment or credit — no silent spend.
- Every purchase and every premium name requires your explicit confirmation.
- Provider actions are idempotent: a retry cannot double-charge or double-register.
- Availability is re-checked at checkout, because a name can be taken between search and purchase.
- Wholesale cost and retail price are stored separately, so the margin is visible per domain.
No prices on this page: per-TLD retail prices are not published while the provider connection is sandbox-stage, because a price that cannot be honoured at checkout is not a price. When the adapter goes live, every price will be shown with country, currency, tax presentation, renewal price and billing cycle.
How domain billing is designed
- Wholesale vs retailStored separately per provider
- RegistrationPriced on its own
- RenewalPriced on its own, with cycle
- TransferPriced on its own
- RestorePriced on its own
- Premium namesExplicit confirmation required
- Country, currency, taxShown with the price
- Availability at checkoutRe-checked before payment
What is real today, and what is being built.
An honest split, taken from the platform’s own implementation status rather than from a roadmap slide.
| Capability | Stage | What that means |
|---|---|---|
| Domain search and pricing | Sandbox-stage | Runs against a sandbox implementation of the provider adapter; results are not a purchasable offer. |
| Registration, transfer, renewal | Blocked pending provider credentials | The flows are built against a provider interface. Turning them on requires live provider credentials. |
| DNS and DNSSEC management | Design contract | Designed to run across providers in one API. Provider support varies and is capability-gated. |
| Ownership in your name | Design rule, not a feature flag | Written into the adapter contract: the registrant is the customer. |
| Connect an existing domain | In development | Depends on the customer-side attach flow through the deployment executor. |
Straight answers about domains.
The questions that decide whether a domain is safe to keep with a platform.
Who owns a domain I buy here?
You do. The registrant contact is you or your organization, and a customer domain is never registered as Hostingsurge property. That rule belongs in the provider contract, not in the marketing copy.
When can I actually buy a domain here?
Not yet. Domain search, registration and transfer are in development and run against a sandbox adapter until the provider connection is verified. Join early access if you want to hear when purchasing opens.
Can I move the domain away later?
Yes. Auth code retrieval and standard transfer support are part of the design, so leaving is a normal operation rather than a negotiation.
Do I have to use your nameservers?
No. Keep the DNS provider you already use and add the records yourself, or move the domain to the platform nameservers and manage records in one place.
Is DNSSEC supported?
Where the provider supports it. DNSSEC is exposed as a capability, so it is shown for providers that have it instead of being claimed everywhere.
Get in early on domains.
Join early access — the account you create is the same one the domain flows will appear in, and prices will be shown in full when they can be honoured.