If you send emails from your .co.site Neo domain using a third-party tool (e.g., Zendesk, Mailchimp, CRM/marketing/transactional platforms), add both SPF and DKIM for that provider.
Why this matters (and what can happen if you don’t)
Not setting up SPF and DKIM for third-party sending commonly leads to:
Lower deliverability: more emails landing in spam/promotions, or being throttled.
Higher rejection rates: some receiving systems will reject unauthenticated mail or treat it as suspicious.
Brand and security risk: your domain is easier to spoof, and recipients may see “via/on behalf of” type warnings depending on the setup.
Account risk: If email sent from your domain repeatedly fails authentication and results in high bounces/complaints, sending may be restricted by provider.We actively monitor authentication signals (using DMARC reports). If your domain keeps sending emails without proper SPF/DKIM setup and inboxes like Gmail and Outlook start blocking or rejecting those emails, we may have to remove DNS for your domain to protect reputation, deliverability and prevent abuse.
What to do (recommended)
Adding SPF? Add DKIM too.
Adding DKIM? Make sure SPF covers that sender too.
If a provider asks you to add a CNAME for email sending/authentication, also set up DKIM (many providers use CNAME-based DKIM).