How to Create a Company Domain Email in Nepal (info@)

The records you will end up with

TXT (verification): the value Google gives you, at the domain itself. Active in about 10 minutes.
MX: one record only. Host @, priority 1, value smtp.google.com. Propagation up to 72 hours.
TXT (SPF): v=spf1 include:_spf.google.com ~all
TXT (DKIM): a 2048-bit key with selector google, generated in the Admin console after Gmail has been running 24 to 72 hours.
TXT (DMARC): at the host _dmarc, starting with a p=none policy.

Before you touch anything

Three things decide how smooth this goes. First, do you control the domain, or does the person who built your website control it? You need login access to wherever DNS is managed. Second, is mail already flowing to that domain, for example to a cPanel mailbox? If so, this is a migration and the order of operations changes. Third, who will be the administrator? Not a personal address, and not someone who is about to leave.

Step by step

Get a domain. A .com is the usual choice for a company selling beyond Nepal. Domains ending .com.np are registered free through Mercantile's register.com.np, which is why so many Nepali institutions use them. Either works for email. If you need help with registration, see domain registration in Nepal.
Choose the mail provider. Google Workspace is the subject of this guide. The alternatives worth comparing are WebsNP's own business email hosting if the budget is per-mailbox tight, and Zoho. Decide before you create records, because the MX values differ per provider and only one provider can receive your mail at a time.
Verify the domain. Google gives you a TXT record to add at your domain. The record is normally active in about 10 minutes, and Google's confirmation is usually quick, up to an hour. Nothing about your existing email changes at this step, which is why it is safe to do first.
Create the people first, the roles second. Add a user for each staff member using the naming convention you agreed. Then decide how info exists: as a user, a group or an alias. This is the choice that decides your monthly bill, so it gets its own section below.
Point MX at Google. One record: host @, priority 1, value smtp.google.com. Delete the old MX records at the same time, because leaving them in place is the single most common reason mail keeps arriving in the old mailbox. Propagation can take up to 72 hours, so expect an overlap period during which messages may land in either system. Older aspmx.l.google.com style records still work if you inherit them, but a new setup uses the single record.
Add SPF straight away. A TXT record with the value v=spf1 include:_spf.google.com ~all tells receiving servers that Google is allowed to send for your domain. If another system also sends on your behalf, a billing tool or a website contact form, its include goes in the same single SPF record, never a second one.
Add DKIM once Gmail has settled. Google asks you to wait 24 to 72 hours after Gmail starts working before generating the key, then produces a 2048-bit key with the selector google that you publish as a TXT record and switch on in the Admin console. This is the step most people forget, because by then the mail is already working.
Add DMARC last, gently. A TXT record at the host _dmarc, starting with a p=none policy so you can see reports without anything being rejected. Once you are confident that everything sending as your domain passes SPF and DKIM, move to quarantine and then reject. Bulk senders above 5,000 messages a day are required to have all three of SPF, DKIM and DMARC.
Connect phones and desktop clients. The Gmail app on Android and iOS signs in with the new address. Staff who insist on Outlook or Thunderbird connect over IMAP. Do this after MX has propagated, not before.
Test properly. Send from the new address to an outside account and reply back. Then open the received message's headers and check that SPF and DKIM both pass. Test the info address from a phone on mobile data, not from a colleague's desk, so you are testing the public path.

The exact values, in one table

Type	Host	Value	Notes
TXT	@ (the domain itself)	The verification string from Google	Active in about 10 minutes
MX	@ (the domain itself)	smtp.google.com, priority 1	One record only. Up to 72 hours to propagate
TXT	@ (the domain itself)	v=spf1 include:_spf.google.com ~all	Only one SPF record per domain
TXT	google._domainkey	The 2048-bit key from the Admin console	Generate after Gmail has run 24 to 72 hours
TXT	_dmarc	A policy record starting at p=none	Tighten to quarantine, then reject

Some DNS panels want the host written as @, some want the bare domain name, and some append the domain automatically so typing the full name creates yourcompany.com.yourcompany.com. Check what the panel shows after saving, not what you typed.

User, group or alias: how info@yourcompany.com should exist

All three produce a working address. They differ in cost and in what happens to the record of what was sent.

