include:websitewelcome.com is the SPF include Bluehost and HostGator give for mail sent from their hosting: “websitewelcome.com should be used in the SPF record configuration rather than brand-specific URLs.” It is broader and dearer than it looks — its record includes Google Workspace’s and Microsoft 365’s too — and include:bluehost.com, which Bluehost also shows, needs more than 10 lookups on its own.
v=spf1 a mx include:websitewelcome.com ~all
| Belongs to | Bluehost and HostGator — Shared and cloud hosting mail (Newfold Digital) |
| 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:websitewelcome.com as the page opens. Enter a domain: we read its SPF record, follow every include and say whether Bluehost and HostGator’s is there and what it costs.
What it covers
Mail sent from Bluehost (Bluehost Portal and Bluerock accounts) and HostGator shared hosting — mailboxes and your website’s own mail.
Do you need it?
Yes, if you send mail from your Bluehost or HostGator hosting: that mail carries your own addresses, so SPF checks your record. Bluehost adds a default record to every domain’s zone.
Know what it brings with it. websitewelcome.com includes a mail-filtering service’s record, Newfold’s own servers, Google Workspace’s _spf.google.com and Microsoft 365’s spf.protection.outlook.com — so it authorises every Google and Microsoft 365 sender, and with a and mx the default record uses all 10 lookups before anything else is added.
Its other forms
| Include | For |
|---|---|
bluehost.com | Bluehost’s own company record, which Bluehost’s help shows as its strictest option. It includes nine more records — Qualtrics, Salesforce, SparkPost, Mailjet and Microsoft 365 among them — and needs more than 10 lookups by itself — so SPF evaluation that follows it ends in an error. |
Common mistakes
- include:bluehost.com: it cannot be evaluated within the 10-lookup limit, so SPF fails with a permanent error.
- Adding another record instead of editing Bluehost’s: “The default SPF record must be deleted from your cPanel before installing a new one.”
- Adding another service to a record that already uses a, mx and websitewelcome.com — it is at the limit already.
- Putting the all first — “Arguments are processed from left to right”.
Questions
Why does my Bluehost record fail with “too many DNS lookups”?
Because a and mx cost one lookup each and websitewelcome.com costs several more (eight when we checked), so a further include soon takes it past 10. Remove what you do not use — for example the a or mx if your website does not send mail — or use your mailbox provider’s include instead if you do not send from the hosting.
Sources
Checked on 26 September 2026 against these official sources:
- Bluehost help: SPF records — bluehost.com
- Hg spf records — hostgator.com