DNS records explained
Shipmail needs 4 DNS records to send and receive email on your domain: MX, SPF, DKIM and DMARC. This page explains what each record does, why it matters for deliverability, and how to check your setup.
For step-by-step setup instructions, see the domain setup guide.
Check the published mail server hostnames and their priorities with the free MX record check. No signup required.
Last updated
Required records
MX record
| Type | Host | Value |
|---|---|---|
| MX | @ | 10 mx1.shipmail.to |
The MX (Mail Exchange) record tells other mail servers where to deliver email for your domain. Without it, incoming email has nowhere to go. The number before the server (10) is the priority, and servers try lower numbers first. Shipmail uses one MX server, so the priority doesn't matter in practice.
SPF record
| Type | Host | Value |
|---|---|---|
| TXT | @ | v=spf1 include:spf.shipmail.to -all |
SPF (Sender Policy Framework) lists the servers allowed to send email for your domain. When a server receives an email from your domain, it checks the SPF record to see if the sending server is on that list. If it is not, the email may be rejected or marked as spam. The -all suffix means "reject everything not listed."
DKIM record
| Type | Host | Value |
|---|---|---|
| TXT | shipmail._domainkey | v=DKIM1; k=rsa; p=... |
DKIM (DomainKeys Identified Mail) adds a cryptographic signature to every outgoing email. Shipmail signs each message with a private key, and the DKIM TXT record publishes the matching public key. Receiving servers use it to check the signature. A valid signature means the message came from your domain and nobody changed it on the way.
A domain bought through Shipmail also has an MX and a TXT record on the mail subdomain, for bounce handling. Shipmail adds them for you. Don't add them to a domain you connect from another provider.
A domain you connect can show as "mailed-by" in Gmail if you add two optional records, an MX and a TXT on the bounce subdomain. Your email works without them. The dashboard doesn't offer them when the domain or its bounce subdomain already sends newsletters or transactional email in Shipmail. See DNS setup for the steps.
Required: DMARC record
DMARC (Domain-based Message Authentication, Reporting and Conformance) is required for Shipmail setup by default. It ties SPF and DKIM together with a policy that tells receiving servers what to do when an email fails authentication. Shipmail recommends the minimal record below. Reporting fields like rua are optional.
| Type | Host | Value |
|---|---|---|
| TXT | _dmarc | v=DMARC1; p=reject |
DMARC policy options
The p= value in your DMARC record decides what happens to emails that fail authentication. If you're moving from another provider and don't want to block real email during the switch, start with none and tighten it later.
| Policy | Effect | When to use |
|---|---|---|
| p=none | Monitor only | Receiving servers take no action on failing emails. Use it while you migrate from another provider, to watch authentication results without risking delivery. |
| p=quarantine | Mark as spam | Emails that fail authentication go to the spam folder instead of the inbox. |
| p=reject | Block entirely | Receiving servers refuse emails that fail authentication. This is the strictest setting. |
Verify records manually
Shipmail checks your records for you, but you can also check them yourself with dig (Linux/macOS) or nslookup (Windows). Replace example.com with your domain.
MX record
dig MX example.com +shortSPF record
dig TXT example.com +shortDKIM record
dig TXT shipmail._domainkey.example.com +shortDMARC record
dig TXT _dmarc.example.com +shortOn Windows, replace dig with nslookup -type=TXT example.com (swap TXT for the record type).
If a published value doesn't match the expected one, see the domain troubleshooting guide for MX, SPF, DKIM, and DMARC examples.
How the records work together
When someone receives an email from your domain, their mail server runs two checks:
- SPF check. Did this email come from a server listed in your SPF record?
- DKIM check. Does the cryptographic signature on the email match the public key in your DKIM record?
Message
you@yourdomain.com
SPF
Allowed server?
DKIM
Signature valid?
DMARC
Policy decides
An email passes DMARC when at least one of these checks passes for the domain in its From address. Your DMARC record tells the receiving server what to do when neither passes: report it, quarantine it, or reject it. Together, SPF and DKIM let a receiving server confirm the message really came from your domain. That is what makes spoofing hard.
Common pitfalls
Multiple SPF records
DNS allows only one SPF TXT record per domain. Adding a second one instead of merging makes both fail. If another service needs SPF too (Google Workspace, Microsoft 365 and others), merge the include statements into one record.
Cloudflare proxy mode on MX records
Cloudflare's orange cloud proxy only works for HTTP traffic, so MX records must not be proxied. Turn the proxy toggle off (grey cloud) for your MX record. TXT records are never proxied.
Appending the domain to the host
Most DNS providers add your domain to the host field for you. If your domain is example.com and you enter shipmail._domainkey.example.com as the host, the record becomes shipmail._domainkey.example.com.example.com. Enter just shipmail._domainkey instead.
High TTL slowing propagation
If existing records have a high TTL (for example 86400 seconds, or 24 hours), changes take longer to propagate. Give new records a low TTL at first (300 seconds, or 5 minutes). You can raise it after verification.
Quotes around TXT values
Some providers (notably AWS Route 53) need TXT values wrapped in double quotes. Others add the quotes for you. If verification fails, check whether your provider needs them.