Essay · 12 min read

Per-domain DKIM, SPF & DMARC in a multi-domain inbox.

Why shared DKIM keys and envelope senders leak secondary domains in email headers, and how per-domain 2048-bit DKIM signing and DMARC alignment prevent it.

In the modern email ecosystem, deliverability is no longer a matter of avoiding spam trigger words or keeping message sizes small. Major receiving mailbox providers—including Google, Microsoft, Apple, Yahoo, and enterprise secure email gateways—evaluate incoming mail using automated cryptographic authentication algorithms. If your messages fail cryptographic verification, they are dropped into Spam or silently rejected before reaching human eyes.

For single-operator founders and portfolio entrepreneurs who manage multiple business domains from a single inbox, maintaining perfect cryptographic authentication is notoriously difficult. Many multi-domain email services cut architectural corners by sharing SPF includes, envelope senders, and DKIM signing keys across all your domains. This compromises sender privacy, exposes your secondary business brands in raw message headers, and triggers catastrophic DMARC authentication failures.

This technical guide explains how receiving mail servers inspect message headers, why shared signing infrastructure damages deliverability, and how per-domain 2048-bit DKIM signing guarantees pristine brand isolation and DMARC alignment across all your business entities.

Anatomy of an email header: How receiving servers inspect your mail.

When an email arrives at a receiving server, the receiving MTA generates an Authentication-Results header per RFC 8601. This header records the server's cryptographic verdicts before handing the message over to spam scoring filters:

Header inspection behavior and identity leakage across major multi-domain email configurations
Provider ConfigurationDKIM-Signature (d=)Return-Path (SPF Envelope)Received & Authentication-ResultsCross-Domain Header Privacy
Folio Multi-Domain Inboxd=sendingdomain.com (Dedicated 2048-bit)mailfrom.sendingdomain.comClean per-domain hop; spf=pass, dkim=pass, dmarc=pass100% Isolated; zero cross-brand leakage
Google Workspace (Secondary Domain)d=secondarydomain.commail.workspace.com relayGoogle SMTP hop; dmarc=pass via DKIM alignmentClean within tenant; requires separate licenses for separate entities
Google Workspace (Alias Domain)d=primarytenant.com (Shared)primarytenant.comReveals primary tenant in Received/Sender; DMARC fails or relaxesLeaks primary company name in raw headers
Fastmail (Multiple Domains)d=sendingdomain.com or messagingengine.commessagingengine.com relayFastmail MTA hop; dmarc=pass via custom DKIM selectorClean if custom DKIM is configured per domain
Migadu (Multiple Domains)d=sendingdomain.com (Dedicated)migadu.com bounce hostMigadu SMTP hop; dmarc=pass via DKIM & SPF alignmentClean if per-domain DKIM CNAMEs are published
Purelymail (Multiple Domains)d=sendingdomain.compurelymail.com bounce hostPurelymail MTA hop; dmarc=pass via DKIM alignmentClean if user publishes per-domain keys
Zoho Mail (Multiple Domains)d=sendingdomain.comzohomail.com relayZoho SMTP hop; dmarc=pass when domain key is verifiedClean if separate DKIM keys are enabled per domain
Basic Registrar ForwardingNo signature or third-party DKIMforwarder.net bounce hostBroken SPF on forwarder hop; dmarc=fail without ARCSevere leakage of forwarding provider and personal address

Scroll to see every column →

The three pillars of multi-domain authentication.

To achieve 100% deliverability across multiple business brands, three distinct cryptographic standards must be configured independently for every domain:

  • ·1. Sender Policy Framework (RFC 7208 SPF): SPF specifies which IP addresses and server hostnames are authorized to dispatch mail on behalf of your domain. Each domain must carry a concise TXT record at root (e.g., v=spf1 include:_spf.folioinbox.com ~all). Crucially, SPF enforces a strict ceiling of 10 DNS lookups; overloading your SPF record with third-party marketing tools causes a PermError and invalidates your entire policy.
  • ·2. DomainKeys Identified Mail (RFC 6376 DKIM): DKIM attaches a cryptographic digital signature to every outbound email. Your mail host holds a private key and uses it to generate a hash of the message headers and body. You publish the matching public key in your DNS at a designated selector name (e.g. folio1._domainkey.yourdomain.com). The receiving server uses your public key to verify that the message originated from your authorized mail server and was not tampered with in transit.
  • ·3. DMARC Alignment (RFC 7489): DMARC ties SPF and DKIM directly to the visible From: address displayed to the human reader. For DMARC to pass, the domain in the From header must match the authenticated domain in either SPF or the DKIM d= tag. In a multi-domain setup, this alignment is where poorly architected alias systems fail.

