Opens in a new tab

include:send.aweber.com — AWeber’s SPF include, which AWeber says you do not need

include:send.aweber.com lists AWeber’s sending servers. AWeber’s own answer to whether you need it is in the title of its help article: “Do I need to update my domain’s SPF record? The answer is No.” Its mail carries AWeber’s return-path, which is what SPF checks; DKIM is what authenticates your domain.

v=spf1 mx include:send.aweber.com ~all
Belongs toAWeber email marketing
Needed on your domain?No — SPF checks a different domain for its mail, not this record on yours

What it costs, and is it in your record?

We measure include:send.aweber.com as the page opens. Enter a domain: we read its SPF record, follow every include and say whether AWeber’s is there and what it costs.

What it covers

AWeber email marketing.

Do you need it?

No. “An SPF record is not required or needed for improving deliverability or guarding against spoofing, when sending from AWeber … The SPF domain needs to align with the domain found in the return-path header which is normally a domain owned by the ESP.”

“If you still want to add an SPF record for AWeber it will likely be ignored by mailbox providers and will not hurt your deliverability.” It does still cost a lookup.

Common mistakes

  • Publishing a second SPF record for AWeber — “you should only publish one SPF (TXT) record”.

Sources

Checked on 26 September 2026 against these official sources:

Stay under 10 lookups without dropping a sender

Let us host your SPF record: you publish one include line, we flatten every service in it to their addresses and refresh it hourly, so however many there are they fit in a few lookups — and we tell you when a service changes its addresses. On the Personal plan and up.

Create a free account