--- title: "Email Security" description: "Add SPF, DKIM and DMARC to your zone in one click, what each record actually says, and the order to roll them out without breaking your own mail." category: "Deployment" language: en source: https://cubepath.com/docs/products/deployment/dns-email-security updated: 2026-11-17 --- # Email Security Open the zone → **Recommendations** tab in [my.cubepath.com](https://my.cubepath.com). Three TXT records decide whether mail claiming to come from your domain is believed: **SPF**, **DKIM** and **DMARC**. Without them, anyone can put your domain in the `From:` line and a fair number of receiving servers will deliver it; with them, forgeries fail and your own mail lands in inboxes instead of spam folders. The tab checks which of the three your zone already has and offers to create the missing ones. Each shows as **Configured** once a matching record exists, so it doubles as a quick audit of a zone you inherited. ## SPF SPF lists the servers allowed to send mail for your domain. **Add SPF** creates a TXT record on `@` with the strictest possible policy: ``` v=spf1 -all ``` That says *nothing* is allowed to send mail as this domain. It's the right starting point for a domain that doesn't send mail at all (a marketing site, a parked domain, an internal service), and it's the single most effective anti-spoofing record you can publish. > Warning: If the domain **does** send mail, edit the record before you're done. Add your provider's mechanism first (typically `include:` for a hosted provider, or `ip4:`/`ip6:` for your own server) and keep `-all` at the end. Publishing a bare `v=spf1 -all` on a domain that sends mail makes every message you send fail SPF. Edit it in the [Records](/docs/products/deployment/dns-records) tab like any other TXT record. ## DKIM DKIM signs your outgoing mail so receivers can prove it wasn't altered in transit and really came from you. The public half of the key lives in DNS, at `._domainkey`. You need two things from your mail provider (Google Workspace, Microsoft 365, Postmark, whoever sends for you): the **selector** (often `default`, `google`, or something provider-specific) and the **public key**. Paste both into the fields in the DKIM section and **Add DKIM** creates the record at the right name. > Note: The key comes from your provider and only they can generate it. If you don't have one yet, enable DKIM in their admin panel first, then come back with the selector and key they give you. ## DMARC DMARC ties the other two together: it tells receiving servers what to do when SPF or DKIM fails, and where to send reports about it. **Add DMARC** creates a TXT record at `_dmarc`: ``` v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com ``` `p=quarantine` asks receivers to put failures in the spam folder rather than deliver them. `rua` is the address that receives the reports. You can enter your own reports address in the DMARC section before clicking **Add DMARC**; leave it empty and it defaults to `dmarc@` your domain, which only helps if that mailbox exists. The reports are aggregate XML from every receiver, and they're how you find the legitimate senders you forgot about before they start getting blocked. ## The order to do this in ```steps ### Publish SPF and DKIM first Get both correct for every system that sends as your domain: your mail provider, your ticketing system, your newsletter tool, your application's transactional mail. ### Add DMARC in monitoring mode Start at `p=none` with a working `rua` address, so you get reports without changing how anything is delivered. ### Read the reports for a couple of weeks They will show senders you'd forgotten. Fix their SPF and DKIM. ### Tighten the policy Move to `p=quarantine`, then `p=reject` once nothing legitimate is failing. ``` The button gives you `p=quarantine` straight away, which is right for a domain that doesn't send mail and aggressive for one that does. If your domain sends real mail, change it to `p=none` in [Records](/docs/products/deployment/dns-records) until the reports are clean. > Tip: A domain that never sends mail still deserves SPF and DMARC. It's the cheapest way to stop your brand being used in phishing, and it takes about a minute here.