Worked header example: Clean per-domain verification.

The difference between clean per-domain signing and shared infrastructure is immediately apparent when viewing raw email headers. Below is an ILLUSTRATIVE header representation (using RFC 2606 reserved .example and .test domains) showing clean per-domain authentication in Folio:

From: Alex <alex@consulting.example>
To: Client <client@enterprise.test>
Subject: Q4 Advisory Review
Return-Path: <bounce-1234@mail.consulting.example>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=consulting.example; s=folio1; h=from:to:subject:date:message-id; bh=47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=; b=kL9...
Authentication-Results: mx.enterprise.test;
    spf=pass (enterprise.test: domain of consulting.example designates 198.51.100.25 as permitted sender) smtp.mailfrom=consulting.example;
    dkim=pass (2048-bit key) header.d=consulting.example header.s=folio1;
    dmarc=pass (p=quarantine sp=quarantine) header.from=consulting.example

Notice that in this header block, every single authentication identity aligns with consulting.example: the From address, the Return-Path, the DKIM signing domain (d=consulting.example), and the DMARC verdict. Even if Alex manages four other companies in the exact same Folio inbox, there is zero trace of those other companies in this header block. The enterprise client receives a pristine, verifiable corporate communication.

Interpreting DMARC aggregate XML reports (RUA).

When you publish a DMARC record carrying an rua=mailto:dmarc@yourdomain.com tag per RFC 7489, major receiving mail servers (Google, Microsoft, Yahoo, Comcast) send automated daily XML feedback reports. These reports summarize every single server that attempted to send mail using your domain name.

In a properly configured multi-domain inbox, inspecting your aggregate reports will show 100% passing results for your host's IP addresses under both SPF and DKIM. If you see unauthorized IPs attempting delivery with failing authentication, the reports give you immediate cryptographic proof of spoofing or phishing campaigns targeting your brand, allowing you to tighten your DMARC policy from p=none to p=quarantine or p=reject with absolute confidence.

How Folio automates per-domain authentication.

Configuring 2048-bit DKIM keys, SPF strings, and DMARC records for five or ten different domains is tedious and error-prone when done by hand. Folio automates this entire pipeline:

  1. 01Automatic key generation: The moment you add a custom domain to Folio, the platform provisions a dedicated 2048-bit RSA key pair specifically for that domain.
  2. 02One-click Domain Connect: If your domain is registered at Cloudflare or GoDaddy, Folio utilizes the Domain Connect protocol to automatically publish your MX, SPF, and DKIM records into your registrar's DNS zone with a single confirmation click.
  3. 03Automated identity matching: Inbound messages are routed to their designated domain identity. When you reply, Folio automatically attaches the correct signature, binds the From address, and queues the message for outbound signing using that domain's private DKIM key.

Cryptographic breakdown: Anatomy of a 2048-bit DKIM signature.

To understand why per-domain DKIM is the gold standard of deliverability, we must examine the internal structure of the DKIM-Signature header generated during outbound message dispatch per RFC 6376. A standard signature contains several critical cryptographic tags:

  • ·v=1: The DKIM protocol specification version.
  • ·a=rsa-sha256: The cryptographic algorithm pair: an RSA private/public key cipher combined with a SHA-256 secure hash digest.
  • ·d=example.com: The signing domain identity (SDID). This is the exact domain that receiving mail servers inspect when calculating DMARC alignment. If d= does not match the visible From address, DMARC alignment fails.
  • ·s=selector1: The selector name. When a receiving server verifies the signature, it queries DNS for selector1._domainkey.example.com to retrieve your public key.
  • ·c=relaxed/relaxed: The canonicalization algorithm. Relaxed canonicalization prevents harmless whitespace or header reformatting by intermediate mail relays from breaking the signature.
  • ·bh=...: The base64-encoded body hash digest, ensuring the email body was not altered in transit.
  • ·b=...: The digital cryptographic signature of the header block, generated using your mail host's private RSA key.

