A quote that arrives from [email protected] reads differently from one sent by a Gmail address with numbers at the end. But registering the domain doesn't get you email: when you register a .com.py at NIC.PY, you buy the name and nothing else. The mailboxes come from another service, and they only work once a few records are added to the domain's DNS.
What you need before you start
- An active domain. If you don't have one yet, our .com.py guide walks through the NIC.PY process from start to finish.
- Access to the domain's DNS. With a .com.py, NIC.PY delegates the domain to the DNS servers you entered on the form. Email records go in that provider, usually Cloudflare or your hosting company, and never at NIC.PY. If you don't know where your zone lives, ask whoever built your website.
- The list of mailboxes. One per person who answers email. Shared addresses like sales@ or info@ are handled with aliases or groups that land in the mailbox of whoever replies.
Three ways to get email on your domain
| Email service | Hosting email | Forwarding | |
|---|---|---|---|
| Examples | Zoho Mail, Google Workspace, Microsoft 365 | Your hosting's webmail (cPanel and similar panels) | Cloudflare Email Routing |
| What it does | Real mailboxes, with a phone app and webmail | Mailboxes on the same server as your website | Mail sent to your domain is forwarded to an inbox you already have |
| Reply from your domain | Yes, from the app or webmail | Yes | Needs an outgoing server (SMTP) as well |
| Best for | Most businesses | People whose hosting already includes email | One contact address that lands in your Gmail |
If your team already works in Gmail, Drive and Calendar, Google Workspace is the natural pick: it's the same Gmail, with your domain. If you want business email and nothing more, Zoho Mail does the job well; [email protected] runs on Zoho Mail. Forwarding works when all you need is for whatever reaches contact@ to show up on your phone, knowing your replies will go out from your Gmail.
One rule for all three: the email admin account has to be in your name. It's the same advice we give about the domain. If someone else created the mailbox from their own account, the day that person leaves, your email leaves with them.
Step by step with Zoho Mail
- Create the account with your domain. In Zoho Mail you open an organization account and type in the domain you already registered.
- Prove the domain is yours. Zoho gives you a TXT or CNAME record. Add that record to your DNS, go back to Zoho and click Verify. With Cloudflare, verification goes through in a couple of minutes.
- Create the mailboxes and aliases. One mailbox per person; sales@ and info@ as aliases of the mailbox of whoever replies.
- Change the MX records. First delete any MX records left from another provider. Then add three MX records at @:
mx.zoho.comwith priority 10,mx2.zoho.comwith 20 andmx3.zoho.comwith 50. - Add SPF. A TXT record at @. Zoho's help page shows
v=spf1 include:zoho.com ~all, but copy the value your own admin panel gives you: for builttoclick.com, the panel gaveinclude:zohomail.com. - Turn on DKIM. In the domain settings of the Zoho admin panel, you add a selector (ours is called zmail). Zoho generates a long key that goes in as a TXT record at
zmail._domainkey. Once it's published, go back to the panel and click Verify. - Add DMARC. A TXT record at
_dmarc. To start,v=DMARC1; p=none; rua=mailto:[email protected]blocks nothing and sends you reports on who is sending email with your domain. - Test it. Send an email to a Gmail address and check the authentication, as explained below.
Step by step with Google Workspace
- Sign up with your domain. Google asks you to verify it with a TXT record that starts with
google-site-verification=. - A single MX record. Value
smtp.google.com, priority 1. Accounts created before 2023 use five records with aspmx in the name; they still work and need no change. - SPF:
v=spf1 include:_spf.google.com ~all. - DKIM: in the Admin console, under Apps, Google Workspace, Gmail, Authenticate email. Google generates the TXT record for
google._domainkey; you add it to the DNS, wait for it to publish and click Start authentication. - DMARC: the same record as step 7 for Zoho.
The four records that decide whether your email arrives
| Record | Where it goes | What it does |
|---|---|---|
| MX | @ | Tells the world which server should receive email for your domain |
| SPF | TXT at @ | The list of servers allowed to send email with your domain. Only one per domain |
| DKIM | TXT at selector._domainkey | A signature on every email that the receiver checks with your public key |
| DMARC | TXT at _dmarc | What to do with an email that fails SPF and DKIM, and where to send reports |
How the email of builttoclick.com is set up
These are our records, looked up on November 6, 2026. Anyone can check them, because DNS is public: it's the quickest way to see how a company runs its email.
| Record | Value |
|---|---|
| MX | mx.zoho.com (10), mx2.zoho.com (20), mx3.zoho.com (50) |
| SPF | v=spf1 include:zohomail.com ~all |
| DKIM | At zmail._domainkey: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3... (the key goes on) |
| DMARC | v=DMARC1; p=reject with two addresses that receive the reports |
Our DMARC is set to p=reject: if someone sends an email pretending to be builttoclick.com and it fails the checks, the receiving server turns it away. A new domain should get there in stages: p=none for the first few weeks, read the reports, move to p=quarantine, and only then to p=reject. If you jump straight to reject and forgot to authorize a service, like your invoicing system or your newsletter tool, those emails stop arriving.
How to tell whether your emails will arrive
In Gmail, open an email you sent from your domain, tap the three dots and choose Show original. Three lines appear at the top: SPF, DKIM and DMARC. All three should say PASS. If one says FAIL or is missing, your emails are more likely to end up in spam.
Since February 2024, Gmail and Yahoo require SPF, DKIM and DMARC from anyone who sends a lot of email per day, and ask everyone else for SPF or DKIM. A business sending quotes won't reach those volumes, but the same checks carry weight when the filter decides where each email goes.
Mistakes we see often
Two SPF records
It happens when switching providers: the new SPF gets added and the old one stays. With two records, the check fails for both. There must be only one, with every service inside it. If you also send email from a mailing tool, its include goes in the same record: v=spf1 include:zoho.com include:sendgrid.net ~all.
Moving the website and breaking email
The website and the email are separate things that share the DNS. If you move to another host and someone replaces the whole zone, the MX records are lost and you stop receiving email without noticing. Before any move, write down the MX, SPF, DKIM and DMARC records you have today.
Replying from Gmail
With forwarding, the client writes to [email protected] and gets the answer from [email protected]. If you reply often, use an email service or set up an outgoing server.
The old MX is still alive
Until DNS updates, some email keeps reaching the previous provider. With Cloudflare the change shows up in minutes; with other providers it can take a few hours. Don't cancel the old account on the same day.
Your business still has no website on its own domain?We send you a free analysis of your business and tell you what to build first.
Message me on WhatsApp →If you want our help
When we build a website, the domain and its DNS are in order from day one, so adding email comes down to the MX, SPF, DKIM and DMARC records of the provider you pick. If your email already exists and lands in spam, message us with the domain and we'll tell you which record is failing.