1. SPF Configuration for Iterable

SPF authorizes Iterable's sending infrastructure to send emails on your behalf. Iterable uses specific IP ranges and includes that must be properly configured in your DNS.

2. DKIM Configuration for Iterable

DKIM provides cryptographic verification of email authenticity and message integrity. Iterable supports comprehensive DKIM implementation with custom selectors and advanced configuration options.

3. DMARC Configuration for Iterable

DMARC coordinates SPF and DKIM authentication results and provides comprehensive reporting on email authentication performance.

Multi-Subdomain Architecture with Iterable

For enterprises using multiple subdomains with Iterable:

SPF Alignment Failures

Symptoms: DMARC reports show SPF alignment = fail despite valid SPF check

DKIM Signature Verification Failures

Symptoms: Emails failing DKIM verification with "bad signature" or "signature missing" errors

How long does DNS propagation typically take for Iterable configuration changes?

A: DNS changes usually propagate within 5-60 minutes, but can take up to 48 hours depending on TTL settings and DNS provider caching policies. We recommend testing after 1 hour and monitoring for 24 hours.

Can I use the same DKIM key across multiple domains in Iterable?

A: While technically possible, it's not recommended for security best practices. Each domain should have its own unique DKIM key pair to maintain security isolation and simplify troubleshooting.