Hunterio

Hunter.io

Warning

API Key Required: This module strictly requires an active API key to function. If the Hunterio key is missing from your configuration, the module simply will not return its functions for selection. For more details on how modules handle missing keys, refer to Global Settings and API Credentials.

The Hunter.io module leverages the commercial Hunter.io API to perform extensive open-source intelligence (OSINT) gathering on corporate domains. It discovers employee email addresses, validates their deliverability, extracts associated professional profiles, and meticulously links the original source URLs where the data was scraped.

Data Source: Hunter.io

Capabilities

The module accepts Domains (and optionally Organizations, if enabled in your network settings) as input. The scope of the search—including API pagination limits, target departments, and specific seniority levels—is highly customizable. For comprehensive instructions on adjusting these search filters, refer to the Network Configuration page. Based on these parameters, the module extracts the following deep intelligence:

Domain Intelligence

• Corporate Details: Extracts the formal Organization name and the standard corporate Email Pattern (e.g., {first}.{last}@example.com).
• Domain Context: Identifies and flags if the target is an Accept-All Domain (catch-all), a Disposable Email Domain, or a generic Webmail Provider.
• Linked Infrastructure: Extracts other domains owned by or linked to the target organization. These are returned as new Domain nodes, automatically tagged with Linked and evaluated against your Scope Boundaries.

Email & Person Discovery

For every discovered email address, the module generates a rich web of interconnected data:

• Email Node: Emits the email address, automatically attaching its classification (e.g., "Personal email" or "Generic email").
• Deliverability: Attaches a Confidence Score property and the latest Verification Status (e.g., Valid, Invalid, Accept All) alongside the verification date.
• Person Node: Automatically extracts the user's first and last name, creating a new Person node explicitly linked as the source of the email address.
• Professional Profile: Enriches the Person node with extracted corporate metadata, including their Position, Department, and Seniority.
• Social & Contact Links: Discovers and links the user's Phone Number, as well as social profiles (LinkedIn and Twitter URLs), returning them as connected URL nodes marked with the Social tag.

Data Provenance (Scrape Sources)

A standout feature of Hunter.io is its transparency regarding where data was found on the public web. The module rigorously parses this:

• Source Grouping: Creates a central "Sources for..." node for each email to keep the graph organized.
• Specific Endpoints: Extracts the exact URL where the email was scraped.
• Source Domains: Extracts the root domain of the scrape source (e.g., github.com or a news site), tagged as Scrape and checked for Out of Scope (see Scope Boundaries).
• Timestamps: Attaches critical OSINT timestamps, including Extracted on and Last seen. It also emits a Still on page status property if the email is confirmed to still be live on that specific URL.

Preflight Checks & Quota Management

The Hunter.io API uses a strict credit-based system. To prevent wasted execution time:

• Account Preflight: Before initiating any domain searches, the module performs a single preflight query to the /v2/account endpoint. It calculates your exact remaining search credits (available - used).
• Graceful Halting: If your API key is invalid, or if your credits are exhausted, the module immediately halts execution before sending search queries. It emits an informational property (Hunter.io API quota exceeded or credits exhausted) to your graph, preventing the module from wasting execution time on API requests that would simply be rejected.