Skip to Content
Docs
Guides

Sending domains

Verify your custom domain with 1-click Domain Connect, Cloudflare auto-publish, zone file export, or manual DNS records.

Every email sent through emitd must originate from an authenticated, verified sending domain. Until verified, dispatch attempts from unverified domains fail with from_domain_not_verified to prevent domain spoofing and preserve global inbox placement.

Manage your domains in the Console under Domains.


Setup methods

emitd offers four configuration paths — from fully automated one-click registrar flows to manual zone entry:

The Add sending domain panel in the emitd console

MethodSupported ProvidersHow it worksCredentials required
Domain ConnectGoDaddy, IONOS, 1&1, Squarespace, WordPress.comClick Set up in one click. You are redirected to your registrar to approve the records.None — authenticated directly at your registrar
Cloudflare Auto-PublishCloudflareEnter a scoped Zone.DNS:Edit token. emitd creates and merges records automatically.Ephemeral API token (never stored)
Zone File ExportAWS Route 53, Google Cloud DNS, Azure DNSDownload an RFC 1035 .zone file containing only missing records and import it.None
Manual ConfigurationAny DNS registrar or hostCopy each record individually with one-click copy buttons in the console.None

1. One-click setup with Domain Connect

emitd supports the open Domain Connect standard (RFC-backed specification co-developed by GoDaddy, Microsoft, and major registrars).

The official Emitd service template (emitd.com.mail.json) is approved and merged in the official Domain Connect Templates repository.

How it works:

1. Add Domain (Console) ➔ 2. DoH Discovery (_domainconnect.<domain>) 
➔ 3. Signed Sync Apply URL ➔ 4. Registrar Consent Dialog 
➔ 5. Records Applied ➔ 6. Verification Complete (< 2 mins)
  1. Open Domains in the Console and click Add domain.
  2. emitd queries _domainconnect.<yourdomain.com> via DNS-over-HTTPS (or nameserver fingerprinting for GoDaddy) to discover your registrar's Domain Connect sync endpoint.
  3. If supported, a Set up in one click (or Configure with Domain Connect) button appears.
  4. Clicking the button securely redirects you to your registrar's authentication portal.
  5. Review the pre-populated DNS records (SPF, DKIM, custom Return-Path, and DMARC) and click Authorize.
  6. The registrar automatically writes the records to your DNS zone and redirects you back to https://app.emitd.com/domains/detail.
  7. emitd verifies the live records via DoH and flips your domain status to Active within 2 minutes.

The Sending domain DNS records panel in the emitd console: live status, 1-click Domain Connect and Cloudflare auto-configure actions, and record values

Cryptographically signed requests (RS256)

emitd signs synchronous Domain Connect apply requests with an RSA-2048 private key (RS256). Your DNS provider verifies the signature against Emitd's public key published in DNS at _dcpubkeyv1.emitd.com. No account passwords, API tokens, or login credentials are ever exposed.

Official template record specifications:

The merged emitd.com.mail.json template configures the following records:

Record TypeHostContent / RuleBehavior & Safety
SPFM@ (apex)include:amazonses.comSPF-Merge: Merges into existing v=spf1 records (e.g. Google Workspace or Microsoft 365) without creating duplicate records or causing RFC 7208 PermErrors.
TXT_dmarcv=DMARC1; p=none; adkim=s; aspf=rDMARC: Configures baseline DMARC monitoring. Respects existing DMARC policies via txtConflictMatchingPrefix: "v=DMARC1".
TXT%selector%._domainkeyv=DKIM1; k=rsa; p=%domainKey%BYODKIM: Publishes your domain's dedicated 2048-bit RSA public key under the relay selector.
MXmail (%spfDomain%)10 feedback-smtp.%region%.amazonses.comCustom Return-Path: Routes bounce and delivery notices to your custom subdomain for strict SPF alignment.
SPFMmail (%spfDomain%)include:amazonses.comSubdomain SPF: Authorizes SES for the custom Return-Path envelope sender.

2. Cloudflare auto-publish

If your domain's nameservers are hosted on Cloudflare:

  1. In the domain details screen, click Auto configure.
  2. Provide a Cloudflare API token scoped with Zone.DNS:Edit permissions for your specific zone.
  3. emitd connects to the Cloudflare API, safely creates the DKIM, Return-Path MX, and DMARC records, and intelligently merges include:amazonses.com into your existing root SPF TXT record.
  4. All email records are created as DNS-only (grey cloud) to ensure mail servers can resolve MX and TXT records directly without HTTP proxying.
  5. The API token is used in-flight and immediately discarded — it is never stored in any database or disk log.

