X Email Scraper

X Email Scraper - Public Contact Emails from X and Twitter Profiles

The X Email Scraper is an Apify Actor that collects publicly indexed contact emails belonging to X accounts. You supply keywords; it returns a structured dataset of leads.

The X Email Scraper works by running site:x.com and site:twitter.com searches through the Apify GOOGLE_SERP proxy and parsing addresses out of the result blocks. Both domains are covered, because Google's index still holds a decade of twitter.com URLs.

The X Email Scraper does not log into X, does not use the X API and does not open x.com. No browser, no JavaScript rendering, no authentication, no cookies.

Everything the X Email Scraper returns already exists in Google's public index: titles, snippets and site labels. If a founder wrote hire me: me@gmail.com in a bio Google crawled, this Actor can surface it.

That makes it an X email extractor - what people still search for as a Twitter email scraper - for keyword-driven contact discovery. You start from a niche or job title, not from a list of handles.

---

Key Features

Feature	What it does
Dual-domain coverage	The X Email Scraper searches both x.com and legacy twitter.com results
Keyword-driven search	Start from a role, niche or community, not from a list of handles
Query expansion	Each keyword x domain pair runs as base, quoted, intitle: and one variant per modifier
Domain filtering	Only emails on the domains you list (@gmail.com, @yahoo.com, ...) are kept
Obfuscation handling	Understands name [at] domain [dot] com, name (at) domain, name @ domain.com, domain .com, zero-width characters and the full-width at sign
Junk filter	Rejects placeholders such as email@, yourname@, test@, xxx@ and single-character locals
Boundary-correct matching	@gmail.com never matches inside @gmail.company or @gmail.com.br
Global deduplication	One row per unique email across every query and every page
Concurrency	An asyncio worker pool runs several queries in parallel with a shared stop signal
Retry logic	Up to 3 attempts per page, exponential backoff, a fresh proxy session per request
Block detection	CAPTCHA, "unusual traffic" and consent pages are detected and retried, never counted as empty
Resumable state	Progress lives in the key-value store, keyed by a hash of your input
Fallback parser	If Google's markup changes, a run degrades to "emails without account details", not "no emails"
Live dataset writes	Each lead reaches the Apify dataset the moment it is found

The X Email Scraper parser locates each <h3> title, then the smallest surrounding block. It does not depend on Google's CSS class names, which is why the X Email Scraper tolerates most SERP layout changes.

---

How the X Email Scraper Works

The X Email Scraper pipeline is short, deterministic and auditable - every row stores the exact query that produced it.

1. Read input. Keywords, location, email domains and limits are validated.
2. Build queries. The X Email Scraper composes site:x.com and site:twitter.com queries, e.g. site:x.com indie hacker "@gmail.com" "Berlin".
3. Expand queries. Base queries run first, then quoted, intitle: and one variant per query modifier.
4. Fetch search results. Pages are retrieved asynchronously with aiohttp through the Apify GOOGLE_SERP proxy.
5. Parse structurally. Each result block is isolated around its <h3> heading.
6. Extract emails. A domain-filtered regex pulls addresses from the block text after normalisation.
7. Deduplicate and push. Every new lead is written straight to the dataset as structured data.

Pagination per query is capped by maxPagesPerQuery. A query stops early once several consecutive pages produce no new email, so the crawler does not spend proxy calls on an exhausted result set.

Blocked or failed queries are re-queued once at the end of the run. The X Email Scraper then logs a summary: pages fetched, blocked pages, retries and emails per page.

---

What Data Does It Extract?

Every X Email Scraper dataset item pairs an email with whatever account metadata Google exposed, plus provenance so you can trace the address back to its query.

Profile and status results usually expose a handle, which the X Email Scraper converts into a username and a canonical profileUrl such as https://x.com/handle. Handles are short - up to 15 characters - so they map cleanly.

Hashtag, explore and search-result pages do not expose a handle. Those rows carry accountName with username: null and an empty profileUrl, while the email and snippet are still returned. That is a Google limitation, not a defect.

---

Input Schema for the X Email Scraper

