Domain guide 14
Your domain checklist starts with the registrant record.
The short answer
Confirm which person or legal entity is the Registered Name Holder, which registrar maintains the registration and which account model applies. For a .com, the registrar may be ICANN-accredited or a reseller working through one. A business-controlled registrar account should have tested recovery and strong authentication. A provider-managed account should disclose control, registrant identity, renewal, DNS requests, and release. Review that evidence before changing web providers or email systems.
How this guide was made. Parcha Lab synthesized firsthand service scope and the official sources listed below. AI assisted with drafting and structural checks.Human review byMikeon.
Know the four roles people casually call the owner.
ICANN defines the registrant as the individual or entity that registers the domain and enters an agreement with the registrar. The registrar maintains the registration. A reseller or web provider may manage the account, and a technical contact may manage DNS. Those roles can involve different organizations.
Ask for the registrar name and use ICANN's lookup resources when the provider is unclear. A hosting company, designer, DNS provider, and registrar may be separate even when one dashboard makes them look like one service.
- Registrant: the registered name holder under the registrar agreement
- Registrar: the company that maintains the registration
- DNS provider: the service that directs web and email traffic
- Manager or reseller: a party authorized to act for the registrant
Test the real access model before an emergency.
If the business owns the registrar account, sign in through the normal address, inspect the domain, and test recovery without changing settings. The recovery email and phone should be current and controlled by the business, not by one former employee or outside vendor.
If a provider manages the registration inside its own account, do not pretend the business has a login it does not have. Require written disclosure of the account controller, customer registrant identity, renewal and DNS request path, status visibility, security verification, and basic handoff or transfer process.
- The account owner/controller and recovery path are named
- Multifactor authentication is enabled on the controlling account
- Registrant and administrative contact data are current
- Authorized users and roles are documented
- Domain lock, renewal and handoff or transfer terms are understood
Treat renewal as a business continuity control.
Record the expiration date, renewal price, payment method, auto-renew setting, and who monitors notices. Renewal emails can be missed or imitated, so sign in through the known registrar address instead of following an unexpected payment link.
Keep billing and contact details current and set a separate calendar reminder before the registrar's notice window. If a provider pays on the business's behalf, the agreement should say when the business is charged and what happens if payment fails.
Map web and email DNS before touching it.
DNS may control the website, business email, verification records, subdomains, and security policies. Export or record the current entries before a migration. A website launch that replaces nameservers without rebuilding email records can interrupt mail even when the new website works.
Require a change plan with the old value, new value, reason, approver, time, verification, and rollback. Make the smallest change that solves the task, then confirm both web and email behavior.
Define handoff before changing providers.
List the domain, registrar account, DNS zone, certificates, email records, verification records, renewal records, and authorized contacts. Decide whether management access changes or the registration itself transfers. These are different operations.
After handoff, verify the public site, email delivery, security records, redirects, and recovery methods. Remove old access only after the new path works and the required records have been preserved.
Questions
What buyers usually ask next.
Who is the Registered Name Holder of a domain name?
ICANN describes the registrant as the individual or entity that registers the name and enters the registration agreement with the registrar. Check the registrar account and available registration data for the specific domain.
Is my domain registrar the same as my web host?
Sometimes, but not necessarily. Registration, DNS, website hosting, email, and site management can be provided by different companies. Record each role separately.
What if my web designer controls the only domain login?
A disclosed managed-account model is different from hidden control. Ask for the registrar, registered holder, account structure, renewal and DNS request path, recovery safeguards, status evidence, and documented handoff or transfer plan. Avoid changing DNS until current web and email records are preserved. With Parcha-managed new registrations, the approved customer is submitted to Cloudflare as the registrant and becomes the Registered Name Holder only after Cloudflare confirms registration, the registration stays in Parcha Lab’s Cloudflare account, and basic account-move or registrar-transfer help is free when provider rules permit it.
How do I avoid losing a domain at renewal?
Keep registrant and billing details current, enable auto-renew when appropriate, monitor notices through a business-controlled address, and set an independent calendar reminder. Sign in through the known registrar site to verify any payment warning.
References
Official sources used for factual claims.
Advice and checklists are Parcha Lab's original synthesis. Changeable technical, platform, standards, and legal-context facts are grounded in the primary sources below.
- ICANN Information for Domain Name Registrants
- Parcha Lab Public Terms of Service