Charchy Senddocs

Domains and DNS

Verify your sending domain with three DKIM records and a DMARC record — or one click with Cloudflare — and avoid the two classic DNS mistakes.

Every email leaves from your own domain, DKIM-signed with your domain's key. Receiving servers check that signature against your DNS.

Add a domain

  1. In the dashboard, open Domains and add the domain you send from, e.g. daringaming.com (or a subdomain such as mail.daringaming.com).
  2. Publish the records we show you:
    • Three CNAME records for DKIM, named like <token>._domainkey.daringaming.com.
    • A DMARC TXT record at _dmarc.daringaming.com, if you don't have one.
  3. The page checks your DNS live and turns Verified when it sees them — usually within minutes, at most a few hours.

Once verified, send from any address on the domain (orders@, no-reply@, support@) without confirming each one.

Add with Cloudflare or Vercel

If your DNS is on Cloudflare, press Add with Cloudflare, sign in, and approve the records. Cloudflare creates them for you. When the button shows Add with Vercel for a domain on Vercel's nameservers, it does the same there.

Step by step for your DNS provider

Cloudflare · Hostinger · GoDaddy · Namecheap · Route 53 · Vercel

The DMARC record

DMARC tells receiving servers what to do with mail that fails its checks; Gmail and Yahoo expect one from every sender. Start with a report-only policy:

_dmarc.daringaming.com   TXT   "v=DMARC1; p=none; rua=mailto:dmarc@daringaming.com"

After a few weeks of good delivery, move to p=quarantine, then p=reject (why).

The two classic DNS mistakes

1. The domain written twice

Many DNS panels append your domain to every name. Paste the full name and the record ends up at

abc123._domainkey.daringaming.com.daringaming.com

and never verifies. Enter only the part before your domain: abc123._domainkey.

2. The Cloudflare proxy on a DKIM record

A Proxied (orange cloud) CNAME on Cloudflare hides its target, so DKIM can't be checked. Set all three DKIM records to DNS only (grey cloud). Add with Cloudflare does this for you.

Keys and domains

  • A live key can be locked to one domain at creation; sending from another domain gets 403 restricted_api_key.
  • A from on a domain not verified in your workspace gets 403 domain_not_verified, or 403 sender_not_allowed if your workspace can't use the domain.
  • Test keys can use any domain.
  • Up to 10 domains per workspace.

If a domain stops verifying

We re-check every verified domain daily. If its DKIM records are gone (DNS edited, domain moved to another provider) at two checks a few hours apart — one DNS hiccup changes nothing — it becomes unverified:

  • new emails from it get 403 domain_not_verified;
  • scheduled emails from it fail when their time comes, are refunded, and fire email.failed;
  • queued emails from it fail the same way;
  • your owners and admins get an email and a notification, and you get a domain.failed webhook.

Put the same records back: we check again every few hours and turn the domain back on by ourselves, with a domain.verified webhook. Check records on the Domains page brings that check forward. If it hasn't recovered within a day of the records being back, start verification again for new records.

On this page