Domain Authentication & Email Security Requirements

To protect your brand and ensure reliable email delivery, Oyster requires all clients to authenticate their domains before sending emails through the platform.

Why this matters

Email authentication prevents spoofing, improves deliverability, and ensures compliance with EU data‑protection and anti‑fraud standards.

What you need to set up

To use your own domain for sending emails, you must configure:

SPF – tells mail servers that Oyster is allowed to send emails for your domain
DKIM – digitally signs your emails so recipients know they’re genuine
DMARC – protects your domain from impersonation and enforces EU‑aligned security policies

What we need from you

Before we enable email‑sending on your account, you’ll need to:

Add the SPF, DKIM and DMARC records we provide to your DNS
Confirm the setup or give us temporary DNS access to validate it
Keep your DNS records up to date if your domain provider or policies change

If your domain is not properly authenticated:

Emails may fail to deliver or go to spam
Your domain reputation may be affected
Oyster may temporarily pause email‑sending features until the issue is resolved

These DNS records must remain active and correctly configured for the duration of your contract.

Sadly as we are not responsible for this, this does not pause or reduce your subscription fees.

You are responsible for maintaining compliant SPF/DKIM/DMARC settings and ensuring they meet EU security and data‑protection requirements. Oyster cannot be held liable for delivery issues or domain reputation problems caused by incorrect DNS configuration.

It's not rocket science and often overlooked but if you need here is a visual step-by-step guide click here.