Most small businesses run on three accounts that one person set up: a domain, a hosting plan and a business email. They are usually held in the owner’s name, behind the owner’s email address and often with the owner’s phone number for the security codes. That is fine while the owner is at the desk. It is a problem the week the owner is in hospital, travelling without signal or otherwise cannot act, and a renewal date falls inside that week. This guide is about planning for that, in advance, in about an hour. It is not about getting back in once you are locked out (see locked out of your domain account for that) and it is not about a planned sale or closure (see selling, closing or handing over your business). It is the quiet middle case: nothing has gone wrong yet, and you would like it to stay that way if you are away.
Why an Absence Hits Renewals First
A website does not usually fail the day its owner becomes unavailable. It fails weeks later, when something that needed a human arrives: a renewal, a card that needs replacing, a verification message, a security alert. Three details make this worse than it looks.
- The three accounts renew on different dates. The domain, the hosting plan and any separate email service are billed separately and can expire months apart, so there is no single date to remember.
- One lapse takes the others down with it. If the domain expires, the website and every email address on it stop working together, even though the hosting account is untouched. See what happens when your domain expires for the stages; the exact number of days differs by registry and registrar.
- The notices go to one inbox. Renewal reminders, payment failures and verification messages usually go to whichever email address was used at sign-up. If that is one person’s inbox, and that person is unavailable, nobody else sees the warning.
Step 1: List the Three Accounts and What Hangs Off Them
You cannot hand over what nobody has written down. Start with a plain list of what exists and who holds each piece. For most businesses it is these three, plus a few things that depend on them.
| Account | What it controls | Questions to answer |
|---|---|---|
| Domain registrar | The domain name itself, its registrant details and renewal | Which company? Which login email? Is auto-renew on? Which card pays? |
| Hosting | The website files, the cPanel login and often the mailboxes | Which company? When does the plan renew? Who has a cPanel login? |
| The mailboxes on your domain (often inside the hosting account, sometimes a separate service) | Where are the mailboxes? Who can reset a mailbox password? | |
| Things that depend on them | The DNS records, social pages that use the business email, and the payment card behind everything | Who can change DNS? Which email is each social page tied to? When does the card expire? |
Some businesses discover during this step that the domain sits with one company, the hosting with another and the email with a third, or that a designer set one of them up years ago. Note that honestly. If the domain is not in your business’s name, fix that first with who owns your domain name, because a backup plan built on someone else’s account is not a plan.
Step 2: Name a Backup Person
Choose one trusted second person, and write their name down. The ideal is someone who is likely to be reachable when you are not and who understands the business well enough to act: a co-owner, a senior colleague, a spouse or relative who works with you. Two things matter more than seniority.
- They should be named, not assumed. “My brother would know” is not a plan. Tell the person, show them where the sheet is kept, and ask whether they are willing.
- Prefer their own access over your login. Where a service lets you add a second person to the account, ask about doing that. Where it does not, or you are not sure, keep the details somewhere safe for them instead of handing over your everyday login. This is the same reasoning as in securing your cPanel account: separate logins let you see who did what and remove one person without disturbing everyone else.
Whether a given company can add a second user, and what that user could do, is something to ask the company. This guide does not know, and the answer differs between providers.

