// trusted b2b contact database
Where Tomba's B2B contact data comes from
150,000+ sales professionals rely on Tomba for verified B2B contacts: work emails, phone numbers, LinkedIn profiles and company data. We crawl 2 billion pages every month, and every email keeps the public pages it was found on.
- PersonRichard Hendricks · CEO
- Emailrichard@piedpiper.comvalidverifying
- Phone+1 650 555 0142
- CompanyPied Piper · piedpiper.com
- LinkedInin/richard-hendricks
- TechCloudflare · HubSpot · React
- Verified B2B emails
- 450M+
- Company domains indexed
- 80M+
- Pages crawled a month
- 2B+
- Of crawled addresses pass the checks
- 6%
Tomba internal counts, October 2026.
// teams at these companies use tomba
// 01 · provenance
Every address comes with its sources
Ask the API where an address was found: up to 20 public pages, with the first and last time Tomba saw it there.
- uri
- The public page the address was found on.
- website_url
- The website that page belongs to.
- extracted_on
- When Tomba first found the address there.
- last_seen_on
- The last time Tomba saw it on that page.
- still_on_page
- Whether the address was still on the page at the last visit.
{
"data": [
{
"uri": "https://piedpiper.com/blog/engineering",
"website_url": "piedpiper.com",
"extracted_on": "2024-06-01T09:14:07+01:00",
"last_seen_on": "2025-01-10T17:02:44+01:00",
"still_on_page": true
},
{
"uri": "https://piedpiper.com/newsroom",
"website_url": "piedpiper.com",
"extracted_on": "2023-05-12T11:20:00+02:00",
"last_seen_on": "2025-08-28T06:12:45+02:00",
"still_on_page": false
}
],
"email": "richard@piedpiper.com"
}// 02 · process
How the database is built
- 01
We scan billions of public pages so you don't have to
Our crawlers process over 2 billion URLs every month: company websites, blog posts, PDFs, forums and professional directories. From each page they keep what it shows: work emails, phone numbers, LinkedIn profiles, job titles, company details and the technologies a site runs on.
- Company websitecompany
- Public professional profilelinkedin
- Press releaseemail
- Contact pagephone
- Job postingrole
- Page sourcetech
- 02
AI fills the gaps when direct discovery falls short
When an email isn't publicly listed, our pattern recognition algorithms predict the most likely format: like firstname.lastname@domain.com. Every predicted result includes a confidence score from 0 to 100, so you always know how reliable each contact is.
Richard Hendricks · piedpiper.com- richard.hendricks@12%
- rhendricks@21%
- richard@67%
richard@piedpiper.comlikeliest - 03
Every record is checked before you see it
Each email goes through syntax, DNS and WHOIS, mail server and mailbox (SMTP) checks. Phone numbers are validated for format, country and line type. Then the contact is linked to its LinkedIn profile, job title and company record.
Richard Hendricks · piedpiper.com- richard@piedpiper.comvalid
- +1 650 555 0142mobile
- in/richard-hendrickslinked
- Pied Piper · 11–50enriched
score 98valid - 04
Only 6% of what we find meets our quality bar
We reject 94% of crawled emails. Duplicates, personal webmail addresses, disposable emails and low-confidence results are all filtered out, and invalid phone numbers are deleted. The result is a B2B database you can trust: because quality always beats quantity.
- richard@piedpiper.combusiness
- richard.h@gmail.comwebmail
- x7k2@tempmail.devdisposable
- +1 555 01invalid number
- removed@piedpiper.comremoval asked
// 03 · crawlers
What powers the database
The crawlers do more than find emails: they find and check phone numbers, link LinkedIn profiles and build a record for every company.
// emails
Email pattern recognition
Detects the format each company uses, so Tomba can find an address that isn't published anywhere.
SMTP verification
Asks the mail server whether the mailbox exists before the address reaches you.
Confidence scoring
Every address gets a score from 0 to 100, so you know which ones to trust first.
Personal and generic sorting
Tells people's addresses from role ones like info@ and support@, and leaves personal webmail out.
// phone numbers
// people and linkedin
LinkedIn profile matching
Goes from a LinkedIn profile URL to the person's work email, and returns the profile with each record.
Real-time enrichment
Adds the job title, department, seniority and social profiles to an email address.
Gender and location
Detects gender from first names and stores the country, state, city and ZIP code.
// companies
DNS and WHOIS resolution
Confirms each company's domain is real and active, and keeps its registration data.
Company intelligence
Industry, size, revenue estimate, founding year, headquarters, business phone and social pages for each company.
Technology detection
Finds the tools and platforms a website runs on.
Similar companies
Finds look-alike companies and competitors from a single domain.
// 04 · fields
What a record can hold
// email data
- Professional email addresses
- Email patterns per domain
- Verification status and confidence score
- Source URLs where emails were found
- Discovery and verification timestamps
// person data
- First name, last name, full name
- Job title and department
- Seniority level
- Gender
- LinkedIn and Twitter profiles
- Country
// phone data
- Phone numbers per person and company
- Valid or invalid
- Line type (mobile, landline, VoIP, toll-free)
- Carrier, when known
- Country and time zones
- International, national and E.164 formats
// company data
- Company name and website
- Industry, employee count and revenue estimate
- Headquarters location (city, state, country)
- LinkedIn company page and other social profiles
- Business phone number
- Technologies and tools used
// domain data
- WHOIS registration data
- MX and DNS records
- Accept-all and catch-all status
- Email patterns used
- Total indexed emails per domain
- Domain age and registrar
// 05 · principles
How we handle the data
- 01
Every email comes with a verified public source
All contacts found via Domain Search include where and when we discovered them. The Email Finder clearly marks whether a result is verified or predicted. You always know the origin of your data: no black boxes.
- 02
Stale data is automatically removed
After six months, we remove any contact or company information that no longer has a valid public source. Before removal, we flag it with a Removed label so you are never caught off guard. This keeps our database consistently fresh and reliable.
- 03
Data subjects have full control over their information
Anyone can remove their contact information by claiming their email address. Owners can edit any field associated with their profile. Upon a deletion request, the email and all related data are permanently and irreversibly removed.
- 04
Website owners decide how we index their pages
Our crawler identifies itself with a clear User-Agent and fully respects the robots.txt standard. If you don't want us indexing your site, simply disallow our crawler: we stop immediately.
// 06 · compliance
Data privacy and compliance
Every email in our database is collected from publicly available web pages, on a legitimate-interest basis, with free opt-out for anyone.
GDPR
Business contact data from public web pages, processed on a legitimate-interest basis, with a Data Processing Addendum and EU Standard Contractual Clauses for customers.
CCPA
California residents can request access, deletion and opt-out at any time, and Tomba honours the Global Privacy Control signal.
Easy opt-out
Anyone can remove their data with the Claim tool at app.tomba.io/claim or by email to privacy@tomba.io. Opting out adds the address to a suppression list, so it is not collected again.
Public sources only
Addresses come from publicly accessible web pages, and each one lists up to 20 of the pages it was found on.
Data minimization
We store only what's necessary for B2B prospecting. Personal webmail addresses are excluded. Only 6% of crawled data passes our strict quality filters.
Transparent processing
Our privacy policy, Data Processing Addendum and security policy describe how data is collected, stored and protected.
// 07 · data updates
A fresh refresh every month
Each month's refresh, as the data updates log lists it: when the data was collected and published, and the counts it reported.
- September 2025: 46.5M
- October 2025: 49.4M
- November 2025: 45.4M
- December 2025: 44.9M
- January 2026: 49.5M
- February 2026: 48.8M
- March 2026: 47.8M
- April 2026: 35.2M
- May 2026: 50.3M
- June 2026: 48.7M
- July 2026: 46.0M
- August 2026: 49.2M
- September 2026: 49.8M
| Month | Collected through | Published | Emails | Companies updated | Open in the docs |
|---|---|---|---|---|---|
| September 2026 | Sep 17, 2026 | Sep 29, 2026 | 49.8M | — | |
| August 2026 | Aug 20, 2026 | Sep 5, 2026 | 49.2M | — | |
| July 2026 | Jul 23, 2026 | Aug 7, 2026 | 46.0M | — | |
| June 2026 | Jun 18, 2026 | Jul 1, 2026 | 48.7M | — | |
| May 2026 | May 21, 2026 | Jun 2, 2026 | 50.3M | — | |
| April 2026 | Apr 21, 2026 | May 22, 2026 | 35.2M | — | |
| March 2026 | Mar 17, 2026 | Apr 1, 2026 | 47.8M | — | |
| February 2026 | Feb 19, 2026 | Mar 9, 2026 | 48.8M | — | |
| January 2026 | Jan 25, 2026 | Feb 9, 2026 | 49.5M | — | |
| December 2025 | Dec 17, 2025 | Jan 8, 2026 | 44.9M | — | |
| November 2025 | Nov 19, 2025 | — | 45.4M * | 18.5M | |
| October 2025 | Oct 19, 2025 | — | 49.4M * | 10.5M | |
| September 2025 | Sep 18, 2025 | — | 46.5M * | 12.0M |