AWeber email authentication

One of the oldest autoresponder platforms still in wide use.

SPF record

Add AWeber to your domain's SPF record with this include:

include:aweber.com

A complete record for a domain sending only through AWeber:

v=spf1 include:aweber.com ~all

What it costs you

6 of your 10 DNS lookups. The include: itself costs one, and AWeber's record chains to 5 more. Behind it are 62 IP ranges.

At 6 lookups this is an expensive include. If your record is near the limit, this is one of the first places to look — see too many DNS lookups.

Live record

This is what aweber.com published when this page was generated:

v=spf1 ip4:204.194.222.0/23 ip4:216.185.208.0/22 ip4:44.216.102.174 ip4:52.4.24.201 include:mail.zendesk.com include:sendgrid.net include:_spf.google.com include:stspg-customer.com ~all

DKIM

Enable DKIM inside AWeber and publish the selector record it generates. DKIM matters more than SPF for deliverability, because a DKIM signature survives forwarding while SPF does not — see how selectors work.

DMARC

Neither SPF nor DKIM protects the address your recipients actually see until DMARC ties them to it. Once AWeber is authenticating, publish a DMARC record — start at p=none with a reporting address and tighten from there.

Generate a DMARC record →

Check it worked

DNS changes take minutes to hours to propagate. Once published, run the domain through the checker — it resolves the full include chain and reports the real lookup count.

Official documentation

AWeber setup docs →