Field	Type	Default	Meaning
keywords	array (required)	["founder", "indie hacker"]	Search terms describing the accounts you want (niche, job title, industry)
location	string	""	Optional location phrase added to every query
customDomains	array	["@gmail.com", "@yahoo.com"]	Only emails on these domains are kept; the leading @ is optional
maxEmails	integer 1-10000	20	Stop after this many unique emails
countryCode	string	""	Two-letter country for the search proxy (US, GB, DE...)
expandQueries	boolean	true	Search each keyword x domain pair in several phrasings
queryModifiers	array	["email", "contact", "inquiries", "hire", "work with me"]	Extra words combined with each keyword when expansion is on
maxPagesPerQuery	integer 1-50	30	Page cap per query
maxConcurrency	integer 1-20	5	Parallel queries

The default modifiers are tuned for X's professional bio culture. hire and work with me are the phrases freelancers and founders actually put beside an address, which is why the X Email Scraper ships with them.

JSON input example

{
  "keywords": ["indie hacker", "solidity developer", "growth marketer"],
  "location": "",
  "customDomains": ["@gmail.com", "@proton.me"],
  "maxEmails": 500,
  "countryCode": "US",
  "expandQueries": true,
  "queryModifiers": ["hire", "work with me", "contact", "inquiries"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}

---

Output Schema and Structured Data Fields

Every item the X Email Scraper writes carries all 14 fields below, so a CSV, XLSX or JSON export always has identical columns.

Field	Meaning
network	Platform name
keyword	The keyword that produced the lead
query	The exact Google query used
title	Raw result title
accountName	Account label Google prints (handle or display name)
fullName	Display name parsed from a profile-style title; empty for post snippets
username	URL-safe handle when X exposes one; otherwise null
profileUrl	Canonical account URL when a handle is known; otherwise empty
url	Direct platform link when exposed, else the profile URL
description	Bio or post snippet, cleaned of labels and engagement counters
email	Lower-cased email address
emailDomain	The matched domain (e.g. @gmail.com)
possiblyTruncated	true when Google's snippet ellipsis touched the email - verify before sending
foundAt	ISO 8601 UTC timestamp

JSON output example

[
  {
    "network": "X",
    "keyword": "indie hacker",
    "query": "site:x.com indie hacker \"work with me\" \"@gmail.com\"",
    "title": "Tomas Beck (@tomasbuilds) / X",
    "accountName": "tomasbuilds",
    "fullName": "Tomas Beck",
    "username": "tomasbuilds",
    "profileUrl": "https://x.com/tomasbuilds",
    "url": "https://x.com/tomasbuilds",
    "description": "Building small SaaS in public. 3 products, 1 developer. Work with me: tomas.builds@gmail.com",
    "email": "tomas.builds@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-03-18T13:55:29Z"
  },
  {
    "network": "X",
    "keyword": "growth marketer",
    "query": "site:twitter.com growth marketer \"hire\" \"@gmail.com\"",
    "title": "#growthmarketing - X",
    "accountName": "X",
    "fullName": "",
    "username": null,
    "profileUrl": "",
    "url": "https://x.com/hashtag/growthmarketing",
    "description": "for freelance work hire.aditi.growth@gmail.com ...",
    "email": "hire.aditi.growth@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": true,
    "foundAt": "2026-03-18T13:56:41Z"
  }
]

The second row is the honest case. Google served a hashtag page rather than a profile, so there is no handle to build a profileUrl from, and the snippet ellipsis touched the address.

---

How to Use the X Email Scraper in Five Steps

1. Open the Actor and confirm your account has Apify proxy access. The GOOGLE_SERP proxy is required.
2. Enter 3-10 keywords. Communities beat categories: indie hacker and solidity developer outperform tech.
3. Choose email domains. X skews technical, so add @proton.me, @pm.me and @hey.com alongside @gmail.com.
4. Set maxEmails. Start at 20 to check the niche, then raise it.
5. Run, then export. Download the dataset as CSV, JSON or XLSX, or pull it via the Apify API into your CRM.

Add a location only when geography actually matters. Much of X is location-agnostic, and an unnecessary location phrase narrows the X Email Scraper's search results for no gain.

---

X Email Scraper Use Cases

Use case	Who it is for	How the X Email Scraper helps
Founder and startup outreach	B2B SaaS sales	Build lists of founders and indie hackers publishing a contact address
Developer relations	DevRel and DevTool teams	Reach engineers by stack keyword and community
Freelancer sourcing	Agencies and studios	Find designers and developers advertising work with me
Tech recruiting	Talent teams	Search role keywords across X and legacy Twitter results
Newsletter and media partnerships	Publishers	Contact writers who list an inbox in their bio
Web3 and crypto outreach	Protocol and NFT teams	Target on-chain communities where X is the default channel
Investor and angel research	Fundraising founders	Identify angels who publish a public email
CRM enrichment	RevOps teams	Feed structured data straight into an existing pipeline

Founders rarely post in one place. Pair this Actor with the LinkedIn Email Scraper for the professional side, and the Bluesky Email Scraper or Mastodon Email Scraper for accounts that migrated off X.

---

Why Use This Actor for X Contact Discovery

Most Twitter email scraper tools need API credentials, a scraping session or a list of profile URLs. The X Email Scraper needs none of that - it queries Google and parses what is already public.

Because the X Email Scraper never touches x.com, there is no login, no API tier to pay for and no session to maintain. Its only dependency is Apify's search proxy.

The extraction layer is where the value sits. Normalisation, obfuscation handling, the junk filter, boundary-correct domain matching and soft-wrap repair remove most of the noise naive regex email scraping produces.

Bio obfuscation is endemic on X. Users write me [at] domain [dot] com to dodge bots, and the X Email Scraper normalises those variants - including the full-width at sign and zero-width characters - into a clean address.

---

Limitations

Read this before planning a campaign around the X Email Scraper.

• Public index only. It finds accounts whose email is publicly visible in Google's index. Emails only in DMs, images or link-in-bio pages are out of reach.
• Google's ~300-result cap. A single query returns roughly 300 results at most. Query expansion exists to work around that ceiling, so keep expandQueries on for volume.
• possiblyTruncated. When Google's snippet ellipsis touched an address, the row is flagged. Verify those rows before sending.
• Handle availability. username and profileUrl are populated only when Google's result exposes a handle. Hashtag and explore pages return accountName instead.
• Apify proxy required. The X Email Scraper cannot run without Apify GOOGLE_SERP proxy credentials.
• Free-plan cap. Free Apify plans are capped at 100 emails per run. Paid plans are uncapped.
• No volume guarantee. Results vary with keywords, domains, location and what Google has indexed. Nothing is guaranteed, verified or real-time.

The X Email Scraper is not affiliated with, endorsed by or officially supported by X Corp. Use the output in line with GDPR, CAN-SPAM and local marketing law.

---

Related Actors

The X Email Scraper shares its engine and output schema with every Actor below, all part of the Social, Creator & Community family.

Actor	What it collects
X Email and Phone Number Scraper	Emails and phone numbers from X
X Phone Number Scraper	Public phone numbers from X
Behance Email Scraper	Public contact emails from Behance
Bigo Live Email Scraper	Public contact emails from Bigo Live
Bluesky Email Scraper	Public contact emails from Bluesky
Bumble Email Scraper	Public contact emails from Bumble
Clubhouse Email Scraper	Public contact emails from Clubhouse
Dailymotion Email Scraper	Public contact emails from Dailymotion
DeviantArt Email Scraper	Public contact emails from DeviantArt
Discord Email Scraper	Public contact emails from Discord
Dribbble Email Scraper	Public contact emails from Dribbble
Facebook Email Scraper	Public contact emails from Facebook
Goodreads Email Scraper	Public contact emails from Goodreads
Hinge Email Scraper	Public contact emails from Hinge
Instagram Email Scraper	Public contact emails from Instagram
KakaoTalk Email Scraper	Public contact emails from KakaoTalk
Kick Email Scraper	Public contact emails from Kick
Lemon8 Email Scraper	Public contact emails from Lemon8
Likee Email Scraper	Public contact emails from Likee
LINE Email Scraper	Public contact emails from LINE
LinkedIn Email Scraper	Public contact emails from LinkedIn
Mastodon Email Scraper	Public contact emails from Mastodon
Medium Email Scraper	Public contact emails from Medium
Mixcloud Email Scraper	Public contact emails from Mixcloud
Patreon Email Scraper	Public contact emails from Patreon
Pinterest Email Scraper	Public contact emails from Pinterest
Quora Email Scraper	Public contact emails from Quora
Reddit Email Scraper	Public contact emails from Reddit
Rumble Email Scraper	Public contact emails from Rumble
Snapchat Email Scraper	Public contact emails from Snapchat
SoundCloud Email Scraper	Public contact emails from SoundCloud
Substack Email Scraper	Public contact emails from Substack
Telegram Email Scraper	Public contact emails from Telegram
Threads Email Scraper	Public contact emails from Threads
TikTok Email Scraper	Public contact emails from TikTok
Tinder Email Scraper	Public contact emails from Tinder
Tumblr Email Scraper	Public contact emails from Tumblr
Twitch Email Scraper	Public contact emails from Twitch
Vimeo Email Scraper	Public contact emails from Vimeo
VK Email Scraper	Public contact emails from VK
WeChat Email Scraper	Public contact emails from WeChat
Weibo Email Scraper	Public contact emails from Weibo

Example: Building a Founder Outreach List

Here is a realistic X Email Scraper run. You sell developer tooling and want 400 technical founders with a public inbox.

Set keywords to ["indie hacker", "technical founder", "bootstrapped SaaS"], customDomains to ["@gmail.com", "@proton.me"], countryCode to US and maxEmails to 400.

The X Email Scraper builds base, quoted, intitle: and modifier variants per keyword across both x.com and twitter.com, then paginates the search results with five parallel workers. Rows stream into the dataset live.

Sort the X Email Scraper dataset by possiblyTruncated, verify the flagged rows manually, then load the rest into your sequencer. Run the same keywords through the Reddit Email Scraper to reach the same builders where they post long-form.

---

X Email Scraper FAQ

Does the X Email Scraper log into X? No. It never authenticates, never opens x.com and never uses the X API. Every field comes from Google's public search results.

Does it cover old twitter.com links too? Yes. The X Email Scraper searches site:x.com and site:twitter.com, so legacy indexed profiles and posts are included.

Where do the X Email Scraper emails actually come from? From titles, snippets and site labels Google already publishes for indexed X pages - usually bios and posts where the account owner wrote the address themselves.

Why do some rows have no username or profileUrl? Because Google's result exposed no handle - typically hashtag, explore or search pages. Those rows still include accountName, the email and the snippet.

What does possiblyTruncated: true mean? Google's snippet ellipsis touched the address, so it may be cut short. Treat those as leads to verify rather than send-ready contacts.

How many emails can one X Email Scraper run return? Free Apify plans stop at 100 emails per run. Paid plans are uncapped and bounded only by maxEmails and what Google has indexed.

Why does a single query not return thousands of results? Google caps one query at roughly 300 results. Query expansion multiplies keyword x domain x phrasing so the X Email Scraper reaches past that ceiling.

Do I need a proxy to run the X Email Scraper? Yes. It requires the Apify GOOGLE_SERP proxy and will not run without Apify proxy credentials.

Can it read emails from protected or private accounts? No. If the content is not in Google's public index, the X Email Scraper cannot see it.

Which email domains work best on X? @gmail.com dominates, but the technical audience means @proton.me, @pm.me and @hey.com are worth adding to customDomains.

Can I resume an interrupted run? Yes. Progress is saved in the key-value store, keyed by a hash of your input, and persists on Apify's PERSIST_STATE, MIGRATING and ABORTING events.

Is scraping X emails legal? The Actor collects only publicly indexed information, but how you use it is your responsibility. Follow GDPR, CAN-SPAM and local rules on unsolicited outreach.

How do I get more leads from one niche? Add query modifiers, widen customDomains, raise maxPagesPerQuery and run adjacent community keywords rather than one broad term.

---

Support

Questions about the X Email Scraper, bug reports or a custom build? Email neurodata.apify@gmail.com.