Is github.com's email set up correctly?
A live check of github.com's email authentication — SPF, DKIM, DMARC, and MX, the four signals mailbox providers use to decide whether github.com's email reaches the inbox.
github.com has a strong email authentication setup.
Receivers can reject or soft-fail spoofed mail.
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
A signing key is published, so sent mail can be cryptographically verified.
Mail failing authentication is quarantined or rejected.
v=DMARC1; p=quarantine; sp=reject; pct=100; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1
github-com.mail.protection.outlook.com
Sending cold email from github.com?
Bulk Email Boxer warms your mailboxes, monitors SPF/DKIM/DMARC, stamps RFC 8058 one-click unsubscribe on every send, and verifies your lists — so your email lands. $40/mo flat, unlimited mailboxes, no per-seat fees.
Start free trial →Fix what's missing: Complete deliverability guide · DKIM setup · Full deliverability tool
Checks public DNS records only. Data shown was current at build time; run the live tool for the latest.