include:spf.messagelabs.com authorises the delivery servers of Broadcom’s Email Security.cloud — Symantec’s service, formerly MessageLabs. Broadcom recommends it even for customers whose outbound mail does not go through the service: mail between two Email Security.cloud customers is checked against the delivery server’s address.
v=spf1 include:spf.messagelabs.com ~all
| Belongs to | Broadcom Email Security.cloud — Symantec Email Security.cloud (MessageLabs) |
| Needed on your domain? | Yes — mail from it uses your domain as the envelope sender, so SPF checks this record |
What it costs, and is it in your record?
We measure include:spf.messagelabs.com as the page opens. Enter a domain: we read its SPF record, follow every include and say whether Broadcom Email Security.cloud’s is there and what it costs.
What it covers
Mail delivered by Email Security.cloud servers — outbound relay, and mail that passes through them for other reasons.
Do you need it?
Yes, if your outbound mail relays through Email Security.cloud. Broadcom also recommends it when it does not: when one Email Security.cloud customer mails another, the recipient’s service checks SPF against the MessageLabs delivery server, so a sender with -all and no include is rejected.
Common mistakes
- include:messagelabs.com — Broadcom says this is wrong; the records live under spf.messagelabs.com.
- Staying on ~all: Broadcom suggests testing with ~all for a week, then moving to -all, since soft mode “does not stop email spammers”.
- More than one SPF record.
Sources
Checked on 26 September 2026 against these official sources:
- Implement SPF records for Email Security.cloud — knowledge.broadcom.com
- Enforce SPF for a domain protected by Email Security.cloud — knowledge.broadcom.com