Safe to Send ยท Low risk

Verify Emails at Github.com

Real-time SMTP verification with 99.7% accuracy. Check any @github.com address before you send, no signup required.

SMTP Responsive MX 1 Auth 3/3 Persistent
Github.com Email Checker
LIVE
85Deliverability
1MX Records
10 / 10Free Checks
Verify 10,000 Github.com emails for just $9.95
Military-Grade Encryption
ISO 27001
SOC 2 Type II
GDPR
CCPA
HIPAA

Deliverability

4 signals
Deliverability85/100
Risk Score15
Blacklists0/8
Domain Age18 years

Infrastructure

5 signals
SMTP StatusResponsive
MX Records1
Authentication3/3
Accepts MailYes
Catch-AllNot detected

Classification

4 signals
Domain TypeCorporate Email
DisposableNo
Free ProviderNo
Mail ProviderMicrosoft 365

Verification Status

May 30, 2026

Yes. You can verify any @Github.com address in real time with a direct SMTP handshake that provides 99.7% accuracy. Github.com is operated by Microsoft Corporation, runs 1 mail server, enforces 3 of 3 authentication standards, and is currently responding to SMTP.

Valid providerYesYes
Mail ProviderMicrosoft 365
MX Records1Active
Authentication3/3Full

Github.com Key Facts

Corporate Domain
Mail ProviderMicrosoft 365
Domain TypeCorporate Email
MX Records1 github-com.mail.protection.outlook.com
SMTP StatusResponsiveResponsive
SPF / DKIM / DMARCPass / Pass / Quarantine
Catch-AllNot detected
DisposableNoNo
Domain Age18 years (since 2007)
RegistrarMarkMonitor, Inc.
Last VerifiedMay 30, 2026

How to read your Github.com verification result

Every check returns one of three clear outcomes so you know exactly what to do with the address.

Passed - Safe to Send

The mailbox exists and accepts mail. Send with confidence, the address is deliverable.

Failed - Do Not Send

The mailbox does not exist, is disposable, or will hard-bounce. Remove it to protect your sender reputation.

Unknown - Use Caution

The server is catch-all or greylisting, so existence cannot be confirmed. Send selectively and watch engagement.

What are Github.com's MX records?

github.com publishes 1 MX record. The primary mail exchanger is github-com.mail.protection.outlook.com, hosted by Microsoft 365, and it is currently reachable and answering SMTP. Mail is routed through these servers in priority order, lowest number first.

MX Records

1 record
PriorityHostnameIPStatus
0 github-com.mail.protection.outlook.com 52.101.50.10 Reachable

Infrastructure

Responsive
SMTP StatusResponsiveResponsive
Primary MXgithub-com.mail.protection.outlook.com
Mail ProviderMicrosoft 365
Accepts MailYes
Catch-AllNot detected
220 DS2PEPF00003448.mail.protection.outlook.com Microsoft ESMTP MAIL Service ready at Sat, 30 May 2026 07:10:32 +0000 [08DEBCE08DD54BE1]

Can you verify Github.com email addresses?

Yes. github.com is a valid email domain, operated by Microsoft Corporation. Addresses are persistent and real mail reaches a genuine recipient. Individual mailboxes still go stale, so verify each one before you send.

Verification method

SMTP

A live SMTP handshake connects to Github.com's mail server and asks whether the mailbox exists using the RCPT TO command, without ever transmitting a message. The recipient never sees the check.

Accuracy

99.7%

Each address runs through 30+ checks including SMTP existence, catch-all detection, role-account filtering, and disposable matching. The same engine has verified billions of addresses since 2012.

Why verify Github.com emails before you send?

Every unverified address is a gamble. Here is what happens when you skip verification and mail a list that has not been cleaned.

Catch role changes

People leave companies. Verification flags github.com mailboxes deactivated since you collected them.

Avoid dead mailboxes

Expired or full github.com inboxes hard-bounce. A live SMTP check catches them before you hit send.

Protect sender reputation

Low bounce rates keep you trusted by github.com mail servers and the major mailbox providers.

Keep CRM data accurate

