The panel your domain answers to

Completely — every record type, unlimited records, anycast nameservers, per-record TTL, no monthly quota and no "premium DNS" tier hiding the good parts. We treat DNS as what it is: the half of the product that makes the domain do anything. Charging extra for it would be selling you a car and metering the steering.

Panel → your domain → DNS zone → add record: type A, host @ (or a subdomain), value your server's IP, save. The record publishes in seconds and the wider internet follows within your TTL. Add an AAAA beside it if the server speaks IPv6 — same form, longer address.

Nameservers decide WHO answers DNS questions for your domain; records are the answers themselves. Editing records in our zone changes the answers we give. Pointing nameservers elsewhere hands the entire answering job to that provider — and our zone goes dormant until you point back. Day to day you edit records; nameserver changes are for re-homing DNS wholesale.

Freely — add the domain at Cloudflare, copy the two nameservers they assign, paste them into the panel here. Registration, renewal, privacy and the Shield stay with us; DNS answering moves to them. Reversing it later is the same edit backwards, and nothing about your registration is disturbed either way.

Nearly every generic extension — .com, .net, .org, .io, .ai, .dev, the whole modern catalogue — has privacy on by default at no cost. The exceptions are country registries that legally require public registrant data: .de, .sa, .us among them. The pricing table carries a privacy column so you can check any extension in two seconds.

One switch inside Nameserver Shield. On our nameservers the whole chain is automatic: we sign the zone and publish the DS record at the registry — nothing to copy. Running external DNS? We generate the keys and show exactly what your DNS provider needs. Switching it off again is the same toggle, no support ticket involved.

No — a notice lands in your inbox before every auto-renew charge, stating the domain, the date and the exact amount. Plenty of time to switch the toggle off if plans changed. No card on file simply means auto-renew waits, and the standard reminder sequence runs instead. The feature exists to prevent surprises, so it doesn't get to cause them.

You set a rule — this domain or subdomain sends visitors to that URL — and choose how: 301 if the move is permanent and search ranking should follow, 302 if temporary, masked if the address bar should keep showing your domain. Rules live in the Routing tab, save in seconds and stack per subdomain.

Yes — TXT is a first-class record type in the zone editor, and it is how you verify with Search Console, prove ownership to Microsoft 365, and publish SPF, DKIM and DMARC for honest mail delivery. Paste the string the service gives you, save, verify; the panel keeps even long DKIM keys intact.

Two minimum — registries insist on redundancy — and up to thirteen, the protocol ceiling. Two well-anycast nameservers serve almost everyone; large setups add more for geographic spread or to mix providers as a failure hedge. Ours are anycast already, so each name you list is many physical servers wearing it.

Unlimited, straight from DNS: an A record with host blog creates blog.yourdomain.com, a CNAME can alias shop to your storefront platform, and a wildcard record catches anything-at-all.yourdomain.com in one rule. Subdomains are just records — no fee, no count, no approval step.

Yes, and without drama: switch off the lock in Shield, copy your EPP code from the panel, hand it to the new registrar. No exit fee, no retention call, no code that takes a mysterious week to generate. ICANN guarantees the right; we just decline to make exercising it unpleasant. Registrars confident in their product don't bolt the doors.

Our name for the protection stack every domain deserves but usually has to assemble piecemeal: registry transfer lock, DNSSEC zone signing, and explicit confirmation on high-impact changes like nameserver or registrant edits — managed as one switch with visible status. It ships armed on every domain, because security that needs configuring is security most people don't have.

Create an alias — hello@yourdomain — and pick where it delivers: your Gmail, Outlook, anything. Mail to the alias lands in that inbox; with send-as configured there, your replies leave from the professional address too. Add specific aliases or one catch-all, all free. When you outgrow forwarding, hosted mailboxes plug into the same domain without touching the aliases.

They solve DNS's chicken-and-egg: if your nameserver is ns1.mybrand.com, resolvers must learn its IP from somewhere before they can ask it anything. A child nameserver registers that name at the registry with its IP attached — the glue. You need this only when running DNS on your own infrastructure under your own domain; the panel handles registering both in one form.

The panel is the supported surface today — built fast enough that bulk work doesn't hurt, with grouped operations for multi-domain changes. A public API for registrations, DNS and transfers is on the platform roadmap with our developer tooling; if API access would change how much you bring here, tell support — volume moves roadmaps.