47. Domain and Email Setup Questions to Ask Before Launch

Launch day is a bad moment to discover that the domain is registered to a contractor's cousin, or that company email only works on one person's phone. Domain and email are the address of the business in a very literal sense. Customers, banks, marketplaces, and staff will use them for years. Before a website goes live, a founder should ask a short list of questions and keep the answers in a folder that is not trapped inside the vendor's account. The questions are not technical for their own sake. They are about ownership, continuity, and what happens on a Sunday when something breaks.

You can ask them in plain language. You do not need to pretend to be a network engineer. A competent person who set up the site will be able to answer without a speech. If the answers are vague, delay the launch until they are specific. A pretty homepage on a domain you do not control is a homepage you can lose.

<>

Ask who owns the name and where it renews

The domain, the .com or .com.my name, should be registered to the business or to the founder, not only to the designer. Ask which company holds the registration, which email receives the renewal notices, and when it expires. A name that expires during a festival weekend can take the email and the site down together. Put the expiry in your own calendar with a reminder a month earlier. Ask how to transfer the name away if you change vendors. A fair vendor will explain the steps. A vendor who says the name cannot leave is describing a hostage, not a service.

Check that the public details are ones you meant to publish. Some registrations show a name, address, and phone. Make sure they are current and that they are not a previous freelancer's details. If you use a local .my name, ask what documents were used and where those approvals sit. You want to be able to renew without finding the person who once had the SSM paperwork in a drawer.

Ask where email lives and who can reset it

Company email should survive a staff resignation. Ask where the mailboxes are hosted, who the administrator is, and how you reset a password if that person is unavailable. A founder should have administrator access, stored somewhere safer than a chat message. Ask for at least one mailbox that is not a personal name, such as an address for quotes or accounts, so customers are not writing only to someone who may leave. Personal forwarding can exist. It should not be the only route.

• Who is the registrant, and which email gets renewal warnings?
• When does the domain expire, and how do you transfer it?
• Where is email hosted, and who is the administrator?
• Which addresses exist, and who reads them on leave?
• Where are the passwords stored, and who else can open that store?

Ask them to send a test to and from the new addresses before launch, including to a Gmail or similar account a customer might use. Mail that only works between people inside the same system is not finished. Ask what happens to a mailbox when you stop paying the vendor. If the answer is that the mail vanishes, plan an export. Your invoices and supplier threads are business records, not a perk of the web project.

<>

Ask about the records that make mail trustworthy

You do not need to memorise abbreviations to ask a useful question. Ask what they have done so that messages from your domain are less likely to be treated as junk, and so that strangers cannot easily pretend to be you. Ask them to say, in a sentence, which records they set and where those records live. They should be in the same account as the domain, or you should be told clearly if a different panel controls them. If email is at one provider and the website is at another, that split is normal. What is not normal is nobody knowing which panel to open when mail fails.

If you cannot renew the name and reset the mailbox without the original vendor, you do not own the launch. You are renting it.

Ask who to call when mail fails on a weekend, and what that help costs. A retainer that excludes email will surprise you at the worst time. Write the names of the panels, the login owner, and the support route on one page. Store that page with your company documents. Update it when a password changes. This single page is worth more than a diagram you cannot read.

<>

Confirm access before you announce the site

On the day before launch, log in yourself. Open the domain panel and the mail admin, even if you only look and then leave. Send one more test. Check that the website address and the email domain match the name printed on your card. A card that says one name and a site that lives on another is a repair you can still make quietly. After you have told the world, it becomes a reprint.

Leave with the passwords changed from any temporary ones the vendor used during setup, if they were shared widely. The person who built the site can keep the access they need for maintenance, and they should not be the only adult in the room. Domain and email are part of the company's front door. Ask the questions before launch, write down the answers, and you will spend the first week selling instead of searching for the keys.