MX records are the reason “[yourname@yourdomain.com” actually reaches an inbox instead of disappearing into nothing.
Below, I’ll explain what they do, then walk through setting them up step by step.
For the hands-on part, I used a domain registered at Namecheap as my example, since that’s a registrar a lot of readers actually use, but I’ll also cover what to expect if your domain sits somewhere else, like GoDaddy or Cloudflare, since the underlying steps look the same everywhere even when the menus don’t.
What Is an MX Record?
An MX (Mail Exchange) record is a DNS entry that tells the internet which mail server should receive email for your domain. Without one, mail sent to your address has no destination to route to. It’s not that delivery fails quietly somewhere in the middle; there’s simply nowhere for it to go in the first place.
Most domains have more than one MX record, and each one carries a priority value, sometimes labeled “preference.”
Lower numbers get tried first. If the top-priority server doesn’t respond, the sending server falls back to the next one. That’s why most setups use two MX records rather than one: the second acts as a backup if the first has a brief issue.
Here are the exact values Hostinger uses:
| Priority | Value | TTL |
|---|---|---|
| 5 | mx1.hostinger.com | 14400 (4 hrs) |
| 10 | mx2.hostinger.com | 14400 (4 hrs) |
mx1 is the preferred server, since it has the lower priority number, with mx2 as the fallback.
With those values in hand, here’s how to actually get them into place.
Step 1: Check Whether You Already Have These Records
Before changing anything, confirm whether this step is even necessary for you. If your domain is registered with Hostinger and its DNS hasn’t been pointed anywhere else, these records are already active.
- In hPanel, go to Emails > Domain settings
- Look for the MX records under “Receive emails in your mailbox”
If both records are already listed and showing as verified, you’re done; no further action needed. If you don’t see them, or your domain is registered somewhere other than Hostinger, move on to Step 2.
Step 2: Find Where Your Registrar Manages Email Routing
This is the step that varies most by registrar, so I’ll walk through it using Namecheap as a concrete example, then cover what to expect elsewhere right after.
Using Namecheap as the example:
- Log into Namecheap and go to Domain List
- Click Manage next to the domain you’re setting up
- Click the Advanced DNS tab
- Look for a Mail Settings section, which shows a dropdown with several options: No Email Service, Email Forwarding, MXE Record, Custom MX, Private Email, and Gmail
Before changing that dropdown, check what it’s currently set to. On the domain I tested, it was set to Email Forwarding, Namecheap’s own built-in forwarding service, evident from a locked TXT record sitting underneath it that can’t be edited while forwarding is active.
Once you’ve confirmed that, change the dropdown to Custom MX. That’s what unlocks the ability to add your own MX records in the next step.
How to Set Up Domain Email
Step 3: Add Hostinger’s MX Records
With Custom MX selected, you’ll see fields for adding MX records directly.
- Click Add New Record
- Set Type to MX Record, Host to @, Value to mx1.hostinger.com, and Priority to 5
- Click Add New Record again
- Set Type to MX Record, Host to @, Value to mx2.hostinger.com, and Priority to 10
- Click Save All Changes
Once saved, both records will show under the Mail Settings section with the correct priorities, 5 for mx1 and 10 for mx2, matching Hostinger’s own configuration exactly.
What If Your Domain Isn’t on Namecheap?
The exact screens differ, but every major registrar follows the same underlying pattern. Find where DNS or mail routing is managed, make sure nothing is set to override custom MX records, then add the two records above.
- GoDaddy: Go to your domain’s DNS Management page and add records directly under the DNS Records section, no separate “mail settings” toggle to switch first.
- Cloudflare: Go to the DNS tab for your domain and add MX records there. Cloudflare requires the proxy status on MX records to stay set to “DNS only,” since MX records can’t be proxied.
- Google Domains or Squarespace Domains: Look for a “Custom resource records” or “Email” section within DNS settings.
Wherever you land, you’re looking for the same three fields: a record type of MX, a host or name of @ (or sometimes your bare domain name), and a value plus priority matching the Hostinger table above.
If your registrar has any kind of built-in email or forwarding service already active, check it the same way I did on Namecheap before switching away from it.
Step 4: Verify the Records Are Actually Live
Saving the records in your registrar isn’t the same as confirming they’re resolving out on the internet. DNS changes need time to propagate, and the only way to know for sure is to check from outside your own account.
- Go to mxtoolbox.com
- Make sure the MX Lookup tool is selected
- Enter your domain name and run the lookup
When I ran this, the results showed both Hostinger MX records exactly as expected, mx1.hostinger.com at priority 5 and mx2.hostinger.com at priority 10, each resolving to a real IP address, with a green “DNS Record Published” confirmation underneath. That result is your actual proof the records are live, not just saved in a dashboard somewhere.
A “DMARC Policy Not Enabled” note, for instance, is a separate configuration entirely and doesn’t mean your MX setup failed. Focus on the MX Lookup section and the “DNS Record Published” result to confirm mail routing is working.
The MX values themselves are simple, one priority 5 record and one priority 10 record, wherever your domain happens to be registered. The part worth real attention is checking what mail service you’re switching away from before you make the change, and confirming the records actually propagated with an outside tool rather than trusting your registrar’s saved confirmation alone.
Troubleshooting Common MX Record Issues
- Lookup shows no MX records at all. DNS propagation can take anywhere from a few minutes to a few hours depending on your previous record’s TTL. Wait and re-check before assuming the setup failed.
- Only one MX record appears instead of two. Double-check both records were actually saved. It’s easy to add the second one and forget to click save or confirm on that specific entry.
- Mail stopped routing after switching your mail settings. If your domain was previously using a different service, like Namecheap’s Email Forwarding or a similar built-in option elsewhere, switching to Custom MX replaces that entirely. Anything relying on the old service needs to be reconfigured separately.
- MXToolbox shows unrelated warnings. DMARC, BIMI, or blacklist warnings on the same results page are separate from MX routing. Confirm the MX Lookup section itself shows both records with a “DNS Record Published” result before troubleshooting further.
- Records look correct, but mail still isn’t arriving. Confirm the mailbox itself exists and is active in Hostinger’s email hosting panel. MX records only route mail to the server; they don’t create the mailbox that receives it.
