Email Scraper

Pricing

Rating

Developer

Actor stats

Categories

Share

A powerful Apify Actor designed to crawl websites and extract email addresses using advanced detection methods. Simply provide a list of starting URLs, configure crawling depth and behavior, and the actor will automatically discover and extract email addresses from across the website—even those hidden behind obfuscation or CloudFlare protection.

⚠️ Pre-Release Version: This is a release candidate. Features are complete but may contain bugs. Feedback and issue reports are welcome!

🚀 Features

• Intelligent Email Discovery: Finds email addresses using multiple sophisticated detection methods, including:
  • Standard text pattern matching
  • Mailto links extraction
  • CloudFlare-protected emails
  • RTL (Right-to-Left) Unicode obfuscation
  • Common text obfuscation patterns
• Configurable Crawl Depth: Control how deep the crawler follows links from your starting URLs (0-10 levels).
• Domain-Focused or Broad Crawling: Choose to stay on the same domain or explore external links.
• Lightweight HTTP Crawling: Fast, efficient method using HTTP requests without the overhead of a browser.
• Anti-Detection Features: Built-in measures to avoid blocking, including user agent rotation, request delays, and robots.txt compliance.
• Proxy Support: Integrates seamlessly with Apify's proxy service for IP rotation and avoiding rate limits.
• Structured JSON Output: Delivers clean, well-structured data with full context about where and how each email was discovered.

📥 Input Parameters

Configure the actor's behavior using these fields in the Apify Console Input tab or via API:

📤 Output Data Structure

The actor outputs one record per unique email address found during the crawl.

Example Output

[
{
"email":"info@example-company.com",
"found_on_url":"https://www.example-company.com/contact",
"start_url":"https://www.example-company.com",
"extraction_method":"mailto_link",
"depth":1
},
{
"email":"support@example-company.com",
"found_on_url":"https://www.example-company.com/about",
"start_url":"https://www.example-company.com",
"extraction_method":"text_standard",
"depth":1
},
{
"email":"sales@example-company.com",
"found_on_url":"https://www.example-company.com/impressum",
"start_url":"https://www.example-company.com",
"extraction_method":"cloudflare_protected",
"depth":2
}
]

📧 Extraction Methods Explained

The actor uses multiple sophisticated techniques to find email addresses, even when websites try to hide them from bots:

💡 Performance Tips

• For small sites: Keep the default settings for optimal speed.
• For large crawls: Use proxy rotation to avoid blocking and rate limits.
• Memory constraints: Set max_concurrent_pages to a lower value (2-5) if running on limited memory.
• Faster crawling: Increase max_concurrent_pages if you have sufficient resources.

🎯 Use Cases

• Lead Generation: Build targeted contact lists for sales and marketing outreach.
• Competitive Research: Discover contact information for companies in your industry.
• Data Enrichment: Enhance existing company databases with email addresses.
• Market Analysis: Gather communication channels for businesses in specific sectors or regions.
• Recruitment: Find contact emails for potential candidates or hiring managers.
• Partnership Development: Identify contact points for potential business partnerships.

🛠️ Maintainer

• Author: Dominic M. Quaiser
• Contact: mail@dominic-quaiser.io
• Website: dominic-quaiser.io

🔧 Troubleshooting

No Emails Found

• Check if the website contains any publicly visible emails
• Try increasing max_depth to crawl more pages
• Verify that stay_on_domain isn't preventing you from reaching contact pages on subdomains
• Check if the website might be blocking the scraper (try enabling proxies)

Actor Running Out of Memory

• Decrease max_concurrent_pages to process fewer pages simultaneously
• Use max_requests_per_run to limit the total crawl size
• Upgrade to a larger memory tier on Apify

Getting Blocked by Websites

• Enable proxy rotation via proxy_configuration
• Increase request_delay_min and request_delay_max
• Enable rotate_user_agents and use_stealth_mode
• Consider enabling respect_robots_txt to honor crawl delays