3. Manual DNS configuration

If your registrar does not support Domain Connect or API tokens, add the following five records directly in your provider's DNS management portal:

TypeHost / NameValue / DestinationTTLPurpose
TXT@ (or root domain)v=spf1 include:amazonses.com ~all3600SPF: Authorizes AWS SES to dispatch emails for your root domain.
TXTrelay._domainkeyv=DKIM1; k=rsa; p=<your-2048-bit-public-key>3600DKIM: 2048-bit cryptographic key verifying email integrity.
MXmail (or mail.<domain>)feedback-smtp.<region>.amazonses.com (Priority: 10)3600Custom Return-Path: Aligns the envelope MAIL FROM address with your brand domain.
TXTmail (or mail.<domain>)v=spf1 include:amazonses.com ~all3600Return-Path SPF: Authorizes SES on the mail bounce subdomain.
TXT_dmarc (or _dmarc.<domain>)v=DMARC1; p=none; adkim=s; aspf=r3600DMARC Policy: Informs receivers to monitor alignment without rejecting legitimate mail.

Critical: Never create multiple root SPF records

According to RFC 7208 §3.2, a domain MUST NOT publish more than one SPF TXT record. Publishing multiple v=spf1 records causes receiving mail servers (Gmail, Yahoo, Outlook) to return a permanent PermError, causing your emails to fail SPF checks or land in Spam.

If you already have an SPF record for Google Workspace or Microsoft 365, merge include:amazonses.com inside your single record:

Correct merged SPF record
v=spf1 include:_spf.google.com include:amazonses.com ~all

Understanding emitd's email authentication architecture

emitd is architected for modern email deliverability standards enforced by Google and Yahoo:

  • Single 2048-bit BYODKIM TXT instead of 3 CNAMEs: Legacy email services force you to configure three separate CNAME delegations pointing to their third-party servers. emitd generates a dedicated 2048-bit RSA keypair unique to your domain, provisions it directly to AWS SES, and requires only a single TXT record at relay._domainkey.
  • Dedicated Custom Return-Path (MAIL FROM): Default AWS SES setups use generic amazonses.com envelope bounce addresses, causing SPF alignment to fail under strict DMARC checks. emitd configures mail.<yourdomain.com> as your dedicated Return-Path so both the header From and envelope sender match your brand domain.
  • DMARC Relaxed Alignment (aspf=r): Because user-facing emails originate from <yourdomain.com> while bounce notifications route through mail.<yourdomain.com>, DMARC relaxed SPF alignment (aspf=r) ensures that your subdomain passes DMARC checks 100% of the time.

RFC 1035 zone file export & bulk import

To configure your DNS in seconds without copy-pasting records one by one, click Export on the domain details screen:

The Export DNS records panel: download a zone file or a CSV, with a note on Cloudflare's proxy setting

  • Zone file (RFC 1035): Standard BIND format supported by major cloud DNS providers.
  • CSV: Tabular export for manual reference.

emitd checks your live DNS before generating the file, so the export contains only the records still missing:

  • Already published records appear as commented-out lines to prevent duplicate conflicts.
  • Records requiring modification (such as an existing SPF record needing include:amazonses.com appended) are highlighted with the exact merged string to paste.
ProviderHow to import the RFC 1035 zone file
CloudflareNavigate to DNS → Records → Import and Export, select the file. Important: Untick "Proxy imported DNS records" — DKIM and MX records must remain DNS-only (grey cloud).
AWS Route 53Navigate to Hosted zones → select your zone → Import zone file, paste file contents.
GoDaddyNavigate to Domain Portfolio → select domain → DNS → Actions → Import Zone File, click Apply Zone File.
Google Cloud DNSRun gcloud dns record-sets import <domain>.zone --zone=<zone-name> --zone-file-format
Azure DNSIn the portal, navigate to DNS zone → Import zone file, or run az network dns zone import -g <group> -n <zone> -f <domain>.zone

Domain Connect FAQs & troubleshooting


Domain-scoped API keys

To enforce least-privilege security across multi-tenant applications or distinct microservices, you can pin API keys to a specific sending domain:

  1. When creating an API key in the Console, select Sending access.
  2. Restrict the key to your verified domain (e.g., billing.yourdomain.com).
  3. Any API requests using this key with a from address outside this domain will be rejected with from_domain_not_verified.

Next steps

On this page