Verified contacts mean your CRM, lead scoring, and routing all run on addresses that reach a person.

Who operates Github.com?

Github.com is Microsoft Corporation, registered through MarkMonitor, Inc. and first seen Oct 9, 2007.

Registration (WHOIS)

.com
RegistrarMarkMonitor, Inc. / IANA 292
RegisteredOct 9, 2007 / 18 years old
UpdatedSep 7, 2024
ExpiresOct 8, 2026
RegistrantGitHub, Inc. / UNITED STATES
Tech ContactUNITED STATES
dns3.p08.nsone.netns-1283.awsdns-32.orgns-421.awsdns-52.comns-1707.awsdns-21.co.ukdns1.p08.nsone.netdns2.p08.nsone.netns-520.awsdns-01.netdns4.p08.nsone.net

Domain Profile

Corporate Email
Domaingithub.com
OrganizationMicrosoft Corporation
TypeCorporate Email
Mail ProviderMicrosoft 365
SPFPassPass
DKIMPassPass
DMARCQuarantineQuarantine

GitHub (github.com) is the world's largest software development and version control platform, owned by Microsoft Corporation and headquartered in San Francisco, California. GitHub hosts over 200 million code repositories and serves over 100 million developers worldwide. The platform is essential infrastructure for open-source software development and enterprise code collaboration.

The github.com domain implements enterprise email authentication with SPF, DKIM, and DMARC enforcement. GitHub is frequently targeted by phishing attacks that impersonate repository notifications, pull request alerts, and security vulnerability warnings. Strong authentication protects the developer community from these sophisticated social engineering attempts.

Email verification against github.com provides definitive accept/reject responses for individual mailboxes. The domain does not function as catch-all. GitHub's mail infrastructure benefits from Microsoft's enterprise security stack and implements strict rate limiting on inbound SMTP connections.

Delivering to github.com requires proper sender authentication. GitHub's email filtering leverages Microsoft's security infrastructure to evaluate incoming messages for authentication compliance, sender reputation, and content quality. Maintaining valid SPF, DKIM, and DMARC records is essential for reliable inbox delivery to github.com employees.

How do you verify Github.com emails in bulk?

Upload a CSV or TXT list of Github.com addresses to the bulk email verifier. Every address runs through a live SMTP handshake plus catch-all, role-account and disposable detection, and you download a clean list when processing completes. For real-time checks at signup, use the real-time email verification API.

1

Upload your list

CSV or TXT with one email per line. No formatting needed.

2

SMTP verification runs

Each Github.com address is checked with a live server handshake.

3

Download clean results

Get a verified list with status codes, risk flags, and catch-all detection.

Verify Github.com emails from $0.0001 each

Pay as you go. No subscriptions, and credits never expire.

10,000 Verifications
$9.95
$0.00099 per email
One-time payment. No contracts.
Get Started
25,000 Verifications
$23.95
$0.00095 per email
One-time payment. No contracts.
Get Started
Popular
50,000 Verifications
$44.95
$0.00089 per email
One-time payment. No contracts.
Get Started
100,000 Verifications
$74.95
$0.00075 per email
One-time payment. No contracts.
Get Started

Frequently asked questions about Github.com

Everything about verifying email at this domain.

Yes, github.com is the official corporate email domain for Microsoft Corporation. It is used for business communications and is not available for public registration.

No, github.com is a corporate email domain belonging to Microsoft Corporation, used exclusively by employees and authorized personnel.

github.com uses enterprise-grade mail infrastructure. Check the MX records section above for specific mail server details.

B2B marketing to github.com addresses requires proper consent and compliance with anti-spam laws. Corporate domains may use catch-all configurations, so verify addresses before sending.

Corporate domains like github.com may use catch-all configurations. Use BulkEmailChecker advanced verification to detect catch-all behavior and validate individual addresses.

Upload a CSV or TXT list to the bulk email verifier. Every address runs through 30+ checks including SMTP existence, catch-all detection, role-account, and disposable matching. Processing time depends on list size.

99.7% accurate using a direct SMTP handshake with github.com's mail servers, the same engine that has verified billions of addresses since 2012.