# Fix email authentication for notion.so

You are working on the DNS and mail configuration for notion.so.
Measured by MailAuthWatch on 17 Oct 2026 from public DNS. Grade C (70/100).
Report: https://www.mailauthwatch.com/check/notion.so

## What is published right now (do not assume anything else)
- SPF (TXT notion.so): v=spf1 ~all   — valid, 0 of 10 lookups
- DMARC (TXT _dmarc.notion.so): v=DMARC1; p=quarantine; pct=100; rua=mailto:re+1b3a27dd30bc@inbound.dmarcdigests.com;
- DKIM: no key found under 79 common selectors
- MX: none (domain does not receive mail)
- Nameservers: dana.ns.cloudflare.com, woz.ns.cloudflare.com  → records are managed in Cloudflare

## Tasks, in order of impact
### 1. No DKIM key found under 79 common selectors.
Why: Either DKIM signing is off, or it uses a selector we did not probe. Without DKIM, forwarded mail and anything that breaks SPF fails DMARC.
Turn on DKIM signing at the mail provider and at every third-party service that sends as this domain (CRM, newsletter tool, help desk).
Publish the selector records each service shows. If DKIM is already on with a selector not in the common list, add that selector to the MailAuthWatch check instead.

## Rules
- Publish exactly one SPF record; never add a second v=spf1 TXT.
- Do not remove any include: or ip4: you cannot account for; mail may depend on it.
- Do not set DMARC to p=reject in one step; stage through p=none → quarantine → reject.
- Show the planned DNS changes as a diff (record, old value, new value) before applying them.
- If you cannot access Cloudflare, stop and say exactly what access you need.

## Verify
  dig +short TXT notion.so
  dig +short TXT _dmarc.notion.so
Then open https://www.mailauthwatch.com/check/notion.so?fresh=1 and confirm:
  DKIM found. Target grade: A.

## Report back
List each record you changed (name, type, old value, new value), what you verified, and anything you could not do.