uSend Docs
DNS provider guides

Hostinger

Add the DKIM, return-path and DMARC records usend shows in Hostinger.

This page shows where the records go in Hostinger and its quirks. Menu labels change over time; if yours differ, look for the DNS records list of the domain.

Before you start

  1. Add the domain in usend (Domains, or POST /domains). usend shows the exact records for it, and the values are unique to your domain, so copy them from there.
  2. Find where the domain's DNS is hosted. DNS is edited at whoever runs the domain's nameservers, which is not always the registrar you bought it from. If it is not Hostinger, follow that provider's guide instead.

The records

usend shows this set of records. Names are relative to your domain, acme.com in the example.

RecordNameTypeValue
DKIMrs1._domainkeyTXTv=DKIM1; k=rsa; p=MIIB... (long, unique to your domain)
Return path and SPFsend and/or send-sesCNAMEthe host usend shows, for example rp-ses-us-east-1.usend.et
DMARC (recommended)_dmarcTXTv=DMARC1; p=none;
Receiving (only if you enabled it)@MXthe host usend shows, priority 10

The domain's page lists one return-path CNAME for each sending transport enabled on usend, so you may see send, send-ses or both. Add every one that is shown. The MX and SPF records for the return path live behind that CNAME, so you do not add a separate MX or SPF record for sending, and your own SPF record at the root does not need to change. See Custom return path to choose another label, and DMARC before you tighten the policy.

Warning

Only add the receiving MX record if you turned on receiving. An MX at the root sends all mail for that name to usend. Use a dedicated subdomain if the domain already receives mail elsewhere.

Add them in Hostinger

Sign in to hPanel, open Domains, choose Manage for the domain and then DNS / Nameservers. The records are under DNS records. It applies when the domain uses Hostinger's nameservers.

In the Manage DNS records form select the Type, fill Name, the value field and TTL, then press Add Record.

The Name is relative to your domain: rs1._domainkey. Use @ for the domain itself.

Add the DKIM TXT record, each return-path CNAME and the DMARC TXT record.

Hostinger-specific notes

  • If Hostinger already created a DMARC or SPF record for you, keep the existing DMARC policy rather than adding a second one.
  • Hostinger's site-builder email records (MX at the root) are separate; leave them in place.
  • If your domain already has a DMARC record, keep it: you only need one, and usend accepts any record that starts with v=DMARC1.

Verify

Back in usend, press Verify on the domain (or POST /domains/{id}/verify). usend checks with public DNS resolvers, so it sees what other mail servers see. Records usually show up within minutes; some providers take longer. Each record gets its own status, and usend keeps re-checking for 24 hours.

If a record stays pending or failed, see Domain not verifying. Background: Verify a domain.