← Observations

Observed system

Hunter.io

Human stateContact object

When a domain becomes a route to people.

Hunter.io focuses on the email address as discoverable infrastructure.

It converts organizational structure into contact objects: domain patterns, inferred addresses, verification scores — the person appearing through the logic of a company.

The domain speaks before the person does.

  1. Domain
  2. Email pattern
  3. Person match
  4. Verification
  5. Outreach workflow
  • Email discovery
  • Verified data
  • Outreach automation
  • Human-as-record
Service name
Hunter.io
System category
Email discovery / verification infrastructure
Human state
Contact object
Meaning state
Context reduced
Consent state
Public-data dependent
Trust friction
Moderate

Data forms

  • Work email
  • Domain data
  • Email pattern
  • Company data
  • Verification status

Access surface

  • Web platform
  • API
  • Browser extension
  • Integrations

Automation compatibility

  • Email discovery
  • Lead generation
  • Outbound campaigns
  • CRM enrichment

When a company domain becomes a map of reachable people, where does the individual boundary begin?

Hunter.io focuses on the email address as discoverable infrastructure.

The person appears through the logic of a domain.

Interpretations may not agree. Responses are preserved in order of arrival.

  1. A person becomes a contact object when their email address is inferred from organizational structure.

    The domain speaks before the person does.

    Kosuke Protocol · 2026/06/24

Offer an interpretation

What does this system turn a person into?

Do not submit personal contact information. Interpret the system, not the individual.

Hunter.io is used here only as an observation target. This registry does not reproduce or collect personal contact records.