Step 3: Decide Where the Details Live
The backup person is only useful if they can find what they need. Think of two separate things: the sheet, which says what exists and where, and the secrets, which are the passwords and security codes. The sheet can be shared widely. The secrets cannot.
- A password manager, with an emergency-access option where one is offered. Several password managers let you name a trusted person who can request access after a waiting period you set, and you can refuse the request in that time. Which managers offer this, on which plans and with what limits, changes over time, so check the provider’s current help pages before relying on it.
- A sealed note held by a trusted person. Old-fashioned and still effective: the details on paper in a sealed envelope, kept by the backup person or somewhere you both know. Update it when anything changes, or it quietly goes stale.
- Never a chat message or an ordinary email. Messages sit in backups and on old phones, and they are the first thing an attacker looks for. The sheet may say “the passwords are in the password manager, emergency access set up for Aisyah”; it should not contain the passwords.
One easy-to-miss detail is the security code. If two-factor codes go only to your phone, a backup person with the password still cannot sign in while you are unreachable. Think about how that second step would work without you, and ask the company what its options are rather than turning two-factor off.
Step 4: Make Notices and Renewals Reach Two People
This is the step that prevents most lapses, and it needs no technical skill.
- An email address two people can read. Set the registrant, billing and account email to a role-based mailbox such as
accounts@that the owner and the backup person can both open, rather than one person’s personal inbox. Verification messages and renewal notices then do not depend on one phone. See the “verify your email address” message for why that email matters. - Not only an address on the domain itself. If every notice goes to a mailbox on the same domain, a lapsed domain also silences the warning. Keep at least one contact address that is not on that domain.
- Auto-renew on, and a payment method that will not fail. Check the card’s expiry date, and that the right account is charged. Most missed renewals trace to an expired card or a stale email. How to make sure you never miss a domain renewal covers this, and 1-year or multi-year registration helps if you want fewer dates to track.
- A reminder that goes to two people. A calendar entry a few weeks before each renewal date, shared with the backup person, is the second safety net behind auto-renew.
- Domain lock stays on. It protects against unauthorised transfers. It also means any transfer needs the account holder, which is another reason the sheet should say who that is.
What a Second Person Can and Cannot Do Without You
Here is the honest limit of any plan like this: companies protect accounts from people who are not the account holder, and they are right to. A backup person who simply phones or writes in your name may be asked for proof of identity, proof of authority or the account holder’s own verification, and may be refused. What each company accepts is for that company to say. This guide does not know what any registrar or host will accept, and it makes no claim about how Gotka verifies another person, adds a user, transfers an account or handles an owner who has died or lost capacity.
What you can do is ask, in writing, while you are well. These are the questions worth putting to your registrar and your host. The answers are unknown to this guide and may differ between companies.
- Can I add a second person to my account with their own login, and what could they do?
- If I name someone in writing in advance, what will you accept as their authority: a letter, copies of ID, a form?
- Which actions could a person acting for me take (renew, update the payment card, change the contact email) and which are reserved for the account holder?
- How do you verify the account holder, and does that depend on a phone number or email I might not be able to reach?
- If my phone is unavailable, what happens to two-factor codes?
- What would you need if an account holder were seriously ill or had died, and where should that person start?
- Who is told when auto-renew fails, and how many reminders go out?
Paste the replies onto your sheet. A short written answer from the company is worth more than a hopeful assumption. Questions of incapacity, wills or the inheritance of a business asset are legal matters, and are best checked with a lawyer or the relevant professional; this guide offers a practical checklist, not legal advice.
A One-Page Continuity Sheet
Copy this layout into a document, fill in each row for your own business and keep it with your backup person. The sheet names accounts and logins, but it holds no passwords. Illustration only: the business, people, companies and dates below are made up.
| What | Company and login email | Where the details are kept | Renews on, paid by | Backup contact |
|---|---|---|---|---|
Domain name contohbakery.com.my | Registrar A, login email [email protected] plus a second address off the domain | Password manager, emergency access set for Aisyah | 14 March each year, auto-renew on, company card expiring 09/2028 | Aisyah (operations manager) |
| Hosting (cPanel) | Host B, login email [email protected] | Password manager, same arrangement | 2 August, auto-renew on, same card | Aisyah |
| Business email (mailboxes) | Inside the same hosting account | Mailbox passwords in the password manager | With hosting | Aisyah; Mei Ling’s brother is the second contact |
| Business Facebook page | Tied to [email protected] | Admin role added for Aisyah | Not applicable | Aisyah |
Under the table, add four short lines:
- Sheet last reviewed: 21 November 2026 (made-up date).
- Sheet kept at: a shared folder and a printed copy in the office safe.
- Written replies from companies: pasted below, with the date each was received.
- Next review due: one year from the last review, or sooner if a login, card, phone number or person changes.
Which Setup Fits Your Business
The shape of the plan depends on who runs the business. Find the row closest to yours.
| Your situation | Main risk | What to set up |
|---|---|---|
| Single owner | Every login, code and reminder sits with one person | One named backup, details in a password manager with emergency access or a sealed note, a second readable email on the account, auto-renew on |
| Two owners | Each assumes the other handles renewals | Agree in writing who the account holder is and who is the backup, and make sure both can read the billing email and see the renewal dates |
| Small team | Access is tied to one person’s phone or to someone who may leave | A role-based mailbox for notices, a separate login per person (see cPanel account security), and a leaver step that updates the sheet |
| Agency-managed | The designer or agency holds the logins and the business holds none | Business named as registrant (who owns your domain), your own login to each account, and a written list from the agency of every account it manages |
A society or committee has a version of the same problem when office-bearers change each year. The idea of a handover that does not depend on one person is covered in a digital name card for societies and committees.
A Fifteen-Minute Yearly Review
A plan nobody revisits drifts out of date. Put a recurring reminder in two calendars and run through this once a year, and whenever a person, card or phone number changes.
- Open the sheet and read it. Is every account still on it, and is anything missing?
- Check each renewal date against the registrar and host, and update the sheet.
- Look at the payment card: expiry date, and that auto-renew is still on.
- Log in to each account once to confirm the login still works.
- Check that the notice email still reaches two people.
- Confirm the backup person is still right, still willing and still knows where the sheet is.
- Re-ask any company question you have not had answered in writing.
- Save the sheet, update the review date and put the next review in both calendars.
Common Mistakes
- Keeping the passwords in a WhatsApp chat “just in case”. It is not safe, and it goes stale the first time a password changes.
- Giving the backup person your own login and calling it done. It hides who did what and may breach the company’s rules. Ask about a second user first.
- Assuming a family member will somehow be able to act. Without the sheet, the registrar’s name and a way to prove who they are, they may not even know where to start.
- Sending every notice to one person’s inbox, or only to a mailbox on the same domain. A lapse then silences its own warning.
- Forgetting that the three renewals fall on different dates. The domain can be safe while hosting lapses, and the reverse.
- Letting the card expire. Auto-renew only works if the payment succeeds.
- Writing the sheet once and never reviewing it. A sheet with a former employee as backup is worse than none.
- Leaving the domain in a designer’s or former employee’s name. No backup plan can fix a registrant who is not you.
If Something Has Already Happened
If you are reading this because an owner is already unreachable, start with the one fact that sets the clock: the earliest renewal date. Check which account it belongs to and whether auto-renew and the payment method are working. If the login is lost or nobody has access, locked out of your domain account sets out the order to follow, and what happens when your domain expires explains the stages if a date has passed. Contact the relevant company in writing and be prepared to prove who you are and on whose behalf you are acting. If a person has died or lost capacity, what the family or business can do with an account is also a legal question, so it is sensible to ask a lawyer or the relevant professional alongside the company.
Where Gotka Technologies Fits
Gotka’s domain registration starts from RM10/yr and includes free transfer in, domain lock and privacy protection, which means your main domain can sit in one account in your business’s name, with a lock that guards against unauthorised transfers. Email accounts are set up inside cloud hosting plans on cPanel, so the website and mailboxes share one hosting account and one renewal date to record on the sheet. For account questions, Gotka support goes through the client-area ticket system, and the phone and WhatsApp line is +60 11-6331 6630, Monday to Friday, 9am to 6pm (MYT). This guide does not describe how Gotka or any other provider handles authorisation of a second person, an account transfer, a customer who is incapacitated or has died, or recovery times and fees. Ask in writing through the ticket system, using the questions above, and keep the reply with your sheet.
Key Terms Used in This Guide
- Continuity plan: a short written plan for keeping the domain, website and email running if the owner cannot act.
- Registrar: the company where the domain is registered and renewed.
- Registrant: the person or business recorded as the holder of the domain.
- Backup person: the second trusted person named to act or to find the details when you cannot.
- Role-based mailbox: a shared address such as
accounts@that several people can read, instead of one person’s inbox. - Emergency access: a password-manager option in which a trusted person can request access after a waiting period you set; availability varies by provider and plan.
- Auto-renew: a setting that renews a service automatically using the payment method on file; it fails if the payment does.
- Domain lock: a setting that blocks unauthorised transfers of the domain to another registrar.
- Two-factor code: a second sign-in step, often sent to a phone, that proves the person signing in is the account holder.
Who should I name as my backup person for my domain, hosting and email?
Someone you trust, who is likely to be reachable when you are not, and who understands the business well enough to act. That might be a co-owner, a senior colleague or a family member who works with you. Name them in writing on your continuity sheet, tell them, and where the service allows it ask the company about adding them to the account rather than giving them your login.
Should I give my backup person my own password?
It is better not to. Sharing your own login makes it hard to tell who did what, and the company’s rules may treat shared logins as a risk. Where a service lets you add a second person to the account, do that. Where it does not, keep the details in a password manager with an emergency-access option or a sealed note held by someone you trust.
Where should I keep my domain and hosting login details?
Keep them in a password manager, ideally one that offers an emergency-access option so a trusted person can request access after a waiting period you choose, or in a sealed note held by that person. Never leave them in a chat thread or an ordinary email. The continuity sheet itself can say where the details are without containing the passwords.
What happens to my website and email if the renewal date passes while I am away?
If the domain is not renewed, the website and every email address on it stop working, usually after a grace period that differs by registry and registrar. Hosting has its own renewal date and can lapse separately. Auto-renew with a working payment method, and renewal notices that reach two people, are what stop an absence turning into an outage.
Can my backup person contact the registrar or host for me?
That depends on the company, and this guide cannot say what any provider accepts. Many providers want the account holder to prove who they are, so a stranger asking on your behalf may be refused. Ask your registrar and host, in writing and in advance, what authorisation they accept for someone acting for you, and keep the answer with your sheet.
How often should I review the continuity plan?
Once a year is a sensible minimum, plus any time someone on the sheet leaves or a login, card or phone number changes. A yearly review takes about fifteen minutes: check each renewal date and payment card, open each account to confirm the login still works, confirm the backup person is still right, and update the sheet.
Domain Name, Website Address and Email Address: What's the Difference?
A domain name, a website address and an email address are three different things that share one part. Here's how they fit together, and what breaks if your domain lapses.
DomainsSelling, Closing or Handing Over Your Business: What Happens to Your Domain, Website and Email
Selling, closing or handing over your business? What to do with your domain, website and email: check the registrant, keep renewing, copy everything, then decide.
DomainsLocked Out of Your Domain Account? What to Do When the Login Email Is Gone or a Former Designer Set It Up
Locked out of your domain account? Check the expiry date, find the registrar, gather proof and contact support safely, then secure the account in the right order.


