Ship
Custom domains
Connect a domain you own and serve your app over HTTPS on your own address.
A custom domain puts your app on an address you own — acme.com or app.acme.com instead of the default your-app.vorx.live. It makes your product look more trustworthy, helps SEO, and is easier to share.
Custom domains are available on paid plans.
Connect a domain you own
Point DNS at Vorx from any registrar. Two records and a few minutes.
Before you start
You'll need three things:
A published app
A domain can only point at a live deployment, so deploy first.
A paid plan
Custom domains are included on every paid tier.
DNS access
Wherever you manage records — Cloudflare, Namecheap, GoDaddy, and so on.
Everything below starts from the Publish dialog in your project — the same place you set your .vorx.live address.
Connect a domain you already own
Open Publish → Connect domain and enter your domain. Vorx shows the exact records to add — one for the apex (acme.com) and one for www.
Type
AName / Host
@Value
(copy the IP shown in the Publish dialog)Using Cloudflare, DNSimple or Netlify DNS?
Prefer an ALIAS / ANAME record at the apex pointing to cname.vorx.live — it follows Vorx if the address ever changes.
Type
CNAMEName / Host
wwwValue
cname.vorx.liveType
TXTName / Host
_vorx.acme.comValue
vorx-verify=xxxxxxxxAdd the records, then click Verify.
DNS changes usually apply within minutes but can take up to 48 hours to propagate worldwide.
HTTPS is automatic
Free SSL, auto-renewed
As soon as a domain verifies, Vorx issues an SSL certificate and serves your app over HTTPS. Certificates renew themselves — nothing to install or rotate.
Choose a primary domain
When you connect both acme.com and www.acme.com, mark one as primary. Vorx serves your app there and 301-redirects the other to it, so you never split visitors — or SEO — across two addresses.
Domain statuses
- Pending
Records detected, waiting on propagation and verification.
- Active
Verified and serving your app over HTTPS.
- Error
A record is missing or wrong. Open the domain to see which one to fix.
Use a CDN or reverse proxy
Two things to watch
Fronting Vorx with Cloudflare works, but keep the record DNS only (grey cloud) until the domain verifies and SSL is issued, then re-enable proxying — and use Full (strict) SSL mode so the proxy validates Vorx's certificate.
Troubleshooting
- Verification keeps failing. The record probably hasn't propagated, or the host is off — many registrars want
@for the apex and justwwwfor subdomains. wwwworks but the apex doesn't (or the reverse). You're missing one of the two records.- Site won't load though it's Active. Old DNS is cached locally; try a private window.
- Certificate warning. SSL is still being issued; wait a few minutes after Active.
Check what the world sees with dig acme.com +short or dnschecker.org — the values should match what Vorx gave you.
FAQ
Yes — anywhere you can edit DNS records.
No. Leave it where it is and just point DNS at Vorx. Buying through Vorx is optional convenience.
Yes. You only touch web records (A, CNAME, TXT); your existing MX records stay untouched.
As many as your plan allows, and each can point at a different project.