Skip to Content

Custom domains for email sending platforms

Sending records added without breaking existing mail. Your SPF include is merged into the customer's record, never duplicated.

For platform engineers, onboarding product managers and support leads at email platforms such as lemlist, Salesforge and Instantly.

SPF at acme.comsign in
Already published
v=spf1 include:_spf.google.com ~all
After the merge
v=spf1 include:_spf.google.com include:spf.example.net ~all
CNAMEs1._domainkey.acme.comlives1.dkim.example.net
Illustration. Your include joins the record already there, before its all qualifier. example.net stands for your platform.

Platforms that send as their customers

  1. Send as each customer's domain

    Partial fit
    CNAME abc123._domainkey.mail.acme.com abc123.dkim.amazonses.com
    SPF merged, never a second record.

    Notifications, receipts and campaigns go out from the customer's own address. Your include is merged into their SPF, never written as a second record. DKIM CNAMEs are checked. MX and SPF merges are written but not value-checked.

    Docs: Email DNS & SPF merge
  2. Transactional email APIs

    Partial fit
    MX mail.acme.com 10 feedback-smtp.us-east-1.amazonses.com
    Per-account DKIM selectors, each value-checked.

    Receipts and password resets from a SaaS's sending domain. The DKIM selectors are per account, so your platform supplies them and each CNAME is checked against its value. MX records are not value-checked.

    Docs: Bring your own records
  3. Email marketing for small businesses

    CNAME k1._domainkey.acme.com dkim.example.net
    DKIM CNAMEs checked, doubled hosts flagged.

    Newsletters from a small business's own domain. The DKIM CNAMEs are checked, and a doubled host name such as acme.com.acme.com is flagged by the live check.

    Docs: Troubleshooting
  4. Commerce email and SMS

    Partial fit
    CNAME send.acme.com send.example.net
    Static routing in one supplied set.

    Branded sending subdomains for online stores. Static routing with CNAMEs and a TXT fits one supplied record set. NS delegation is refused in a connection and accepted only inside managed DNS zones, which are rolling out.

    Docs: Managed DNS
  5. Lifecycle and product messaging

    Partial fit
    MX em1.acme.com 10 mx.example.net
    Hourly drift check on the held records.

    Onboarding and retention email from a SaaS's sending subdomain. The hourly drift check covers the records the connection holds. MX values are not value-checked.

    Docs: Monitoring and services
Three more jobs
  1. CRM sending domains

    CNAME s1._domainkey.mail.acme.com s1.dkim.example.net
    DKIM checked, CNAME collisions flagged first.

    Sales email from the CRM on a subdomain not used for hosting. Its DKIM CNAMEs are checked, and a CNAME collision is flagged before writing.

    Docs: Setup types & the ask gate
  2. Help desk and chat email

    CNAME hd1._domainkey.acme.com dkim.example.net
    DKIM checked, a needed SPF include merged.

    Support replies from support@ on the company's domain. The DKIM CNAMEs are checked, and an SPF include that is still needed is merged in.

  3. Enterprise engagement platforms

    CNAME links.eu.acme.com links.example.net
    One connection per subdomain, in bulk.

    Regional or brand subdomains, each with link-branding and sending records. The API creates one connection per subdomain in bulk.

    Docs: Create connections for a set of domains in one call

Outbound and cold email

3 jobs

Many sending domains per customer, each with its own tracking subdomain.

  1. CNAME track.acme.com tracking.example.net
    A tracking subdomain per sending domain.

    A tracking subdomain per sending domain, so each sender's links stop sharing one host. Deliver the vendor's CNAME as a supplied record, or serve the host over HTTPS on the edge on Growth and up.

    Docs: Where domains point
  2. Cold email inbox infrastructure

    Partial fit
    MX acme.com 10 mx.example.net
    Bulk create across an account's domains.

    Providers that set every record across dozens of domains per agency. Bulk create and a remembered provider key connect an account's domains together. MX and SPF merges are written but not value-checked.

    Docs: Buying a domain
  3. White-label outbound for agencies

    Partial fit
    CNAME portal.acme.com customers.example.com
    Client labels and setup links for agencies.

    Lead generation agencies serving many clients under their own brand. The agency workspace adds client labels and setup links. Not every email record is value-checked.

    Docs: Agencies

Business email and inbound mail

5 jobs

