MailAuthWatch
C55/100

gandi.net

2 fixes stand between this domain and a clean A. 2 items below, ordered by how much inbox they are costing you.

SPF PASSDKIM NOT FOUNDDMARC NOT ENFORCINGMX OK
Monitor this domainRe-run checkMeasured 0s ago · 1292 ms · public DNS

Fix these, in this order

ranked by impact
1
DMARC is sitting at p=none.

You are collecting reports and enforcing nothing, so anyone can still send as you. Gmail and Yahoo accept p=none from bulk senders, but it protects nobody.

Do this: move to p=quarantine; pct=25 for two weeks, watch the reports, then step to pct=100 and p=reject.

2
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 include:_spf.gandi.net -all
DMARC · _dmarc.gandi.net
v=DMARC1; p=none; rua=mailto:dmarc@gandi.net
DKIM · 0 of 79 selectors
none under common selectors
MX · Custom / other
10 mail12.gandi.net
30 mail8.gandi.net

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 include:_spf.gandi.net -all
DNS lookups
2 of 10 allowed
Final mechanism
-all
  • OK No problems detected.

Include tree

2 / 10
gandi.net0
└─ include:_spf.gandi.net+2
     └─ _nblcorp.gandi.net

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=none; rua=mailto:dmarc@gandi.net
Policy
p=none
Applies to
100% of failing mail
Aggregate reports
mailto:dmarc@gandi.net
  • WarningPolicy is p=none: you receive reports but spoofed mail is still delivered. Move to p=quarantine, then p=reject, once reports show legitimate mail passing.

Mail exchange and extras

  • OK No problems detected.
MTA-STS
Not published optional: enforces TLS for inbound mail
TLS-RPT
Not published
BIMI
Not published optional: brand logo in inboxes, requires p=quarantine or reject

How the grade is calculated

Score 55/100. SPF present and valid. SPF ends with -all. DMARC present and valid. DMARC policy is none (monitoring only). 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: