Engineering Glossary · Domains
Domain registrar — Your Registrar Is an API, a Delegation and a Set of Limits
You need to know which of your DNS problems the registrar owns and which ones it cannot touch.
The short answer
A registrar is the accredited company that holds your registration and, more importantly for day-to-day work, publishes the delegation that tells the world which nameservers are authoritative for your domain. Nothing you edit anywhere else counts until that delegation points at it.
Treat it as infrastructure rather than a supplier. The registrar decides the minimum TTL you can set on delegation records, whether DS records for DNSSEC are accepted, how long the post-transfer lock runs, and whether there is an API you can put in a deployment script. Those four answers shape every DNS change you will ever schedule.
By the HostingFast team · Reviewed 24 August 2026
100+
Terms defined properly
2 min
Read time, end to end
Plain
English, no hand-waving
24/7
Engineers on shift
Registries sell the namespace wholesale; registrars retail it, handling registration, renewal, delegation, transfers and the public record under an accreditation agreement. That much is the same everywhere.
The differences show up after you sign, and they are operational as often as commercial: whether the DNS interface has an API or only a web form, whether records propagate to the registrar's own nameservers in seconds or minutes, how many clicks stand between you and an auth code, and whether anybody answers when a delegation goes wrong at two in the morning.
The delegation is the only lever that counts
There is exactly one authoritative statement about who answers for your domain, and it lives at the registrar as a set of NS records in the parent zone. Query the parent for your NS set before you debug anything else — the answer is frequently not the provider whose control panel you have been editing.
This single fact explains most so-called DNS bugs. Records edited in a zone that nothing delegates to are perfectly valid records that no resolver in the world will ever ask for.
Limits that turn up in a migration runbook
Minimum TTLs on delegation records vary, and a registrar or registry floor of a day means the nameserver switch you planned for a 300-second window will actually take considerably longer to settle everywhere.
Then there is the 60-day lock after registration or a previous transfer, glue record support for private nameservers, and whether DS records can be published at all. Check each one before you write the runbook, not while you are executing it.
Automating the boring parts
If your registrar exposes an API, DNS becomes something a script can do: issue ACME DNS-01 challenges for wildcard certificates, drop a TTL twenty-four hours before a cutover and raise it afterwards, or assert in CI that a required record still exists. If it does not, all of that becomes a human with a checklist at an unsociable hour.
Account security belongs in the same conversation. The registrar login is a single credential that can redirect every service on your domain, so it wants two-factor authentication, a monitored recovery address and as few people holding it as the job allows.
Registering or pointing a name here
Register with us and the delegation, the zone, the certificate and the mail routing land together. Order annually and the first year of the domain costs nothing; renewals bill at the rate you originally paid rather than at a rate that discovers you later.
Keeping the registration elsewhere is equally supported. Delegate the nameservers to us for the full zone, or leave the zone where it is and point a single A record at your account — the panel, the certificates and the caching behave the same either way.
The reference we wanted when we were on the other side of the ticket
Every entry answers a question that turned up often enough to deserve a proper answer, written with the command, the panel screen and the failure mode included.
Support here is a human being at any hour, and the scope covers the awkward operational questions other hosts bounce straight back to you.
- 100+ entries, each tied to a real check
- Delegation, TTL and lock rules spelled out
- Cross-linked into DNS, A Record and TTL
- Written by the people who run the platform
Why HostingFast
Standard on every plan
Delegation before everything
The one query that settles most DNS arguments, and the reason it settles them.
Registrar, as infrastructure
What the registrar controls in your stack, expressed as limits you can plan around.
Automation surface named
Where an API turns a two-hour manual cutover into a scheduled job.
Lock and TTL floors
The rules that decide whether your migration window is realistic before you book it.
Credential risk stated
One login can redirect an entire business, and this page treats it accordingly.
Neighbours wired in
Domain Name, WHOIS and EPP Code continue directly from here.
Quick Start
From order to online
- 1
Query the parent for your NS set
Ask for the NS records of your domain and note what comes back. Every debugging session should start with the delegation, because everything downstream depends on it.
- 2
Write down the limits
Record the TTL floor, the lock period, DNSSEC support and whether an API exists. Those four values are the constraints your next migration has to fit inside.
- 3
Lock the account down
Turn on two-factor authentication, point the recovery address at a mailbox somebody actually watches, and remove logins that no longer need to exist.
- 4
Script one repetitive task
Start with something small — asserting a required record still exists, or lowering a TTL on a schedule — and you will never do it by hand again.
Built In
Loaded onto every plan
- Delegate nameservers to us or keep your zone elsewhere, both supported
- Full zone editing in cPanel for every domain on the account
- Free SSL issued and renewed for every hostname
- First year of the domain free on an annual order
- Renewal billed at the price you first signed up at
- No setup fee on any plan
- NVMe SSD storage across every tier
- Engineers reachable at any hour, every day
Frequently Asked
What people ask us most often
Which nameservers is my domain actually delegated to right now?
Ask the parent zone rather than trusting a control panel: query the NS records for your domain and read the answer. That is the set every resolver on the internet will use, and if it does not match the provider whose zone you have been editing, you have found your bug in under ten seconds.
Does my registrar's own DNS speed matter?
It matters if you use their nameservers. Query each authoritative server directly and compare the reported query time; a set that answers from one region will be noticeably slower for distant visitors than an anycast set. It stops mattering the moment you delegate elsewhere.
Should the domain live with the same company as the hosting?
As an engineering decision it comes down to failure domains: one supplier means one login and one queue, two suppliers means an outage at one does not lock you out of the other. Either is defensible. What is not defensible is choosing a registrar without first checking how easily you can leave it.
What is the refund position if I change my mind?
Thirty days on shared, business, WordPress and WooCommerce hosting; seven on reseller. VPS and dedicated servers are provisioned to order the moment payment lands, so they sit outside the guarantee — as do domain registrations, where the registry charges the instant the name is secured. Inside the window, one request returns the hosting fee.
Keep reading
TLD (Top-Level Domain)
The ending above your name, and the registry rules that come with it.
WHOIS
The public record, and the three fields that end most delegation arguments.
Point a Domain at Your Server
Pointing a name at a server, in order, with the step people skip.
Business Hosting
Shared hosting with the full developer toolbelt: SSH, Node.js, Python and PostgreSQL.
Node.js Hosting
Run Node.js applications beside your sites, with SSH and Git included.
Changing hosts? Run through our checklist first.
A straightforward sequence for a switch your visitors never feel: which files move first, how to shift email across without losing a single message, the right moment to repoint DNS, and the two mistakes behind almost all the downtime we get asked to rescue.
Put the delegation where you can see it.
Scaling from one site to a rack of servers is an account change here, not a migration you have to survive.
View Business Hosting plans