NetSuite has two SPF includes, often mixed up. sent-via.netsuite.com is for email; mailsenders.netsuite.com is for faxes sent from NetSuite through a service such as eFax, which checks SPF. For email, Oracle says you do not need SPF to align with DMARC, and to add the include only if a recipient’s mail system asks for it — DMARC passes through NetSuite’s DKIM.
v=spf1 include:sent-via.netsuite.com ~all
| Belongs to | Oracle NetSuite email and fax |
| Needed on your domain? | It depends on how you use it — see below |
What it costs, and is it in your record?
We measure include:sent-via.netsuite.com as the page opens. Enter a domain: we read its SPF record, follow every include and say whether NetSuite’s is there and what it costs.
What it covers
sent-via.netsuite.com: email sent from NetSuite. mailsenders.netsuite.com: faxes sent from NetSuite.
Do you need it?
For email, usually not: Oracle says you do not need to align SPF with your DMARC policy when sending from NetSuite, and to set up SPF only “If you must include a reference to NetSuite SPF” — for a recipient that asks for it. DKIM and a DMARC policy are what NetSuite needs.
Without NetSuite’s DKIM set up, it rewrites the sender to its shared domain — jsmith@example.com <system@sent-via.netsuite.com>.
For fax: if you send faxes from NetSuite through eFax, add include:mailsenders.netsuite.com, because eFax validates SPF.
Its other forms
| Include | For |
|---|---|
mailsenders.netsuite.com | Faxes sent from NetSuite, for eFax’s SPF check — not email. |
Common mistakes
- Adding mailsenders.netsuite.com for email: it is the fax sender.
- Allow-listing NetSuite’s addresses instead of using its DKIM.
Sources
Checked on 26 September 2026 against these official sources:
- NetSuite Help Center, topic 4820740297 — docs.oracle.com
- NetSuite Help Center, topic 1536091586 — docs.oracle.com
- NetSuite Help Center, topic 1556559917 — docs.oracle.com