Short answer. A site and its mail rest on four accounts: the domain name, at a registrar; the DNS zone, which says where the site and the mail are; the site's hosting; the mail service. If the name expires, everything stops, even if the rest is paid for. Three rules: the name is registered in the company's name; the account's contact address does not depend on the name; renewal is automatic, and its due date is in the manager's calendar. If a former provider holds the access: renew first, then recover the account or the transfer code, then group everything and write everything down.
This guide is for the manager who no longer knows in whose name the domain is, for the one whose site or mail stopped at a due date, and for the founder based in France who runs the site of their Algerian company. The facts quoted come from public sources: ICANN's policy on expired names and transfers, the description of the .dz domain and its registry, and the definitions of the registrar, of cache time and of certificates. The company, dates and providers in the example are constructed. This guide gives neither prices nor legal advice: who a name belongs to in a disagreement is a matter for the registrar, the registry and your legal adviser.
Four accounts behind your site and your mail
The figure follows a visit and an email: both go through the name, then through the DNS zone, before reaching the site or the mailboxes.
The name. A registrar is a company that manages the reservation of domain names; it allows a person or an entity, the registrant, to register a name, on behalf of the registries that run each extension. The name is reserved for a period, and renewed. The DNS zone. It says where to send a visit and where to deliver an email; it is often at the registrar or at the host. The site is at a web host. The mail is at a mail service, described in the guide to professional mail.
The dependency. In the example, hosting and mail are in the company's name, and paid for. But the name and the zone are under the former provider's account: on 14 March the name expires, and nothing arrives anywhere. How to find out. The public directory of names is queried through a WHOIS service, a query protocol for the databases that record the registered holders of internet resources; it shows the registrar, the due date and the name servers. The holder is often hidden, but the registrar and the date are enough to know whom to contact. .dz or .com. The .dz is Algeria's national domain, administered by the DZ NIC centre, attached to CERIST; according to its public description, it is reserved for entities established in Algeria. A .com is registered with any registrar. Many companies hold both; the question in this guide, who holds the account, applies to one as to the other.
«The site and the mail do not hang on the host: they hang on the name, and on whoever holds its account.»
Around the due date: five periods, and what can still be done
The figure divides the life of a name around its due date, for a generic name such as a .com.
Before. ICANN's policy on expired names requires the registrar to send at least two reminders before the due date, one about a month before, the other about a week before, then at least one more within the five days that follow. They go to the registered holder's address: if that is the former provider's, you will never see them. After. The name remains renewable for a period whose length depends on the registrar; during that period, the registrar interrupts the resolution of the name, and the site and the mail both stop. That is generally when people notice.
Redemption. After the registration is deleted, the policy provides a redemption period of thirty days during which restoration of the name can still be requested. Then the name is deleted for good and becomes free: anyone can register it, including to publish something else on it. For a .dz, the rules are those of the national registry and are checked with it. The lesson. While the name is renewable, the problem is settled in ten minutes by whoever has the account. The whole issue is therefore to have the account, and to receive the reminders.
«A name is not lost all at once: it is lost because the reminders reach someone who is no longer there.»
Taking back control, in six steps
The second step is accented: you secure the due date before discussing who holds what.
Find out: the registrar, the due date, the name servers, the site's host, the mail service. Secure the due date: if it is close, have the name renewed, by the former provider if need be; a renewed name leaves a year to settle the rest, an expired name leaves only a few weeks. Recover: either access to the account, or the transfer code. That code is required to transfer a name from one registrar to another, and the registrar must provide it within five calendar days of the request.
Put it in the company's name: the registrant becomes the company, with a contact address outside the name, for example a mailbox of the manager's at another provider. Mind the order: under the transfer policy published by ICANN, a recent registration, transfer or change of registrant can block a new transfer for several weeks, sixty days in the rule read at the time of writing, which is under revision; so you first decide where the name should end up. The transfer itself takes about five days. Copy: the DNS zone, the site's files and its database, somewhere safe. Record: the accounts, the due dates and two people in charge. If the provider no longer answers, the registrar gives the procedure; when the registered holder is the provider itself, the next steps are a matter for the registrar, the registry and your legal adviser.
Six things to hold yourself
The figure gives, for six items, what you need in hand and the sign that you do not have it.
The certificate. The padlock in the browser rests on a certificate that also expires: those from Let's Encrypt, issued at no charge, are valid for ninety days by default, and the organisation plans to shorten that further. Their renewal therefore has to be automatic, and monitored. The backup. The copy the host makes on its own server does not protect you from the host; you need a copy of the files and the database elsewhere, restored at least once, following the method in the guide to backups.
Changing host without an outage. A DNS record carries a cache time: a server that has read it keeps it for the time stated. Before a change, you lower that time, copy the site to the new host, switch over, then raise it again. For the choice of place, a server in Algeria or in Europe, see the guide to hosting an application; for a brochure site, that question weighs less than knowing who holds the accounts.
A name and a site under control, in five layers
The accented layer is the first: in whose name the domain is registered.
Registered holder: the company, not a person and not a provider. Accounts and access: one account per provider, two-step verification, two authorised people, codes in a vault; the rules are those in the guide to hacking, because a hijacked registrar account means the site and the mail going elsewhere. Due dates: four of them, the name, the hosting, the mail service, the certificate.
DNS zone: documented and exported. Site and mail: hosted, backed up, restorable. Keeping all this up to date is routine work, which fits in the contract described in the guide to managed IT; what cannot be delegated is the name of the registrant and the possession of the access.
Taking back control in 2027, in weeks
Three weeks in the example, the first of which changes nothing visible.
- What the manager sees: one page with the four accounts, in whose name, at which provider, the due date of each and the two people who have access.
- What the company no longer does: discover a due date the day the site goes down, depend on a third party's address for a reminder, hunt for a password with a former employee, change host in an emergency.
- What is measured: days left before each due date, date of the last backup restored, accounts without two-step verification.
- What Symloop does: the findings, recovering the accounts with you, grouping them, hosting and backing up the site, following the due dates, and redesigning the site when that is useful.
Week 1, findings and securing: you find the registrant, the registrar, the due date and the name servers, have the name renewed if the date is close, and copy the zone, the site and its database. Week 2, recovering the accounts: access or transfer code, name put in the company's name, outside contact address, two-step verification.
Week 3, grouping and follow-up: the accounts are grouped and recorded, renewal is automatic, alerts are in place, the backup runs and a restore has been tried.
- Who does my domain name belong to?
- The name is registered to a holder, at a registrar; it is that holder, and whoever holds the account, who can renew it, transfer it or change it. If the name was reserved by an agency or by an employee, it is often their name and their address that appear. You check with the registrar shown by the name's public directory.
- My domain name has expired, what should I do?
- Act at once. While the name is renewable, whoever has the account renews it in a few minutes and everything restarts. If you do not have the account, contact the person who does, then the registrar. For a generic name there is still, after deletion, a redemption period of thirty days; after that the name becomes free.
- The former provider kept the access, how do I get my site back?
- In order: have the name renewed if the due date is close; ask for access to the account or for the transfer code; put the name in the company's name; copy the zone, the site and its database. If the provider does not answer, the registrar gives the procedure; in a disagreement about the registrant, see your legal adviser.
- Should we take a .dz or a .com name?
- The .dz is the national domain, administered by the Algerian registry and, according to its public description, reserved for entities established in Algeria; the .com is registered anywhere. Many companies take both. In both cases, what counts is the same: the name in the company's name, the account in your hands, the due date watched.
- What is the difference between a domain name and hosting?
- The name is the address; hosting is the place where the pages are. Between the two, the DNS zone says where the name points. They are separate accounts, often at different providers, with different due dates.
- Why did my mail stop at the same time as the site?
- Because mail also goes through the name. When the name expires, its zone no longer answers: the servers that want to write to you no longer find where to deliver. The mail service itself works, but nothing reaches it any more.
- How do I find out where my domain name is registered?
- By querying the name's public directory, through a WHOIS service: it gives the registrar, the due date and the name servers. The holder is often hidden, but you know whom to contact and how much time is left.
- How do you transfer a domain name to another registrar?
- With the transfer code, which the current registrar must provide within five days of the request. The transfer takes about five days. A recent registration, transfer or change of registrant can block it for several weeks: so you first decide where the name should end up.
- Where should my company's website be hosted?
- For a brochure site, at a serious host, with a certificate renewed automatically and a backup that you hold. The country matters less than for a business application. What counts: the account in your name, a copy of the site in your hands, and the ability to leave within a day.
- How do we stop depending on a provider for our site?
- By holding the four accounts yourself, the name, the zone, the hosting, the mail service, with two authorised people, and by keeping a copy of the site and its database. The provider then works with access that you give, and that you can withdraw.