🧭 Domain Lead Qualifier – Email Readiness & WHOIS Intelligence API (Bulk Enrichment)

Upload domains → get age, registrar, DNS auth & email-sendability score. Built for SDRs, lead-gen agencies & list vendors.

Domain Lead Qualifier helps SDR teams and growth operators qualify domains before outreach using email readiness and deliverability signals, WHOIS/RDAP registration data, TLS status, and hosting intelligence. Run it from the Apify Console or automate it via API to score domains at scale and avoid low-quality or risky leads.

⭐ Key Features

• 🎯 Bulk domain enrichment for lead qualification — one result per domain
• 📬 Email readiness & deliverability checks — MX, SPF, DMARC + disposable detection
• 🧾 WHOIS / RDAP intelligence — domain age, registrar, expiry (with fallback)
• 🔒 TLS validation — certificate status and days to expiration
• 🌐 Hosting context — resolved IP, ASN, hosting organization
• 🧮 Email-readiness score (0–100) — 🟢 high / 🟡 medium / 🔴 low, fully configurable

💡 Why use this Actor?

• Avoid bad leads — filter domains with no MX, disposable email, or weak auth
• Protect deliverability — catch SPF/DMARC gaps before campaigns go out
• Audit lead vendors — objectively score purchased lists at scale
• Save SDR time — prioritize outreach to high-scoring domains only

📥 Input

Configure the Actor from the Input tab. Only domains is required — everything else is optional.

domains (required)

Domains to enrich and qualify.

• URLs are automatically normalized to domains

concurrency (optional)

Controls how many domains are processed in parallel.

• Default: 10
• Higher values are faster but use more memory

scoring (optional)

Customizes how the email_score (0–100) is calculated.

• If omitted, the Actor uses a production-ready default scoring model
• Use this only if you want to change how domains are ranked

Minimal example (most users)

{
    "domains": ["example.com", "google.com"]
}

✅ Uses default concurrency and default scoring. This is enough for most SDR, lead-gen, and list QA workflows.

Full example (explicit defaults shown)

The example below shows all default values. You do not need to include this unless you want to override something.

{
    "domains": ["example.com", "google.com"],
    "concurrency": 10,
    "scoring": {
        "weights": {
            "mx": 30,
            "spf": 15,
            "dmarc": 10,
            "domainAge": 25,
            "tls": 15,
            "notDisposable": 5
        },
        "thresholds": {
            "high": 70,
            "medium": 40
        }
    }
}

💡 Partial overrides are supported. You can change only thresholds.high (for example) and keep all default weights.

📤 Output

Each input domain produces one result object in the default dataset.

{
    "domain": "example.com",
    "has_mx": true,
    "has_spf": true,
    "has_dmarc": true,
    "tls_valid": true,
    "is_disposable": false,
    "email_score": 100,
    "email_score_label": "high",
    "email_score_emoji": "🟢",
    "resolved_ip": "104.18.27.120",
    "domain_registered_at": "1995-08-14",
    "expires_at": "2026-08-13",
    "registrar": "RESERVED-Internet Assigned Numbers Authority",
    "domain_age_days": 11101,
    "tls_expires_in_days": 71,
    "hosting_cms": "unknown",
    "asn": 13335,
    "hosting_org": "Cloudflare"
}

Key fields to watch

• email_score, email_score_label, email_score_emoji — primary qualification signals
• has_mx, is_disposable — fast exclusion filters
• domain_age_days, expires_at, registrar — trust and risk indicators
• tls_valid, tls_expires_in_days — maintenance and security signals

Per-domain lookup failures don’t crash the run. Partial results may include *_error fields.

🧠 Tips & Best Practices

• Interpret the score

  • 🟢 High: safe for outreach
  • 🟡 Medium: review or enrich further
  • 🔴 Low: exclude from cold email

• Fast exclusion rules

  • has_mx = false
  • is_disposable = true
  • email_score_label = "low"

• When to customize scoring

  • Don’t customize for general B2B qualification or list QA
  • Customize if you target very new startups, need strict compliance, or want higher auth requirements

• Performance tuning

  • Start with concurrency = 10
  • Increase only if runs are slow and memory usage is low
  • Reduce concurrency first if you see timeouts

🔌 Integrations

This Actor fits naturally into automated lead-qualification workflows:

• Actor-to-Actor: Trigger this Actor from another Actor or Task, or pass its dataset to a downstream Actor for filtering, enrichment, or export.
• Automation tools: Run it from Zapier, Make, n8n, or similar platforms using the same JSON input as in Apify Console.
• Data pipelines: Connect the output dataset to integration-ready Actors to upload results to databases, spreadsheets, or internal systems.

See Apify’s integration docs for setup details.

🚀 Get Started

Upload a list of domains and get email-readiness scores fast. Ideal for SDR teams, lead-gen agencies, and anyone qualifying leads before outreach.

🛟 Support

This Actor is actively maintained. Need help or want to customize it?

• 📬 Contact the developer
• 🐞 Report a bug
• ✨ Request a feature