Hostinger manages DNS in hPanel with fields for Type, Name, value, Priority and TTL. To receive mail at every address on a domain with Free Domain Mail, add one TXT record that proves you own the domain and one MX record that sends incoming mail to mx.freedomainmail.com, then remove Hostinger's own MX records.

Step-by-step setup
- 1Sign in to hPanel, open Domains in the left sidebar, then DNS, and choose the domain.
- 2Check that the domain uses Hostinger's nameservers; otherwise add the records at your DNS provider.
- 3Add a TXT record with Name _maildock-verify and the maildock-verify=… value shown in the app.
- 4Add an MX record with Name @, Mail server mx.freedomainmail.com and Priority 10.
- 5Delete the mx1.hostinger.com and mx2.hostinger.com MX records.
- 6Wait for propagation, then run DNS Checker below; once both records pass, every address at the domain receives mail.
What goes in each DNS field
| Type | Name / Host | Value / Data | Priority |
|---|---|---|---|
MX | @ | mx.freedomainmail.com | 10 |
TXT | _maildock-verify | maildock-verify=… (shown in the app) | — |
Interface reference: Hostinger — How to manage MX records. Always copy the domain-specific values shown inside your Free Domain Mail setup.
The two records for a catch-all inbox
Free Domain Mail turns a domain you own into a catch-all inbox: every address at the domain receives mail, and there are no mailboxes to create. Messages are kept for 90 days and never forwarded; sending from the domain is optional and needs three more TXT records shown in the app.
You add two records: a TXT record at _maildock-verify that proves you own the domain, with the maildock-verify=… value shown in the app (it is unique to your domain, so copy it exactly), and an MX record for the root of the domain that points to mx.freedomainmail.com with priority 10.
Type Name / Host Value Priority
TXT _maildock-verify maildock-verify=… (shown in the app) —
MX @ mx.freedomainmail.com 10Add the records in hPanel
In hPanel open Domains in the left sidebar, then DNS, and pick the domain. You can also go to Domains, Manage, then DNS / Nameservers and Manage DNS records.
Add a TXT record with Name _maildock-verify and the maildock-verify=… value from the app. Then add an MX record with Name @, Mail server mx.freedomainmail.com and Priority 10.
Delete Hostinger's MX records
Hostinger domains usually have MX records for mx1.hostinger.com with priority 5 and mx2.hostinger.com with priority 10. A lower number wins, so while mx1.hostinger.com is there, most mail goes to Hostinger instead of your inbox. Delete both.
If the domain receives mail in a Hostinger Email mailbox you still use, connect a different domain instead: the MX records decide where all mail for the domain goes.
Records only work with Hostinger's nameservers
hPanel lets you edit records even when the domain points to other nameservers, but they only take effect once the domain uses Hostinger's nameservers. If the domain uses Cloudflare or another DNS provider, add the records there. Hostinger says changes can take up to 24 hours to spread.
SPF, DKIM and DMARC: only if this domain also sends mail
Receiving at the catch-all inbox does not need SPF, DKIM or DMARC. These records are only needed if this domain also sends mail: through Free Domain Mail, add the three TXT records shown on the domain page (DKIM at fdm1._domainkey, an SPF include for _spf.freedomainmail.com and DMARC); through another provider, use that provider's values.
In that case keep one SPF TXT record at the root and merge every sending service into it rather than adding a second v=spf1 record. Copy DKIM selectors exactly as that provider shows them, and publish DMARC as a TXT record at _dmarc, starting with p=none.
Check the result
Wait for the old TTL to pass, then run an MX lookup from outside Hostinger. The answer should list only mx.freedomainmail.com.
Send a message from an outside account to any name at the domain, even one you have never used. If it arrives in the inbox, the catch-all is working.
Common errors with Hostinger
Hostinger Email's MX records still listed
Domains set up for Hostinger Email have mx1.hostinger.com (priority 5) and mx2.hostinger.com (priority 10). The lower number wins, so while they remain most mail goes to Hostinger. Delete both and keep only mx.freedomainmail.com.
Something other than @ in Name
Hostinger's form expects @ as the Name of an MX record for the root domain. Use _maildock-verify, without the domain, for the TXT record.
How long DNS takes at Hostinger
Hostinger only says that propagation starts after the change and takes some time to complete; it gives no fixed figure. A new record is usually visible within an hour, and resolvers that cached the old Hostinger MX records keep them until their TTL runs out.
Sources, checked on November 8, 2026:
Common mistakes to avoid
- Leaving mx1.hostinger.com at priority 5, which receives mail before mx.freedomainmail.com.
- Adding records in hPanel while the domain uses another provider's nameservers.
- Typing the full domain into Name, which creates _maildock-verify.yourdomain.com.yourdomain.com.
Frequently asked questions
What do I put in Name for the MX record?
@, which Hostinger uses for the root of the domain.
Why does mail still go to Hostinger?
Check for mx1.hostinger.com: with priority 5 it is preferred over a priority 10 record. Delete it and any other old MX records.
Can I keep my Hostinger website?
Yes. Website A and CNAME records are separate from MX records, which only decide where mail is delivered.
Do I need to create each email address?
No. Once the TXT and MX records are verified, every address at the domain receives mail.