- How does deterministic DOM extraction avoid email hallucination?
- It relies strictly on exact RFC 5322 regular expression matching and mailto: protocol parsing directly from HTML text, guaranteeing 100% verified existence on the target page.
- Does this crawler respect website rate limits and polite crawling standards?
- Yes. The crawler restricts traversal to same-origin internal links, limits recursion depth, and throttles requests to prevent server strain.
- Can I export the extracted contact lists to CSV or JSON?
- Yes. You can copy emails as comma-separated lists or download them as structured CSV and JSON files formatted with department tags.
- Which corporate departments are automatically categorized?
- Executive, Sales, Human Resources, Engineering, Customer Support, Legal, and Press/Media based on page context and role prefix patterns.
- How does this tool extract website emails without using AI or LLM models?
- The engine uses a deterministic three-stage pipeline: First, it loads rendered HTML into Cheerio to isolate all anchor tags using the mailto: protocol. Second, it strips non-text scripts and media tags, running an RFC 5322 compliant regular expression over text nodes. Third, it executes rule-based de-obfuscation algorithms that recognize common obfuscation patterns like name [at] domain.com and HTML character entities, ensuring complete extraction without dispatching data to external AI models.
- How are email addresses categorized into corporate departments and units?
- Classification operates deterministically using structural and semantic heuristics. The engine first evaluates local-part prefix dictionaries (e.g. sales@, hr@, support@, ceo@, legal@, dev@). When prefixes are ambiguous, Cheerio examines surrounding DOM card containers, nearest headings (h2, h3), sibling role attributes, and page path slugs (/team, /contact, /kariyer, /leadership) to assign the contact to the correct corporate unit.
- Does the crawler navigate across external domains or outgoing links?
- No. The crawler operates under strict same-origin isolation. It only crawls internal hyperlinks matching the root hostname of your target URL. External domains, advertiser links, and third-party partner portals are filtered out to ensure privacy, speed, and polite network crawling.
- What safeguards protect against Server-Side Request Forgery (SSRF)?
- Our backend resolves the target domain via DNS and verifies that the resulting IP does not belong to private RFC 1918 subnets (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), loopback addresses (127.0.0.1, localhost), link-local cloud metadata endpoints (169.254.169.254), or non-HTTP protocols.
- How does the tool identify individual personnel names and roles?
- If an email conforms to personal naming patterns (such as [email protected] or first_last@), the system automatically parses and capitalizes the individual's full name. Additionally, it reads sibling heading tags and CSS role descriptors (such as .title, .designation, or .role) within the containing team member card.
- What export options are available for the discovered email addresses?
- You can export discovered contacts with one click into comma-separated lists, newline-separated strings for email campaigns, structured CSV spreadsheets (including Name, Department, Role, Email, and Source URL), or raw JSON files for programmatic API pipelines.