Form	Best for	Uses a licence?
A user	An address that needs its own login, storage and Drive, for example a reception PC	Yes
A group	An address several people answer, keeping a shared record of what arrived	No
An alias	A second address landing in one person's existing inbox	No

For most Nepali offices info and sales are groups, accounts is an alias on the finance person's mailbox, and only real humans get licences. A boutique in Pokhara with an owner and two staff needs three licences, not six addresses' worth.

Where your DNS actually lives

People lose an afternoon here, so it is worth being precise. DNS is managed wherever the domain's nameservers point, which is not always where you bought the domain.

The registrar's panel. The default if nobody changed the nameservers.
Your hosting cPanel. Common when a Nepali web developer set up the site and pointed the domain at the hosting account. Look under Zone Editor.
Cloudflare. If someone put the site behind Cloudflare, DNS records live there and changes elsewhere do nothing.

For a .com.np domain registered free through register.com.np, the same rule applies: the records are edited wherever the nameservers point, which is often a hosting panel rather than the registration portal. Find the nameservers first, then log in to the right place once.

Mistakes that cost a week

Leaving the old MX records in place. Mail keeps going to the old host and staff think Google is broken. Remove them when you add the Google record.
Two SPF records. A domain must have one. Merge the includes into a single record instead of publishing a second.
Never adding DKIM. Mail works without it, right up until a bank or a foreign client's filter decides your invoice is suspicious.
Making the owner a personal address. The Workspace super administrator should be an account the company controls, with recovery details that are not one employee's phone.
Switching MX before importing old mail. Import history first, cut over second, then run a delta import for anything that arrived in between. The migration guide covers the order.
No 2-Step Verification. Turn it on for administrators before you announce the new addresses, not after.

What it costs and who does the work

Business Starter is enough for an office whose main need is email on its own domain, at $2.78 per user per month through WebsNP, $25.83 per user per year, paid in NPR. Google's own list price for the same edition is $7 per user per month on the annual fixed-term plan, billed in US dollars by card, since NPR is not a supported Google billing currency.

WebsNP includes this setup with every Workspace order: domain verification, MX, SPF, DKIM and DMARC records, user creation, and migration of existing mailboxes from cPanel email, Zoho or another Workspace tenant. If you would rather do it yourself, everything above is what you need, and the longer administrative sequence including org units, groups and 2-Step Verification enforcement is on the Workspace setup guide. If you are still deciding whether the whole exercise is worth it, read business email with Google Workspace and what Business Starter includes first.

Frequently asked questions

How long does it take before the new email works?

Domain verification is usually the fastest part: the TXT record is active in about 10 minutes and Google's confirmation is normally quick, up to an hour. The MX change is the slow one, with propagation of up to 72 hours, although in practice most receivers pick it up sooner.

Do I need to pay for info@yourcompany.com?

Not usually. Create it as a group if several people answer it, or as an alias on an existing mailbox if one person does. Only create it as a user, which uses a licence, when it genuinely needs its own login and storage.

Can I use my .com.np domain for Google Workspace?

Yes. A .com.np domain works like any other for email. The only difference is knowing where its DNS is managed, which is wherever its nameservers point: the registrar panel, your hosting cPanel or Cloudflare.

What happens to email arriving during the switch?

For a period, some senders still see the old MX record and some see the new one, so messages can arrive in either system. Keep the old mailboxes active through the changeover and run a second import afterwards to collect what landed there. Nobody, including Google, can promise a switch with no overlap at all.

Why is my mail going to spam even though it works?

Almost always missing or wrong authentication records. Check that SPF exists once and only once, that DKIM was generated and switched on after Gmail had been running 24 to 72 hours, and that DMARC is published at _dmarc. Then read the headers of a message you sent to an outside account and confirm SPF and DKIM both pass.

Can I have two providers on one domain?

Mail delivery follows the MX records, so one provider receives at a time. Arrangements that deliver to two systems exist and are set up deliberately, not by leaving old records in place by accident.

Sources and further reading

Product facts on this page were checked against Google's own documentation on the date shown above. Google changes plan contents, limits and country availability over time, so treat the official pages as the final word.