← Help Center
Email, forms & schedulingHOW-TO

Sending domains & DMARC

Register the domain you send from, verify its DNS, give campaigns their own subdomain, and read what your DMARC record says.

Why a verified domain

Email that is not authenticated by the domain it claims to come from is filtered or rejected outright — Gmail and Yahoo have required SPF, DKIM, and DMARC on bulk mail since 2024. Settings → Email → Sending domains is where PULSE registers your domain with its delivery provider and shows you the records to add.

Add and verify a domain

  1. Under Sending domains, type the domain (for example acme.com) and click Add domain.
  2. PULSE lists the DNS records to create at your registrar or DNS host: an SPF record, a DKIM key, and an MX record for bounce handling. Copy each name and value exactly.
  3. Once the records are in your zone, the status moves from pending to verified on the next check — usually within an hour, sometimes longer while DNS propagates. Use Check status to re-read it. Until a domain is verified, mail from any address on it is refused, so the Sender card warns if your From address sits on an unverified domain.

Give campaigns their own subdomain

Reputation attaches to the exact domain in the From address. Sending campaigns from the same domain as your invoices means one bad campaign can hurt the delivery of the mail you most need to arrive. Register a subdomain — mail.acme.com is the usual choice — verify it the same way, then under Who each kind of email comes from set Campaigns & sequences to an address on it, such as news@mail.acme.com. Person-to-person, Documents & records, and Internal notifications stay on your main domain. The Sender card warns whenever campaigns still share the domain your documents and invoices go out on.

Any local part works on a verified domain — news@, hello@, updates@ — and you can change it at will. Replies still come back to the Reply-To you set.

What the DMARC line means

Each verified domain shows its DMARC policy, looked up live from DNS. A subdomain with no record of its own is covered by its parent, so mail.acme.com reading "covered by acme.com" is correct, not a problem. The policy is one of three: none (monitoring only — receivers report but take no action on a forged message), quarantine, or reject. None satisfies the Gmail and Yahoo requirement; moving to quarantine is the usual next step once the aggregate reports have looked clean for a while.

The reports address (rua) is where receivers send those aggregate reports. If it points at a vendor you no longer use, nobody on your side is reading them — repoint it to a mailbox you own. Never add a second DMARC record at the same name: two records means receivers treat the domain as having no policy at all.

Removing a domain

Remove takes the domain off this workspace only. Adding it back adopts the existing registration and it verifies immediately.

Still need a hand?
Check system status, report a bug, or message the team.