Mail keeps arriving while the domain also points at a platform.

  1. Mailbox suites on a customer's domain

    Partial fit
    MX acme.com 1 smtp.google.com
    MX, SPF, DKIM and DMARC in one apply.

    Platforms that bundle email, and site builders whose customers add mail beside the site. MX, SPF as a merge, DKIM and DMARC go in one apply. MX is not value-checked.

  2. Reply and inbound-parse subdomains

    Partial fit
    MX reply.acme.com 10 inbound.example.net
    A supplied MX on the reply subdomain.

    Help desks and CRMs that receive replies on reply.acme.com. A supplied MX on the subdomain is written but not value-checked.

  3. Email forwarding and aliases

    Partial fit
    MX acme.com 10 mx.example.net
    MX and an SPF merge, no forwarding product.

    A hello@ address on a domain without a mailbox. MX and an SPF merge can be supplied. CustomDomain™ has no forwarding product of its own.

  4. Mailboxes bundled with a domain

    Partial fit
    TXT acme.com v=spf1 include:_spf.google.com ~all
    The mail provider's TXT, value-checked.

    Site builders, registrars and MSPs that bundle mailboxes with a domain. The mail provider's TXT record is checked against its value. MX is not.

  5. Privacy and budget mail hosts

    Partial fit
    MX acme.com 10 mail.example.net
    The full mail set in one apply.

    Mail hosts whose paid plans include custom domains, often many per account. The full set goes in one apply. MX is not value-checked.

SPF, DKIM and DMARC records

6 jobs

The record mechanics behind sending as a customer's domain.

  1. Merge SPF, never add a second

    TXT acme.com v=spf1 include:mailgun.org include:_spf.google.com ~all
    One SPF record, your include deduplicated.

    A domain may publish only one SPF record. The SPF merge adds your include to the customer's record, deduplicated and keeping its qualifier, so policy never loosens. It is refused past 10 lookup mechanisms or 255 characters.

  2. DKIM keys too long for the panel

    Partial fit
    CNAME sel1._domainkey.acme.com sel1.dkim.example.net
    A DKIM CNAME instead of a long TXT.

    A 2048-bit DKIM key in a TXT record runs past 255 characters, and some DNS panels refuse or cut it. A DKIM CNAME that points at the sender avoids the problem.

  3. DKIM by CNAME delegation

    CNAME selector1._domainkey.acme.com selector1.dkim.example.net
    Selector CNAMEs, so keys rotate without edits.

    Selector CNAMEs point at the sender, so keys rotate with no change in the customer's DNS. Supplied records ride the sign-in, API key and by-hand paths, and each CNAME is checked against its value.

  4. DMARC beside your records

    Partial fit
    TXT _dmarc.acme.com v=DMARC1; p=none; rua=mailto:dmarc@example.com
    One DMARC TXT per name, no merge.

    Publishing DMARC next to a platform's sending records. DMARC goes in as a TXT record, one per name. There is no policy merge or staged rollout.

  5. Bulk-sender rules at large inboxes

    Partial fit
    TXT _dmarc.acme.com v=DMARC1; p=none; rua=mailto:dmarc@example.com
    SPF, DKIM and DMARC grouped, alignment unchecked.

    Large senders need aligned SPF and DKIM plus a DMARC record. The email template groups MX, an SPF merge, a DKIM CNAME and DMARC for the widget's email screen. Alignment is not checked.

  6. SPF over its lookup budget

    Partial fit
    TXT acme.com v=spf1 include:mailgun.org include:_spf.google.com ~all
    Refused past 10 lookup mechanisms or 255 characters.

    Several senders can push an SPF record past 10 lookups. The merge is refused past 10 lookup mechanisms or 255 characters, counting only the record's own mechanisms. Nested includes and void lookups are not counted.

Jobs are a full fit unless marked Partial fit, which means CustomDomain™ handles part of the job today. Email DNS records (docs)

Also covered, with SPF merges and DKIM in a supplied set or one subdomain CNAME: event and community email, recruiting email, and preference and cancel pages. Also covered, each one supplied tracking CNAME: sales engagement tracking and outreach tools that send from a mailbox.

Records another service checks, such as an SSO TXT, are on Domain verification.

Common questions

Will connecting a sending domain break existing mail?

CustomDomain™ merges your SPF include into the customer's existing SPF record instead of adding a second one, which would break mail. Records already in the way are flagged before anything is written.

Which email records are checked against their values?

CNAME, A, AAAA and TXT records. MX, SPF merge and CAA records are written but not value-checked, so a set made only of those can go live without confirming them.

Does CustomDomain™ check DMARC alignment?

No. DMARC goes in as a TXT record you supply. Alignment, policy merges and staged rollouts are not checked or managed.

Where your customers' DNS is hosted

  • Cloudflaresign in
  • NameSiloone-click
  • GoDaddyapi key
  • Amazon Route 53api key
  • Namecheapby hand
  • Squarespaceby hand

Ways in from the provider census, read November 2, 2026.

Trademark notices

Names and logos belong to their owners. We write the records where the provider allows it and show the exact ones where it does not. A name here does not mean the provider endorses us.

Cloudflare and the Cloudflare logo are trademarks and/or registered trademarks of Cloudflare, Inc. in the United States and other jurisdictions.

lemlist, Salesforge, Instantly and other names on this page are trademarks of their owners. CustomDomain™ is not affiliated with or endorsed by them. Facts about other products were read from their public pages on November 2, 2026.

Put your customers on their own domains.

Your first ten domains connect free. No card needed to sign up.