A home-repair business pays an agency to build its website. The site works, customers can request estimates, and the owner assumes everything is under control. Then the agency closes, and nobody at the business knows which account holds the domain name—or who will receive the next renewal notice.

The website's design may be excellent. But a business that cannot manage its domain registration has a problem the homepage won't reveal. The good news is that you can check the essentials without moving the site or changing technical settings.

Understand the Difference Between Your Domain and Your Website

Your domain name is the address customers type, such as the name ending in .com. It is not the website's content, hosting account, or business email service, although those services may depend on it.

The registrar is the company that manages the domain registration. The registered name holder, sometimes called the registrant, is the person or organization recorded as holding that registration. A website designer may help manage the account without being the registered name holder. Alternatively, the designer may have registered the name using their own details.

ICANN explains that domain registration is governed by an agreement with the registrar, including rights and responsibilities for managing, renewing, and transferring the name. Paying a design invoice is not, by itself, confirmation of whose registration it is.

This distinction matters most when you change providers, lose access to an email account, or need to correct an expired registration.

Find the Registrar and Confirm the Registration Details

If you don't know where your domain is registered, start with ICANN Lookup. For generic domain extensions such as .com, ICANN's lookup service uses the Registration Data Access Protocol (RDAP), which replaced traditional WHOIS as the definitive registration-data service in 2025.

The lookup can help identify the registrar and show certain registration details. It may not reveal the registered holder's name or contact email, because some information is not public. An empty or privacy-protected field isn't evidence that your agency owns the domain.

Next, sign in to the registrar's actual account or ask the person managing it to show you the relevant registration and contact settings. Confirm the registered holder, the account administrator, the renewal date, and the email address used for registrar notices. Ask how the business can obtain access if the current manager becomes unavailable.

If a former developer set up the domain and cannot be reached, ICANN's registrant-contact guidance recommends contacting the registrar. Account recovery or changing the registered holder may require identity checks and documentation; don't assume a domain can be reassigned simply because your business uses it.

Make Renewal a Business Responsibility

A domain registration has an expiration date. If it isn't renewed, the website or email addresses associated with it may stop working. ICANN's explanation of expired domains warns that interruption can affect both services.

For generic top-level domains, ICANN's expiration policy requires registrars to send reminders approximately one month and one week before expiration. Those notices don't help if they reach an inbox no one checks.

Record the expiration date in a business calendar, check whether automatic renewal is enabled, and verify the payment method. Keep an alternate, accessible contact address on file where the registrar allows it—preferably one that doesn't rely solely on the domain you are trying to protect.

Automatic renewal is a useful safeguard, not a reason to stop checking. Payments can fail, cards can expire, and renewal or recovery fees depend on the registrar and registration terms. Don't build a continuity plan around an assumed post-expiration grace period.

Secure Access Without Locking Yourself Out

The registrar account is sensitive because it can control settings that affect where your website and domain-based email are directed. Use a strong, unique password and enable multifactor authentication where the provider supports it. Keep recovery methods current and secured.

An outside developer may need to manage website hosting or make occasional domain-related changes. That doesn't mean the business should surrender all administrative access. Ask whether the provider supports separate authorized users or delegated access rather than sharing one password with everyone.

Write down who is responsible for registrar support, renewals, and changes to DNS—the settings that help route website and email traffic. Store recovery information securely, not in a public website document or a shared spreadsheet containing passwords.

A simple rule helps: the business should know how to reach the registrar and regain control even when a contractor is unavailable. Don't change name servers or DNS records during this review just to prove you have access; an incorrect change can disrupt services that are currently working.

Know What Happens When You Change Agencies

You can replace a website designer or hosting company without necessarily transferring the domain to another registrar. These are different operations. Before making a change, ask what will happen to the website files, email service, DNS settings, and domain account separately.

If you do decide to move the domain registration to another registrar, there is a formal transfer process. ICANN's transfer FAQ describes authorization codes, account requirements, and circumstances in which transfers may be restricted. For example, a recent initial registration, registrar transfer, or change of registrant may trigger a transfer restriction under the applicable rules.

Don't change the registered holder just before an urgent registrar move without checking the consequences. Some changes can lead to a 60-day inter-registrar transfer lock. Ask both providers to explain the sequence, especially when business email depends on the existing domain settings.

You don't need to request a transfer code or unlock the domain simply to conduct a routine ownership review. The immediate task is to establish who can authorize a move later if one becomes necessary.

Avoid Renewal Scams and Create a One-Page Domain Record

Not every invoice mentioning your domain comes from its registrar. In a 2026 consumer alert, the Federal Trade Commission warned small businesses about fake invoices for services including domain registration and search engine optimization.

When a renewal notice looks unfamiliar, don't pay from the email link or assume urgency makes it legitimate. Sign in through the registrar website you already know, or contact the provider using a separately verified channel. Make sure the bill matches a service your business actually uses.

Then keep a short, private domain record with these details:

  1. Domain and registrar: The exact domain name, registrar, and official support route.
  2. Registration and access: Who is recorded as the registered holder, who administers the account, and how authorized business staff can recover access.
  3. Renewal: Expiration date, auto-renew status, current payment responsibility, and where notices are delivered.
  4. Dependencies: Who manages DNS, website hosting, and domain-based email, plus who to contact if each service stops working.
  5. Next review: A calendar reminder to recheck the record after a provider change or account-personnel change.

Keep credentials and recovery codes in appropriate secure storage, separate from this checklist. If you discover a registration you cannot control, resolve that issue with the registrar and relevant parties before attempting technical changes.

A business doesn't need to become a domain specialist. It needs to know who holds the registration, who can act on it, and what will happen if the usual website contact disappears. That small amount of preparation can protect more than a web address: it can help preserve the customer communications that depend on it.

Sources and Further Reading