Domain setup
Connect your domain to shipmail so you can create mailboxes and send email from your own address. This requires 4 DNS records.
1. Add your domain
Go to the Domains page in your dashboard and click Add domain. Enter your domain name (e.g. example.com) and click Add.
shipmail will automatically detect your DNS provider (Cloudflare, GoDaddy, Route 53, etc.) and display it next to the domain.
2. Add the DNS records
Pending domains show the required DNS records directly below the domain row. Add each record in your DNS provider, or click Download zone file to get all 3 records in BIND format that you can import directly.
| # | Type | Host | Value |
|---|---|---|---|
| 1 | MX | @ | 10 mx1.shipmail.to |
| 2 | TXT | @ | v=spf1 include:spf.shipmail.to -all |
| 3 | TXT | shipmail._domainkey | v=DKIM1; k=rsa; p=... |
The MX record routes incoming email to shipmail. SPF authorizes shipmail to send email on behalf of your domain. DKIM adds a cryptographic signature to verify outbound email authenticity. See understanding DNS records for a detailed explanation of each record.
3. SPF record merging
DNS only allows one SPF record per domain. If you already have an SPF record (e.g. for Google Workspace or another email provider), you need to merge them instead of adding a second one.
shipmail detects existing SPF records and shows a suggested merged value. For example, if your current SPF record is:
v=spf1 include:_spf.google.com -allYou would replace it with:
v=spf1 include:_spf.google.com include:spf.shipmail.to -all4. Wait for verification
shipmail automatically checks your DNS records every 30 seconds. Each record is verified independently. Green checks appear next to verified records as they propagate. The domain status changes to Verified once all 4 pass.
DNS propagation typically takes a few minutes, but can take up to 48 hours depending on your provider. If auto-verification times out after 10 minutes, you can click the Verify button manually.
Required: add a DMARC record
ShipMail requires DMARC before a domain can finish setup. It tells receiving servers what to do when an email fails authentication and improves deliverability and spoofing protection. Add this TXT record at _dmarc:
v=DMARC1; p=rejectSee understanding DNS records for details on DMARC policy options and optional reporting fields.
Provider-specific notes
For detailed step-by-step instructions with provider-specific tips, see the DNS setup by provider guide.
Cloudflare
Go to your domain in the Cloudflare dashboard, click DNS in the sidebar, then Add record. Add each record type separately. For TXT records, paste the value exactly as shown.
GoDaddy
Go to My Products, find your domain, click DNS, then Add New Record. Add each record type separately. For the MX record, set priority to 10.
Namecheap
Go to Domain List, click Manage on your domain, then Advanced DNS. Click Add New Record for each entry. Use @ as the host for root records.
AWS Route 53
Go to the Route 53 console, select your hosted zone, and click Create record. For TXT records, wrap the value in double quotes. Leave the record name empty for root records.
Troubleshooting
Some records verified but not all
Each record is checked independently. If some show green checks but others do not, double-check the records that are still pending. Make sure the type, host, and value match exactly.
SPF record conflict
If you see a warning about an existing SPF record, do not add a second SPF TXT record. Use the merged value shown in the dashboard. Having two SPF records will cause email delivery failures.
DKIM TXT record not found
Make sure the TXT record host is exactly shipmail._domainkey (not the full domain, your provider appends it). Copy the full DKIM value from the dashboard, including the v=DKIM1 prefix.
DNS provider not detected
Provider detection works by checking your nameserver records. If your provider is not detected, the setup process is the same. Add the records in your DNS provider and verification will work regardless.