Dual-DKIM Signing: 2048-bit RSA + RFC 8463 Ed25519 Signatures
SadaSend signs every outbound email with both legacy 2048-bit RSA and ultra-fast Ed25519 elliptic curve cryptography. Universal compatibility for older corporate servers, instant sub-1ms cryptographic verification for modern receivers.
Live MIME Signature Inspector
Inspect how receiving mail transfers evaluate concurrent cryptographic headers.
Modern receivers evaluate Ed25519 in sub-1ms.
RFC 5966 compliant; prevents UDP truncation across DNS port 53.
Zero dropoffs: legacy servers read RSA, modern receivers read Ed25519.
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=yourdomain.com; s=sada-ed; t=1763371200; h=from:to:subject:date:message-id:content-type; bh=2jmj7l5rSw0yVb/vlWAYkK/YBwk=; b=k9xL2pQ8m...Ed25519SignatureSub1ms...== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yourdomain.com; s=sada1; t=1763371200; h=from:to:subject:date:message-id:content-type; bh=2jmj7l5rSw0yVb/vlWAYkK/YBwk=; b=AbC8910...RSA2048SignatureUniversalFallback...==
Cryptographic Architecture & Protocol Standards
Engineered from first principles to satisfy RFC 6376, RFC 8463, and modern zero-trust email delivery.
RFC 8463 Ed25519 Elliptic Curve Signatures
Modern Mail Transfer Agents (Gmail, Fastmail, Apple Mail) evaluate Ed25519 signatures first. Small 44-character public keys fit effortlessly in compact DNS TXT records without UDP packet fragmentation.
2048-bit RSA Universal Compatibility
Legacy enterprise on-premise mail servers (older Microsoft Exchange and legacy spam appliances) lack Ed25519 support. SadaSend automatically signs with RSA 2048-bit so zero emails fail verification.
Automated Dual DNS Selector Provisioning
When you add your custom sending domain, SadaSend provisions two canonical selectors: sada1 (RSA 2048) and sada1e (Ed25519). Our automated DNS checker continuously verifies both records.
High-Throughput In-Memory Signing Engine
Ed25519 cryptographic signing executes in under 0.8 milliseconds, eliminating queue bottlenecks during high-frequency API burst sends and autonomous agent loops.
Dual-DKIM vs Legacy Email Providers
Why legacy infrastructure providers still leave your domain vulnerable to RSA DNS truncation.
| Provider | RFC 8463 Ed25519 | RSA Key Length | Dual-Signature Header | DNS Packet Size |
|---|---|---|---|---|
| SadaSend | Native (RFC 8463) | 2048-bit High-Grade | Automatic Dual-Header | Optimal (< 300 bytes) |
| SendGrid | Unsupported (RSA only) | Legacy 1024 / 2048-bit | Single Signature Only | Heavy (~ 450 bytes) |
| Postmark | Unsupported (RSA only) | 2048-bit RSA | Single Signature Only | Heavy (~ 450 bytes) |
| Mailgun | Unsupported (RSA only) | 1024 or 2048-bit | Single Signature Only | Heavy (~ 450 bytes) |
Zero-Config Dual-DKIM Code Examples
Dual-DKIM signing happens automatically at the API edge. Zero manual cryptography libraries required.
Dispatch emails with automatic dual-DKIM cryptographic signing via the official TypeScript SDK.
import { SadaSend } from 'sadasend';
const sadasend = new SadaSend({
apiKey: process.env.SADASEND_API_KEY!,
});
// Outbound message automatically signs with both:
// 1. DKIM-Signature: v=1; a=ed25519-sha256; s=sada1e; d=yourdomain.com
// 2. DKIM-Signature: v=1; a=rsa-sha256; s=sada1; d=yourdomain.com
const response = await sadasend.emails.send({
from: 'Security <alerts@yourdomain.com>',
to: 'developer@example.com',
subject: 'Production Deployment Verified',
html: '<p>Dual-DKIM cryptographic verification passed.</p>',
});
console.log('Dispatched message ID:', response.id);Frequently Asked Questions
Technical answers regarding RFC 8463, DNS record configurations, and cryptographic key rotation.
Upgrade Your Sending Domain to Dual-DKIM
Sign with modern RFC 8463 Ed25519 and universal RSA-2048 simultaneously. Free tier includes 6,000 emails every month.