Custom Email Domains

Add and verify your own sending domain through Yaplet's guided, self-checking setup — to send branded emails and unlock newsletter campaigns.

Why Use a Custom Domain?

With a custom domain, your emails come from your own address (like [email protected]) instead of a shared @yaplet.io address. This matters for three key reasons:

Brand Trust

Customers recognize and trust emails from your own domain. A @yaplet.io address may look unfamiliar and get ignored.

Better Deliverability

Custom domains build their own sending reputation, so your emails are far more likely to reach inboxes instead of spam folders.

Newsletter Access

Newsletter campaigns require a verified custom domain. This is not optional — Yaplet enforces it to protect deliverability for all users.

You cannot send newsletter campaigns from a @yaplet.io email address. When you try to create a newsletter campaign, Yaplet checks for a verified custom domain email. If none exists, the campaign cannot be created and you'll be prompted to add a custom domain first.

How Setup Works

Custom-domain setup has three parts: add the domain in Yaplet, add the DNS records it generates at your domain registrar, and let Yaplet verify them. The difference from a typical DNS setup is that the page checks your work for you — it polls your DNS automatically and shows a live status next to every record, so you're never guessing whether something propagated.

Plan for 15–30 minutes of hands-on work, plus anywhere from a few minutes to 48 hours for DNS to propagate (usually well under an hour).

Add Your Domain

Adding a domain is a full-screen guided flow with three steps. A bar at the top shows which step you are on, and has Exit (on the last step Back) and a button to move on: Next, then I've added them, then Done.

Start the flow

Go to Settings → Connections → Emailing → Custom Domains and click Add domain (the first time, Add your first domain). The Add a domain window opens on step 1, Choose domain.

Enter your domain

Under Which domain will you send from?, type your domain in the Sending domain field — for example yourcompany.com (just the domain, no https:// or www.). Below the field, What your recipients see previews an address such as [email protected]. Use your main domain for addresses like [email protected]. If you send a lot of newsletters, a subdomain such as news.yourcompany.com keeps their reputation separate from your everyday email.

Click Next

Yaplet checks the name, then generates your DNS records and requests an SSL certificate for link tracking. All of this happens in this one step — the Next button shows a loading indicator until it's done. Then step 2 opens.

Add the records at your DNS provider

Step 2, Add DNS records, says Add these records at your DNS provider. Choose your provider in the Your DNS provider list — Yaplet preselects it when it can tell from your domain's nameservers (We detected … from your domain's nameservers.). A short numbered guide for that provider appears next to the records: Cloudflare, GoDaddy, Namecheap, Squarespace (Google Domains), Hostinger, or Other / I'm not sure, plus an Open your provider's guide link. Under Records to add, copy everything in one go with Copy all or download it with Download zone file. When you've added the records, click I've added them.

Verify

Step 3, Verify, checks your records (Checking your records…, then Waiting for your records until they show up) and re-reads your DNS every 20 seconds. Check again checks right away. When the domain is verified you'll see "{domain} is verified" — click Done. You can close the window at any time: the domain's card keeps checking, and its Verify domain button brings the flow back at the records step.

Sending reputation is managed automatically, per email provider — see Email Deliverability.

Rules for adding a domain

Yaplet checks the name before it sets anything up. If it refuses a domain, a red Error notification tells you why. The rules:

  • Up to 3 domains a day. Your workspace can add at most 3 domains in any 24 hours, and deleting a domain does not give its slot back. Past the limit you'll see "You can add up to 3 domains a day. You can add more tomorrow." A domain that Yaplet refuses (an invalid or already-taken name, for example) does not use up one of the three.
  • A domain name belongs to one workspace. If another Yaplet workspace already has the domain, or already has a domain that yours would be a subdomain of (for example mail.example.com when another workspace has example.com), the add is refused with "This domain is already in use by another Yaplet workspace." If your own workspace already has the domain, you'll see "Domain already exists". If the name is already taken on the email-sending side and can't be added, you'll see "This domain is already in use and cannot be added. Contact support." — in that case, contact support.
  • Yaplet's own domains can't be added. That includes yaplet.com, yaplet.io and anything under them: "This domain belongs to Yaplet and cannot be added."
  • Enter just the domain name. Something that isn't a valid domain name — for example one with https:// in front — gets "Enter a valid domain name."
  • A paused domain stays paused. If sending from a domain was paused for a deliverability review (see Email Deliverability), deleting it and adding it again does not clear the pause. The pause is remembered by name, so the re-added domain starts out paused again, and so does a subdomain of it.

The Domain Page and the Setup Tab

