MailAuthWatch
C70/100

notion.so

1 fix stands between this domain and a clean A. 1 item below, ordered by how much inbox it is costing you. Measured 0s ago from public DNS in 90 ms.

SPF PASSDKIM NOT FOUNDDMARC QUARANTINENO MX

Fix these, in this order, or hand the list to your agent

ranked by impact
1
No DKIM key found under 79 common selectors.

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.

Do this: turn on DKIM at your mail provider and at every third-party sender, then add the selector names when monitoring so they are verified daily. If DKIM is already on with an uncommon selector, add it to the check.

Records found

SPF · TXT
v=spf1 ~all
DMARC · _dmarc.notion.so
v=DMARC1; p=quarantine; pct=100; rua=mailto:re+1b3a27dd30bc@inbound.dmarcdigests.com;
DKIM · 0 of 79 selectors
none under common selectors
MX · None (no MX)
none

Fix this with your AI agent

AGENT-READY

A prompt built only from what was measured: the records as published, 1 task in order, exact record values and Cloudflare commands, guardrails, and how to verify. Paste it into Claude, Cursor, Copilot or ChatGPT.

# 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
…
Your agent, your DNS, your review. MailAuthWatch never changes records; it writes the plan and re-checks the result.

Grade history

Free checks keep nothing. Monitoring records every daily measurement and alerts you on change.
History goes back as far as your subscription.

SPF OK

v=spf1 ~all
DNS lookups
0 of 10 allowed
Final mechanism
~all
  • OK No problems detected.

DKIM Not found

DKIM selectors cannot be listed from DNS, so 79 selectors used by common providers were probed. "Not found" means none of those selectors exist; the domain may still sign with a custom selector.

  • WarningNo DKIM key found under 79 common selectors. If you know your selector, add it to the check; if you have no DKIM at all, enable it at your mail provider.

DMARC OK

v=DMARC1; p=quarantine; pct=100; rua=mailto:re+1b3a27dd30bc@inbound.dmarcdigests.com;
Policy
p=quarantine
Applies to
100% of failing mail
Aggregate reports
mailto:re+1b3a27dd30bc@inbound.dmarcdigests.com
  • NotePolicy is p=quarantine. p=reject is the strongest protection once you are confident all senders are aligned.

Mail exchange and extras

  • NoteNo MX records: this domain does not receive mail. If it also never sends mail, publish "v=spf1 -all" and a p=reject DMARC record to stop spoofing.
MTA-STS
Not published optional: enforces TLS for inbound mail
TLS-RPT
Not published
BIMI
OK v=BIMI1; l=https://vmc.digicert.com/ae66f82a-dd47-4f08-9fd9-fd865f1d0b30.svg; a=https://vmc.digicert.com/ae66f82a-dd47-4f08-9fd9-fd865f1d0b30.pem

How the grade is calculated

Score 70/100. SPF present and valid. SPF ends with ~all. DMARC present and valid. DMARC policy is quarantine. DMARC aggregate reporting enabled. SPF contributes up to 35 points, DKIM up to 25, DMARC up to 40 (policy strength and reporting). Any critical issue caps the grade at C. Lookups that failed are shown as "not measured" and never counted as missing.

Check another domain: