Register or transfer in
Check availability and pricing, then register a new domain or transfer one from your current registrar.
Deployxa Domains
The whole domain lifecycle, in one place.
Registration, transfer-in, managed DNS, edge routing, renewal and automatic TLS, scoped to your organization.
- 01Registeredrenews yearly
- 02DNS recordsA · CNAME · TXT
- 03Edge routingactive
- 04TLS certificateLet's Encrypt
01 / Capabilities
Everything a domain needs.
Managed DNS
Create and manage A, AAAA, CNAME, MX, TXT and SRV records.
Edge routing
Purchased domains point at the active Deployxa ingress automatically.
Automatic TLS
Certificates are issued once DNS ownership and routing checks pass.
02 / Lifecycle
How it works.
- 01 /
Check
See availability plus registration, transfer and renewal pricing.
- 02 /
Register or transfer
Register a new domain, or transfer one in with its EPP auth code.
- 03 /
Configure
Add registrant contact details on first purchase; DNS and edge routing are set up for you.
- 04 /
Manage
Renew, validate transfers, edit records and watch DNS, TLS and expiry in one place.
03 / DNS records
Every record type you need.
Registrar-managed domains get a full DNS editor. Each record has a name, a value and a TTL; MX and SRV records also take a priority.
| Record | What it does | Example |
|---|---|---|
| A | Points a name at an IPv4 address. Use it for an apex (root) domain. | @ → your Deployxa ingress IP |
| AAAA | Points a name at an IPv6 address. | api → 2001:db8::10 |
| CNAME | Aliases one hostname to another. Use it for subdomains such as www or app. | www → the CNAME target shown in the dashboard |
| MX | Routes email for the domain to a mail provider. Takes a priority value. | @ → mail.example.net, priority 10 |
| TXT | Free-form text: ownership checks, SPF, DKIM and DMARC. | _deployxa-challenge → deployxa-verification=… |
| SRV | Advertises a service on a host and port. Takes a priority value. | _sip._tcp → 10 5 5060 sip.example.net |
Example values are illustrative. The dashboard shows the exact ingress IP and CNAME target for your project.
04 / External registrar
Keep your registrar. Point it here.
Add the domain to a project and Deployxa shows the records to create at your current DNS provider. Once they resolve, verify the domain and routing and HTTPS switch on.
- Apex or root domain: an A record to the Deployxa ingress IP
- Subdomain such as www or app: a CNAME to the target shown for your project
- Behind a CDN or proxy: a TXT record at _deployxa-challenge to prove ownership
- Retry verification any time from the domain manager or with deployxa dns
- 01A record (apex)ingress IP
- 02CNAME (subdomain)project target
- 03TXT ownership_deployxa-challenge
- 04Verificationretry
05 / Transfer in
Moving a domain from another registrar.
Transfers follow the standard registry process. Most of the waiting happens between registrars, so plan it outside a launch window.
- 01 /
Unlock at your current registrar
Turn off the transfer lock (often called registrar lock) and make sure the domain is not inside a recent-registration or recent-transfer lock period.
- 02 /
Get the EPP auth code
Request the authorization code from your current registrar. It proves you control the domain, so you never share your registrar login.
- 03 /
Start the transfer
Choose the project, paste the EPP code, decide on WHOIS privacy and add registrant contacts if this is your first purchase. The order appears as pending transfer.
- 04 /
Validate and finish
Use Validate to re-check progress, or Cancel while it is still pending. Your current registrar may also send an approval email you can accept to speed things up.
06 / TLS
HTTPS without the certificate chores.
Issued after verification
When DNS points at the Deployxa ingress and the ownership check passes, a Let's Encrypt certificate is requested for the hostname. Until then the domain shows SSL pending.
Renewed in the background
Let's Encrypt certificates are short-lived (90 days), so renewal is automatic. You never upload or rotate a certificate by hand.
Failures are surfaced
DNS, TLS and renewal failures raise alerts in the domain manager, and domains that stop resolving to Deployxa are flagged with a retry button.
Works behind a proxy
If a CDN or proxy hides your origin record, add the TXT ownership record so verification can still succeed.
07 / FAQ
Domain questions.
Do I have to buy my domain from Deployxa?
No. You can keep it at any registrar and point it at Deployxa with an A record (apex) or a CNAME (subdomain). Buying or transferring through Deployxa just puts registration, DNS and routing in one place.
How long does a domain transfer take?
It depends on the registry and your current registrar. For common generic TLDs a transfer usually completes within about five days, and sooner if the current registrar approves it. Keep your existing DNS live until it finishes.
Why is my domain stuck on SSL pending?
A certificate is only requested after DNS resolves to the Deployxa ingress and ownership is verified. Check that the A or CNAME record matches the value in the dashboard, add the TXT record if you use a proxy, allow time for propagation, then retry verification.
How long do DNS changes take?
Usually minutes, but resolvers can serve cached answers until the old TTL expires. The editor accepts TTLs from 60 seconds to 86,400 seconds (one day), with 3,600 as the default.
Can I use my own nameservers?
Yes. For registrar-managed domains you can replace the nameservers (at least two are required). Records you manage elsewhere then need to point at Deployxa yourself.
How are domains billed?
Registrations, transfers and renewals are paid from topped-up account credit and each creates a paid invoice. Promotional credits cover compute and plans, not domains. Prices are shown before you confirm.
Are custom domains and HTTPS included on the Free plan?
Yes. Connecting a custom domain and automatic HTTPS are included on every plan, Free through Enterprise.
Ready when you are
Bring your domain.
Point it at Deployxa or buy a new one, and HTTPS is handled for you.