Each domain you add gets its own card on the Custom Domains page: its name, a status pill (Verified, Verifying or Unverified), how many addresses it has and when it was added. An unverified domain shows a Verify domain button that reopens the guided flow at its records. Manage opens a card, and its Domain actions menu (the three dots) holds View send logs and Delete domain. An open card has three tabs: Setup, Deliverability and Emails.

The Setup tab is titled Domain authentication and walks you through the records and checks them for you. A few things to know about how it behaves:

  • It re-checks your DNS automatically every 20 seconds while anything is still pending, and again whenever you return to the page. A small line such as Checked 3 min ago says how fresh the status is. Just add the records and the page catches up on its own; the Verify domain button at the bottom of the list (it reads Re-check status once the domain is verified) forces an immediate check.
  • Each record shows a live status so you know exactly what's left.
  • Stuck? The Ask AI for help button hands your current setup state to Yaplet's AI assistant, which reads your live DNS and tells you precisely which records are still missing and where to add them.

Sending status

The pill on the domain's card tells you where it stands overall, and a banner at the top of the Setup tab says what to do next:

PillWhat it means
UnverifiedThe three DKIM records — the only required ones — aren't all in your DNS yet. The banner says Add the DNS records below at your provider.
VerifyingThe three DKIM records are detected (skipped optional records don't hold this up); Amazon is verifying — usually 5–60 minutes (occasionally longer). The banner says Records detected — Amazon is verifying your domain.
VerifiedDone. You can send from this domain.

Records, grouped by what they do

Instead of one flat table, the records form a checklist, one row per kind of record. Each row has a status icon, its name, a Required or Optional badge, a status line and a short description of what the record does — and, for optional ones, why they're optional. Show records (for example Show 3 records) opens the row's records as a small table; Hide records closes it. On the page, the first row that still needs work starts open; in the guided flow, every row that needs work does.

RowBadgeWhat it is
DKIMRequiredProves to inboxes that the email really came from you. Only the three DKIM CNAMEs are required: they alone verify the domain.
SPF & return pathOptionalThe SPF TXT lists Amazon (who sends the email for us) as allowed to send for your domain, and the MAIL FROM MX + TXT put your own domain on the bounce address. Amazon's own sender address already passes SPF checks, so these add extra trust with some inboxes — without them Amazon's fallback address works fine.
DMARCOptionalA TXT that tells inboxes what to do with mail that fails the checks above. Gmail and Yahoo expect one from anyone sending newsletters; if you already have your own DMARC record, it counts.
Google PostmasterOptionalA single google-site-verification TXT record. Gmail is the one major provider that never reports spam complaints back to senders; this record lets Google share how Gmail rates your domain, so Yaplet can watch your Gmail spam rate and protect the domain before trouble escalates. Sending works without it — add it to unlock Gmail health monitoring on the Deliverability tab. Keep it in your DNS permanently.
ReceivingOptionalA single inbound MX record that sends email addressed to your domain into your Yaplet inbox. Add it only if you want incoming email for your domain (like customer replies) to land in Yaplet; skip it if you only need to send — for example, newsletters. Don't add it if your domain already runs on Google Workspace or Microsoft 365, or it will reroute your existing mail. Only the addresses you added under Emailing get their mail into Yaplet — mail to any other address on the domain is dropped, and its sender gets no bounce.
Secure links (SSL)OptionalAn SSL-validation CNAME (and, if your domain blocks it, a CAA record). This lets Amazon issue a certificate so your tracking links can be branded. It works in parallel with sending, so you can add it at the same time.
Branded link trackingOptionalThe link. CNAME and a switch. Measures clicks through link.yourcompany.com instead of a shared address — see below.

The status line of a row reads Verified, Not found yet, of {total} found (some of its records are in DNS, some are not), Wrong value — check the record, Skipped — you keep your own (a record you deliberately leave out), or Off (link tracking switched off). While Amazon is still working, it reads Found — Amazon is verifying (usually 5–60 min) for DKIM, Issuing the certificate… for Secure links, or Turns on once the record is found for link tracking.

Per-record live status

Every record row shows the Type, the Host and the Value — each with a copy button (Copy host, Copy value) — plus, for MX records, the priority, and a status badge:

BadgeMeaning
Verified (green)Yaplet queried your DNS and the value matches.
Wrong value (red)A different value is set in DNS than the one shown — in practice an SPF record without include:amazonses.com (only one v=spf1 is allowed). Unrelated values at the same name never cause this.
Not found (gray)Nothing found yet. Add the record, or wait for it to propagate.
Don't add (amber)The record conflicts with your existing email setup — leave it out. Details below, under conflict detection.

If your domain already has its own DMARC record, the DMARC row shows Verified — any v=DMARC1 policy satisfies the requirement, and your own (often stricter) policy is better than Yaplet's permissive default.

Yaplet also detects your DNS provider from your nameservers and tailors the host hints — for example, telling Namecheap and GoDaddy users to enter only the host part (link, _dmarc, @) since those providers append the domain automatically. Copying a host shows a Host copied reminder of exactly what to type.

On Cloudflare, set every CNAME (the DKIM records and the link-tracking record) to DNS only — the gray cloud, not the orange one. A proxied CNAME makes Cloudflare answer with its own addresses, so DKIM and SSL validation fail. Yaplet detects Cloudflare and shows this reminder directly on each CNAME row until the record is found.

Under the checklist, DNS records not verifying? opens four quick fixes: don't double the domain in the Host, keep Cloudflare CNAMEs on DNS only, keep to a single SPF record, and give new records time to propagate.

Conflict detection

When you open the page, Yaplet scans your existing DNS for four common conflicts. Each conflict appears as a note on the record row it affects — and a record you shouldn't add is faded out with its copy buttons disabled and an amber Don't add badge, so it can't be added by accident:

  • Existing mail records — your domain already has MX records, so adding the (optional) inbound MX would reroute your existing mail to Yaplet. Skip it unless that's exactly what you want.
  • Existing SPF record — only one v=spf1 record may exist. Merge include:amazonses.com into your existing record rather than adding a second.
  • Mail subdomain in use — mail.yourcompany.com already belongs to another mail service (for example a CNAME to your mailbox provider), so the two MAIL FROM records can't be added there. Skip them: verification and sending work without them, and Amazon uses its own bounce address instead.
  • Existing DMARC record — keep yours; it already covers what Yaplet's default would add.

Export all records at once

Rather than copying each record by hand, click Export records on the left of the Setup tab to download every DNS record for this domain as a single zone file, then import it in one step at your DNS provider — for example in Cloudflare under DNS → Records → Import and Export. When the import finishes, come back and press Re-check status. (In the guided flow, Download zone file on the records step does the same.)

  • File format — when Yaplet sees that your domain is on Cloudflare, you can choose Cloudflare (tuned so the DKIM and link-tracking CNAMEs are pre-set to "DNS only", the gray cloud) or Standard BIND (the portable format any BIND-based host accepts). For every other provider the file is plain BIND.
  • Include inbound email (MX) record — off by default. Turn it on only if you want incoming mail for the domain to land in your Yaplet inbox; it reroutes the whole domain's mail, and mail to addresses you haven't added under Emailing is then dropped.
  • Conflicting records stay out — anything that conflicts with your existing setup is left commented out in the file so the import can't add it: a second SPF (merge include:amazonses.com into your existing record by hand afterward), the two mail. records when that subdomain is already in use, and a second DMARC when you have your own.
A zone file only helps providers that can import one — Cloudflare, or any BIND-based host. Some registrars, such as GoDaddy and Namecheap, can't import files; there, add the records with the per-row copy buttons instead.

Link tracking rewrites the links in your emails through a tracking subdomain (link.yourcompany.com) so Yaplet can measure clicks. It is the last row of the checklist, with a switch on it:

  • The switch is locked until your SSL certificate is issued (add the Secure links records first). Until then its tooltip reads "Available once your SSL certificate is issued" and the row says "Available once the Secure links certificate is issued — add that record first."
  • Once the certificate is issued, the link. CNAME appears in the row. You can flip the switch on before that record propagates — you'll see "Link tracking turned on — finishing setup", and tracking stays pending and activates automatically once the record resolves. Until then your links are sent untouched, so nothing breaks.
  • Turning it off reverts to plain, untracked links.

DNS records reference

All values are generated per domain and shown in your dashboard — always copy from there. This table is for reference; the Setup tab is the source of truth.

RowTypeName (host)ValuePriority
DKIMCNAME{token}._domainkey.yourcompany.com (×3){token}.dkim.amazonses.com—
SPF & return pathTXTyourcompany.comv=spf1 include:amazonses.com ~all—
DMARCTXT_dmarc.yourcompany.comv=DMARC1; p=none—
SPF & return pathMXmail.yourcompany.comfeedback-smtp.eu-central-1.amazonses.com10
SPF & return pathTXTmail.yourcompany.comv=spf1 include:amazonses.com ~all—
ReceivingMXyourcompany.cominbound-smtp.eu-central-1.amazonaws.com10
Google PostmasterTXTyourcompany.comgoogle-site-verification=… (shown in dashboard)—
Secure links (SSL)CNAME(certificate validation — shown in dashboard)(shown in dashboard)—
Branded link trackingCNAMElink.yourcompany.com (after cert issued)(shown in dashboard)—
Merging an existing SPF record: if you already have v=spf1 include:_spf.google.com ~all, change it to v=spf1 include:_spf.google.com include:amazonses.com ~all — don't add a second SPF record.

CAA records

CAA records control which certificate authorities may issue SSL certificates for your domain. If your domain already has a CAA record and it doesn't include Amazon, Amazon can't issue the certificate for your link. subdomain.

Yaplet detects this automatically. If a CAA record is blocking issuance, the Secure links row shows a "A CAA record is blocking the SSL certificate" alert, and Yaplet adds the exact record you need to that row:

TypeNameValue
CAAyourcompany.com0 issue "amazon.com"

If your domain has no CAA record at all, you don't need one — CAA only restricts issuance when it's present, and it only affects link tracking, not sending.

Verifying your domain

You don't have to run a manual check. After you add the records, Yaplet checks DNS for you (automatically every 20 seconds, and on demand with the Verify domain button — Re-check status once the domain is verified — or Check again in the guided flow). Once your DKIM records are detected — they're the only required ones — Amazon verifies the domain, usually within 5–60 minutes, and the card's pill turns from Verifying to Verified. You can close the page and come back; it re-checks when you return.

If verification previously failed

Amazon only searches your DNS for the DKIM records for 72 hours after a domain is added. If you added or fixed the records later than that, pressing Verify domain (or simply opening the Setup tab) automatically restarts Amazon's search using the same records. Nothing needs to be re-added; verification then completes within minutes to a few hours.

Optional records never block verification

A domain verifies on its three DKIM records alone. If optional records are still missing on an already-verified domain, Re-check status shows a gentle warning — "Verified — optional records not added" — and that's all: sending keeps working, and adding the remaining records only improves deliverability or unlocks extra features.

Adding Email Addresses

Once your domain is verified, create sending addresses on it from the Emails tab of the domain's card:

Click "Add email"

The Add Email window opens.

Enter the email prefix

Type the part before the @ in the Email Address field, which ends in @yourcompany.com — for example newsletter creates [email protected]. Prefixes must be 3–30 characters, lowercase letters, numbers, dots, hyphens, or underscores, and start and end with a letter or number. Because you own the domain, almost any prefix is allowed — support@, news@, admin@ and hello@ all work. Only six prefixes the mail system itself needs are reserved: no-reply, noreply, postmaster, abuse, mailer-daemon and bounce.

Select a widget

In the Widget list (Select a widget), choose which widget this address is linked to. Incoming emails to it route to that widget's inbox.

Click "Add"

The address is ready immediately — for inbox conversations and, for newsletter campaigns, as a sender option.

The Emails tab lists the domain's addresses with the widget each one is routed to and the date it was added. Each row has a three-dots menu with Delete.

Incoming Emails and Threading

If you added the optional Receiving record, custom-domain addresses behave just like yaplet.io addresses for inbound mail: incoming emails create chats in the inbox (assigned to the linked widget), threading is automatic via a unique Reply-To, and email-source chats auto-send agent messages as email with an "Email" badge.

Incoming mail on a custom domain also passes the same per-brand filters as yaplet.io addresses — the spam filter (on by default) and the optional AI answer filter. See the Filtering Incoming Email section of Yaplet.io Emails.

Email behavior is identical for yaplet.io and custom-domain addresses. The difference is only branding, deliverability, and newsletter access — not how conversations work.

Deliverability

Once you're sending, Yaplet manages your domain's sending reputation automatically — ramping volume up per email provider when bounce and complaint rates stay healthy, and pulling back when they don't. The Deliverability tab on each domain shows a per-provider health score so you can see exactly how you're landing.

Email Deliverability

Read the bounce/complaint health bands, the per-provider breakdown, and what to do if a provider goes "at risk".

Send Logs

To see send statistics for the last 7 days, open the Domain actions menu (the three dots on the domain's card) and choose View send logs. The Email sends for the last 7 days window breaks each period down into Sent and Failed, and by type — Campaigns, Automations (the mail your email automations send) and Other (inbox replies, notifications, and transactional mail) — so you can monitor what's going out.

Managing Domains

Switch domains by clicking a domain's card or its Manage button — each domain has its own setup, deliverability, and addresses.

Delete a domain from its Domain actions menu (Delete domain), and confirm. This is permanent and removes all of its email addresses; any in-flight or scheduled mail from it will fail. Make sure no active campaigns or email automations depend on its addresses first. Deleting a domain does not give back one of the day's three adds, and it does not clear a deliverability pause (see Rules for adding a domain).

Want a dedicated IP?

By default all Yaplet mail goes out from a shared, pre-warmed IP pool — the right choice for almost everyone. High-volume senders who want a sending reputation entirely their own can enable a dedicated IP for the domain. It is an account-wide add-on, so it sits in its own Dedicated IP panel below your domain cards rather than inside one domain.

© 2026 Yaplet. All rights reserved.