SEND-3 Sending, approvals & deliverability

Verify your sending domain (SPF, DKIM, DMARC)

Last verified

Until your sending domain is verified, Deloosh blocks marketing and cold-outreach sends from it. The denial code is domain_unverified, and the reason reads: “tenant {your workspace} has no verified sending domain (connected_systems.email_domain_verified is not set)”.

What domain auth is

Domain auth is the DNS proof — SPF, DKIM, and DMARC — that mail from your domain is really yours. Without it, sending is unsafe.

  • SPF lists which servers are allowed to send as your domain.
  • DKIM signs each message so the receiving server can verify it was not forged or altered.
  • DMARC tells mailbox providers what to do when a message fails those checks, and where to report it.

They are DNS records you publish at whoever hosts your domain. They are not settings inside Deloosh.

Why an unverified domain is blocked rather than warned

Unauthenticated mail risks spam-folder placement and makes domain spoofing easier. Gmail and Yahoo both require authentication from bulk senders, so Deloosh treats verification as a pre-send requirement.

So this is a hard block, not an advisory. It applies to the classes that send from your domain: marketing and cold outreach.

How to get verified

Deloosh does not yet have a self-serve domain-verification screen. Today, verification is a conversation: ask the assistant about domain setup, or contact support, and you will be given the exact SPF, DKIM, and DMARC records to publish for your domain. Once the records are live and checked, your workspace is marked verified and the block lifts.

The assistant will raise this with you early — before your first send — because it is a precondition, not a gate that ambushes you later. It states it once and offers to walk you through it whenever you are ready; it will not nag, and it will not touch your DNS itself.

Checking your status

The straightforward check is to ask in chat. If sends are being denied with domain_unverified, the domain is not verified yet, whatever your DNS host’s dashboard says — propagation and exact-record mismatches are the usual culprits.

Domain verification is separate from warm-up. Verifying proves the mail is yours; warm-up is the slow ramp that earns a new domain its reputation. See SEND-15, Warm-up: why new senders start slow.

For the full list of reasons a send can be stopped, see SEND-2, Why was my send blocked? (denial reasons index).

More in Sending, approvals & deliverability