Manage your email domains
Configure custom domains to send and receive email under your own brand. Mailpipe guides you through DNS verification so you can be up and running in minutes.
Call the POST /api/v1/domains endpoint with the domain name you want to verify. Mailpipe will return a set of DNS records you must add to your registrar.
curl -X POST "https://api.mailpipe.dev/v1/domains" \
-H "Authorization: Bearer mp_live_your-api-key-here" \
-H "Content-Type: application/json" \
-d '{ "domain": "yourdomain.com" }'{
"id": "dom_abc123",
"domain": "yourdomain.com",
"status": "pending",
"created_at": "2025-01-15T10:00:00Z",
"dns_records": [
{ "type": "MX", "host": "@", "value": "mx.mailpipe.dev", "priority": 10 },
{ "type": "TXT", "host": "@", "value": "v=spf1 include:mailpipe.dev ~all" },
{ "type": "TXT", "host": "mp._domainkey", "value": "v=DKIM1; k=rsa; p=MIIBIjANBgkq..." },
{ "type": "TXT", "host": "_dmarc", "value": "v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain.com" }
]
}After adding the DNS records to your registrar, ask Mailpipe to check them. Verification is usually instant once DNS has propagated — this can take anywhere from a few seconds to 48 hours.
curl -X POST "https://api.mailpipe.dev/v1/domains/dom_abc123/verify" \ -H "Authorization: Bearer mp_live_your-api-key-here"
Tells other mail servers where to deliver email for your domain
Type: MX Host: @ (or leave blank — depends on your registrar) Priority: 10 Value: mx.mailpipe.dev
If you already have MX records pointing elsewhere, remove them first so Mailpipe receives all inbound mail.
Authorises Mailpipe servers to send email on your behalf
Type: TXT Host: @ Value: v=spf1 include:mailpipe.dev ~all
The ~all suffix uses a softfail policy. Use-all for strict enforcement once you are confident Mailpipe is your only outbound mail provider.
Proves outbound messages have not been tampered with in transit
The exact DKIM public key is unique to your domain. Copy the value returned by thePOST /v1/domains response — it looks like:
Type: TXT Host: mp._domainkey Value: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA...
Mailpipe rotates DKIM keys periodically for security. The dashboard will notify you when a key rotation is required.
Instructs receivers what to do when SPF or DKIM checks fail
Type: TXT Host: _dmarc Value: v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain.com; ruf=mailto:dmarc@yourdomain.com; fo=1
| Tag | Meaning |
|---|---|
| p=none | Monitor only — take no action on failures (start here) |
| p=quarantine | Send failures to spam/junk folder |
| p=reject | Block delivery entirely (strictest — use once stable) |
/v1/domainsList all domains on your account/v1/domainsAdd a new domain and get DNS records/v1/domains/:idRetrieve domain details and current status/v1/domains/:id/verifyTrigger a DNS verification check/v1/domains/:idRemove a domain and its mailboxesDNS records have been returned but not yet confirmed. Either you have not added them yet or DNS propagation is still in progress. Re-run the verify endpoint to check again. Propagation typically completes within 5–30 minutes but can take up to 48 hours.
All required DNS records were detected and validated. Your domain is ready to send and receive email through Mailpipe. You can now create mailboxes and configure routing rules for this domain.
Verification could not complete because one or more DNS records are missing or incorrect. Retrieve the domain details to see which records failed the check, correct them at your registrar, then trigger verification again.
curl -X GET "https://api.mailpipe.dev/v1/domains/dom_abc123" \
-H "Authorization: Bearer mp_live_your-api-key-here"
# Look for "verification_errors" in the response
# e.g. { "verification_errors": ["MX record not found", "SPF include missing"] }Mailpipe re-checks verified domains every 24 hours. If a DNS record is removed after verification the domain will be moved back to pending and you will receive an email alert.