Email senders
AWeber DMARC setup: DKIM, SPF and alignment
How AWeber signs your mail with DKIM, why it says SPF is not needed, and the DMARC record mistakes that catch AWeber customers.
SPF include for AWeber
include:send.aweber.com
AWeber does not require this include. If you use it, add it to the SPF record you already have: a domain must publish only one.
- DNS lookups it uses
- 1 of 10
- Needed in your SPF record
- No
- Last checked in DNS
- 2026-11-11
DKIM for AWeber
- Selectors
- aweber_key_a aweber_key_b aweber_key_c
- How to enable it
- Three CNAME records on your domain, aweber_key_a._domainkey, aweber_key_b._domainkey and aweber_key_c._domainkey, each pointing to the matching host under send.aweber.com. Connect Domain adds them for you on supported DNS providers.
AWeber signs with your domain
Envelope-from and SPF alignment
SPF counts for DMARC only when this domain matches the domain in your From address. If it is AWeber’s own domain, SPF can pass without aligning, and DMARC then depends on an aligned DKIM signature.
- Envelope-from (Return-Path)
- AWeber does not document this.
Sending ranges of AWeber
Use these to recognize AWeber in your reports. They change over time, so do not copy them into your SPF record.
- 216.185.208.0/22
- 204.194.222.0/23
Updated 2026-11-15
Does your domain authorize AWeber?
Enter your domain. The SPF Checker reads your record and names the senders it authorizes.
AWeber documentation
- AWeber: Authenticate Your Email Domain with DKIM and DMARC
- checked 2026-11-09
- AWeber: Do I need to update my domain's SPF record?
- checked 2026-11-09
- AWeber: What is DMARC and how does it affect sending from AWeber?
- checked 2026-11-09
- AWeber: How to comply with Google & Yahoo's new sending requirements
- checked 2026-11-09
How it authenticates
AWeber DMARC setup relies on DKIM (DomainKeys Identified Mail), the signature that ties a message to your domain. You connect the domain under My Account > Domains and Addresses. On more than 40 DNS providers, the Connect Domain option adds the records for you. Elsewhere you publish three CNAME records under _domainkey and one TXT record at _dmarc.
Each CNAME points to a key that AWeber hosts. The records live on your domain, so the signature can pass DMARC alignment.
SPF (Sender Policy Framework) authorizes sending servers. For DMARC, the return-path domain must pass SPF and align with From. AWeber says this domain normally belongs to the email provider and requires no SPF record. Its cited articles give no exact return-path domain, so rely on DKIM.
What to watch for
Adding include:send.aweber.com will not fix a DMARC failure. AWeber says mailbox providers will likely ignore it. If you add it anyway, keep a single SPF record on the domain.
Keep one _dmarc record too. AWeber flags extras with 2 or more DMARC records found. Receivers discard all DMARC records at that name; a parent-domain policy may still apply. If your domain already has a policy, keep that record and check it after you connect. The value must not be wrapped in quotation marks.
AWeber's suggested record sends aggregate reports to dmarc@fbl.optin.com. To receive them yourself, add your address after a comma, as in rua=mailto:dmarc@fbl.optin.com,mailto:dmarc@example.com. Then confirm that each record shows Installed behind the gear icon.
A From address at Yahoo or a similar provider gets rewritten for small senders, to a form like you=yahoo.com@send.aweber.com. Large senders must use their own domain.
AWeber advises against quarantine or reject on a first DMARC record. Start at p=none and read your reports before you tighten the policy.
Check each selector with the DKIM checker. A broadcast returns to Draft if authentication has lapsed when you send it.