github.com
84/100
Mail provider: Microsoft 365
| Check | Details | |
|---|---|---|
| MX | ✔ | github-com.mail.protection.outlook.com |
| SPF | ✔ | v=spf1 ip4:192.30.252.0/22 include:spf.protection.outlook.com include:_netblocks.google.com include:_netblocks2.google.com include:mail.zendesk.com include:_spf.salesforce.com include:servers.mcsv.net include:mktomail.com include:sendgrid.net ip4:62.253.227.114 ip4:166.78.69.169 ip4:166.78.69.170 ip4:166.78.71.131 ~all (10 lookups); ~all (softfail) - fine with DMARC; -all is stricter |
| DKIM | ⚠ | Selectors found: selector1 (1024-bit), google (2048-bit+), k1 (1024-bit), k2 (2048-bit+), k3 (2048-bit+), s1 (2048-bit+), s2 (2048-bit+), smtpapi (1024-bit), mailo (1024-bit); upgrade 1024-bit keys to 2048-bit |
| DMARC | ✔ | v=DMARC1; p=quarantine; sp=reject; pct=100; rua=mailto:dmarc@github.com; ruf=mailto:dmarc@github.com; fo=1 |
| MTA-STS | ⚠ | Not set (optional; enforces TLS for mail sent to you) |
| TLS-RPT | ⚠ | Not set (optional; reports TLS delivery failures) |
| BIMI | ℹ | Not set (optional; shows your logo in Gmail/Yahoo; needs DMARC quarantine/reject) |
How to fix it
- No DNS changes needed. 🎉
DNS changes can take up to 24–48 hours. Re-run the check afterwards.
Want it fixed for you? I set up SPF, DKIM and DMARC without breaking your other senders,
with a before/after report.
Get it fixed on Fiverr
Get it fixed on Fiverr
Prefer to do it yourself? Get the step-by-step Fix Kit ($15) – 19-page guide, checklist, 20+ providers.