MX records for github.com
Live MX lookup for github.com: 1 mail host, run by Microsoft 365.
try:
- mail hosts
- github-com.mail.protection.outlook.com
- provider
- microsoft
- spf record
- 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
- dmarc policy
- quarantine
- dmarc record
- v=DMARC1; p=quarantine; sp=reject; pct=100; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1
- disposable domain
- no
- free consumer provider
- no
Mail servers for github.com
DNS lists 1 mail host for github.com, starting with github-com.mail.protection.outlook.com. Lower priority values are tried first; the rest exist for failover.
Who runs the mail
The hosts match the pattern of Microsoft 365. Microsoft 365 (Exchange Online Protection) hosts the mail. Tenants are frequently configured to accept every address at the domain, so mailbox checks answer catch-all more often here than on other providers, and a risky verdict means the mailbox could not be disproved rather than that it is bad.
What this means for verification
For github.com, verification runs the whole pipeline: syntax, live MX, the open lists, and then the SMTP handshake with the mail host, with no message ever transmitted. Each verdict carries a machine-readable reason.
More checks for github.com
checked 2026-09-03 · sources: live-dns 2026-09-03 · disposable-domains 2026-09-02 · free-provider-domains 2026-09-02 · mx-provider-patterns 2026-09-03 · rdap-registration 2026-09-03 · Top-domain list: Majestic Million, CC BY 3.0
Need this at scale?
The Spaw API runs the same checks plus mailbox-level SMTP verification, batch and bulk endpoints, and list monitoring — 10 free lookups a month, no card required.