Company Email Pattern Finder: GitHub Commits + MX Check

What it does

Give it company domains and it returns the email format each company uses, measured from the commit authors in its public GitHub organization, with a confidence score, the alternatives, MX records and the mail provider. Every row also carries the organization's profile, tech stack and recent activity.

{
  "domain": "vercel.com",
  "githubOrg": "vercel",
  "orgName": "Vercel",
  "orgIsVerified": true,
  "publicRepos": 239,
  "publicMembers": 72,
  "orgMatchConfidence": "confirmed",
  "pattern": "first.last",
  "patternConfidence": 0.77,
  "patternConfidenceLevel": "high",
  "patternInferred": false,
  "patternExample": "jane.doe@vercel.com",
  "alternatives": [
    { "pattern": "first", "confidence": 0.09, "matches": 2 },
    { "pattern": "last", "confidence": 0.03, "matches": 1 }
  ],
  "evidenceCount": 20,
  "mxValid": true,
  "emailProvider": "Google Workspace",
  "catchAll": null,
  "commitSource": "git",
  "commitsScanned": 1282,
  "uniqueEmailsSeen": 110,
  "corporateEmailsFound": 20,
  "noreplyEmails": 32,
  "personalEmailsSeen": 34,
  "activeCommitters90d": 50,
  "notes": []
}

Why this one

Use cases

• Learn whether a company writes `jane.doe@` or `jdoe@` before constructing any address by hand.
• Enrich a list of company domains with mail provider, tech stack and engineering activity.
• Find developer-tool prospects that are active on GitHub, with their languages and how many people commit.
• Check which domains have no MX records and cannot receive email, without sending a message.

Input

Every field has a default, and the defaults are deliberately small so a first run is cheap enough to inspect before you commit to a sweep. This table mirrors the Actor's own input schema field for field.

Output and fill rates

A field being in the schema is not the same as it having a value. The percentages below were counted on real runs; the sample sizes are in Measurements. Anything not listed here is not promised.

Every key is always present. A field that exists but is empty comes back as explicit null, so a parser never has to guess.

Datasets

Different record types go to different datasets, so the main table never carries columns that are blank on most rows.

Pricing

Pay per delivered result. Charges are applied as each row is produced rather than in a lump at the end, so an aborted run bills only for what it actually gave you.

Measurements

Each figure is shown with the method that produced it. A benchmark without a method is a marketing claim wearing a number's clothes.

What it will not do

Stated plainly so you can judge fit before spending anything.

• Only companies with a public GitHub organization and commits from their own domain get a measured pattern; the rest get the most common pattern for their mail provider, marked as a guess with confidence 0.10.
• Without a GitHub token, GitHub allows 60 API requests an hour, about 15 domains per run. With a token, about 500 domains an hour.
• No address is verified. `catchAll` is always null because whether a server accepts every recipient cannot be known without SMTP.
• The organization match can be wrong for generic names. Each row reports `orgMatchConfidence` and `orgMatchReasons`; `confirmed` means the organization's commits contain addresses on the requested domain, which held for 38 of 44.
• Latin American companies measured weaker: of 8, a pattern was measured for 5 and reached high confidence for 3.
• Forked repositories are skipped by default, because their commits mostly belong to the original project's authors.

Privacy

• A corporate email address tied to a name is personal data in the EU, and a pattern applied to a named person produces one.
• By default the row is company-level data only: pattern, confidence, counts, MX and the public organization profile, with no individual's address.
• Corporate addresses behind the pattern appear only with `includeSamples`, and personal-domain addresses only with `includePersonalEmails`; the input asks the user to enable them only with a lawful basis.
• GitHub's Acceptable Use Policies forbid using its information for spamming, including sending unsolicited emails to users or selling personal information to recruiters, headhunters and job boards.
• The GitHub token, when given, is never logged or written to the output.
• Removal requests: privacy@actorstack.dev

See also the data removal process.

Guides for this Actor

• Email format from GitHub commitsEvery commit pairs an author's name with an address. How the Company Email Pattern Finder turns that into a company email format with a confidence score, how well it worked on 46 domains, and why it stops at the MX record.