A real DNS manager, built in
The subdomain is the hook. The DNS control is the product.
Supported record types
| Type | What it does | Example value |
|---|---|---|
| A | Points a hostname at an IPv4 address. | 203.0.113.10 |
| AAAA | Points a hostname at an IPv6 address. | 2001:db8::1 |
| CNAME | Aliases a hostname to another hostname. | cname.vercel-dns.com |
| TXT | Arbitrary text — mostly verification and SPF. | google-site-verification=… |
| MX | Routes mail for the hostname, with a priority. | mail.example.com |
SRV and CAA are on the list for later.
Bring your own DNS
You are not locked into our manager. Add NS records on your subdomain and it is handed to whichever nameservers you name — your own Cloudflare account, another provider, or a server you run. Everything below that name becomes yours to manage there.
Manage it here
The default. Add records in the dashboard and they are live on our nameservers immediately. Nothing else to set up.
Delegate it away
Point the name at your own nameservers and run it yourself, with whatever features that provider gives you. How to do it →
Limits
- 5 subdomains per account.
- 10 DNS records per subdomain.
- TTL from 5 minutes to 1 day, or Auto when a record is proxied.
- 7-day terms, renewed every time you sign in. How that works →
Starting limits, set low while the project is small. They will go up.
Your records are yours alone
Every DNS operation is authorised server-side against the subdomain you own. The zone apex, wildcards and other people's hostnames are unreachable — attempts are rejected and logged. You never receive nameserver credentials, because the backend makes every call for you.