Pricing

Rating

Developer

Actor stats

Categories

Share

Business Email & Domain Reputation

What this Actor does

Validate business emails and score domain reputation with allow/review/block verdicts. Wraps the Business Email & Domain Reputation API as an Apify Actor that accepts a list of emails and/or domains and writes scored results to the default dataset.

What data can you get?

Each run writes structured Scored email or domain item rows to the Apify dataset. Common fields include:

How to use Business Email & Domain Reputation

1. Open this Actor in Apify Console.
2. Paste the input JSON below or fill the form fields in the Input tab.
3. Click Start and wait for the run to finish.
4. Open the Dataset tab to preview rows, then export JSON, CSV, Excel, XML, or HTML.
5. For production, schedule the Actor or call it from the Apify API, SDKs, webhooks, or MCP server.

When to use this

• Fraud teams scoring inbound business email signups for disposable, MX, SPF, DMARC, and TLS posture
• Security review pipelines flagging risky vendor domains during procurement onboarding
• Account-takeover defenses gating high-risk allow/review/block verdicts before login
• B2B onboarding flows blocking free-mail and disposable domains without false positives

When NOT to use this

• You need consumer-individual reputation — this is business-domain focused
• You need real-time mailbox-existence checks — service stops at deliverability posture
• You need full WHOIS contact data — RDAP returns registrar/age, not all contact fields

Input example

{
"domains":[
"linear.app"
]
}

Input fields

Provide a list of emails and/or domains to score. At least one of emails or domains is required.

• emails (array, user input): Business or consumer email addresses to validate and score. Each email is checked for syntax, disposable/free provider signals, role account patterns, DNS/MX/SPF/DMARC, website/TLS/RDAP domain signals, and an allow/review/block recommendation.
• domains (array, user input): Bare domains to score without an email local part. Use this for vendor domains, signup domains, company websites, and CRM enrichment when you only know the organization domain.
• apiBaseUrl (string, optional override): Override of the upstream API base URL. Defaults to runtime.baseUrl from service.json.

Output dataset

Each dataset item is one scored email or domain with the upstream API response.

• kind: Whether the scored input is an email or a bare domain.
• input: Original email or domain submitted to the API.
• result: Full upstream API response with classification, recommendation, risk_score, signals, and explanations.

Sample output

How can you use the Business Email & Domain Reputation data?

• Block disposable emails before free-trial or account creation
• Detect free consumer emails in B2B lead forms
• Flag shared role accounts before routing leads to sales
• Check MX, SPF, DMARC, RDAP domain age, website, and TLS signals before outbound campaigns
• Flag newly registered, high-entropy, punycode, parked, and suspicious-TLD domains
• Clean CRM records with lightweight email/domain reputation context
• Screen vendor and marketplace account domains
• Give AI agents a simple email and domain trust tool
• Normalize upstream email, security & data enrichment data into one Apify dataset contract.

API, integrations, and MCP

• Run this Actor from Apify Console, schedules, webhooks, REST API, or the Apify SDKs.
• Connect the Actor to AI agents through the Apify MCP server.
• Export dataset items to JSON, CSV, Excel, XML, HTML, Google Sheets, S3, or downstream BI tools.
• Use the generated INPUT.example.json as the baseline payload for API calls and scheduled runs.

FAQ

How much does it cost to use this Actor?

Per-check pricing: blocking one disposable-domain signup before fraud loss easily covers thousands of legitimate verifications.

Can I use this Actor with the Apify API?

Yes. Use the same input JSON shown above with Apify's REST API, JavaScript SDK, Python SDK, schedules, or webhooks.

Can I use this Actor through an MCP server?

Yes. Add this Actor to the Apify MCP server so AI agents can run it and consume the resulting dataset.

Is it legal to use this data?

Use this Actor only for the allowed use cases: Business email validation, signup risk scoring, lead enrichment, CRM cleanup, outbound email quality checks, vendor screening, marketplace review, and internal security/operations workflows. Do not use it for prohibited workflows: Use as the sole basis for denying legally protected services, illegal surveillance, credential harvesting, bypassing access controls, or collecting private personal data.

Pricing

Per-check pricing: blocking one disposable-domain signup before fraud loss easily covers thousands of legitimate verifications.

Developer notes

Set COMPANY_DOMAIN_RISK_API_KEY as an Apify secret environment variable. The Actor forwards it as X-API-Key to the upstream API. Use apiBaseUrl only for local or staging QA. Production runs default to the deployed API base URL from service.json. For advanced testing, a requests array can call explicit API paths; normal users should use the service-specific fields above.

Run locally

$apify run

Deploy

$apify push

Changelog

• 0.1.0 (2026-04-30) — Initial release: business email/domain reputation scoring with disposable detection, MX/SPF/DMARC, TLS, RDAP age, and allow/review/block verdicts.