The 1024-bit vs. 2048-bit security bar.

In the early days of DKIM adoption, 1024-bit RSA keys were the standard due to DNS UDP packet size limits (the 512-byte DNS ceiling). However, modern computational advances have rendered 1024-bit RSA keys vulnerable to cloud-scale factorization attacks. Modern security standards enforced by Google, Microsoft, and the US National Institute of Standards and Technology (NIST) mandate 2048-bit RSA keys for all production email signing.

Publishing a 2048-bit key in DNS requires modern EDNS0 (Extension Mechanisms for DNS) support because a 2048-bit public key string is approximately 392 characters long. Folio automatically provisions full 2048-bit RSA key pairs for every custom domain you connect, ensuring that your cryptographic posture satisfies the highest enterprise security standards.

The 10-lookup SPF limit and multi-domain include traps.

Another frequent deliverability failure in multi-domain portfolios involves the Sender Policy Framework (RFC 7208 SPF) 10-lookup limit. When an external mail server evaluates an SPF record, it must resolve every include:, a, mx, ptr, and redirect modifier using recursive DNS queries.

RFC 7208 strictly limits the number of recursive DNS lookups to 10. If resolving your domain's SPF record requires 11 or more lookups, the receiving server aborts evaluation and returns a PermError (Permanent Error). When an SPF PermError occurs, receiving servers treat your domain as having no valid SPF policy, and DMARC evaluation fails immediately.

Solo founders who add multiple SaaS marketing tools, CRM trackers, and transactional gateways to a single SPF record frequently breach the 10-lookup limit without realizing it. Folio's SPF include (include:_spf.folioinbox.com) consumes exactly one DNS lookup, leaving you ample headroom for necessary transactional tools like Stripe or Postmark.

Strict vs. relaxed DMARC alignment across multiple brands.

Under RFC 7489 (DMARC), domains can operate in either relaxed or strict alignment mode. Under relaxed mode (the default), an organizational domain match is accepted (for example, mail from news.example.com signed by d=example.com aligns). Under strict mode (adkim=s and aspf=s), the domain names must match byte-for-byte.

If you operate completely distinct brands on separate root domains (e.g., brandA.com and brandB.com), even relaxed alignment will fail if your email host uses shared signing. Clean per-domain DKIM signing ensures that every message passes strict DMARC alignment automatically, giving you the highest possible sender reputation and inbox delivery rates.

To test your current domains for SPF, DKIM, and DMARC compliance, run our free domain health checker and email deliverability audit. Explore our complete email authentication hub, read our detailed guide on email setup for multiple LLCs, and review transparent flat-rate pricing on Folio's pricing page.

Questions readers ask

What is the difference between shared DKIM and per-domain DKIM?

Shared DKIM signs outgoing messages from secondary domains using the cryptographic key and domain tag of a primary account (d=primary.com). Per-domain DKIM generates and maintains unique 2048-bit private keys for each domain, signing as d=secondary.com.

Why does DMARC fail when sending from an email alias?

DMARC requires identifier alignment between the visible From domain and either the SPF envelope domain or the DKIM signing domain (d=). If your mail server signs an alias email with your primary account's domain, the domains do not match, causing DMARC to fail.

Can receiving mail servers see my other business domains in email headers?

Yes, if your email host uses shared envelope senders, Return-Path addresses, or unaligned DKIM selectors. Dedicated multi-domain platforms like Folio isolate all header metadata, ensuring that no cross-domain identifiers leak in raw headers.

What key length is recommended for DKIM signatures in 2026?

The current industry standard enforced by major email providers is 2048-bit RSA keys. Legacy 1024-bit keys are increasingly flagged by strict security gateways as deprecated and cryptographically weak.

Sources & further reading

§ Google Search

Make Folio a preferred source.

If you read Folio often, add it as a preferred source. Google can then mark our writing as preferred in Top Stories, AI Overviews, and AI Mode for you.

Change or remove it any time in Google’s source preferences.