MailFlatDocs
Documentation/DNS provider guides/Hostinger

Connect your domain on Hostinger

Where Hostinger hides the DNS editor, and the one field that decides verification.
Hostinger adds your domain to whatever you type
Enter names without your domain — _mailflat-verify, not _mailflat-verify.acme.com. Typing the full name stores it as _mailflat-verify.acme.com.acme.com, and no amount of waiting will make that verify. In the dashboard, keep the Provider dropdown on name only and use the copy button next to each Host.

Where the DNS editor is

  1. Log in to Hostinger
  2. Domains → Domain portfolio
  3. Pick your domain
  4. DNS / Nameservers
  5. Add record
Field names here: Name for the record name, Points to / TXT value for the value, Priority for MX priority.

The five records, as Hostinger wants them

Your real values are on Domains in the dashboard — the verification token and the DKIM key are unique to your domain. Everything else looks exactly like this.
TypeNamePoints to / TXT valueWhat it does
TXT_mailflat-verifymf-verify-… (yours is in the dashboard)Proves you own the domain. Verification fails without it.
MX@mail.mailflat.net.Priority 10PriorityRoutes incoming mail to MailFlat.
TXT@v=spf1 include:mailflat.net ~allAuthorises MailFlat to send for your domain.
TXTmail._domainkeyv=DKIM1; k=rsa; p=… (yours is in the dashboard)Signs your outgoing mail.
TXT_dmarcv=DMARC1; p=none;Tells receivers what to do when a check fails.

Hostinger specifics

Hostinger adds your domain for you. @ is the root; mail._domainkey stays short.
Make sure the domain actually uses Hostinger's nameservers — if you changed them, edit DNS wherever they now point.

Then verify

Back on Domains, press Verify. If it fails, the message says what is actually wrong — including the case where your records landed one level too deep, with the exact name we found them under. DNS changes are usually visible within minutes; a failure that names a wrong record will not fix itself by waiting.
More on custom domains: Custom domains (BYOD).