Business Email & Domain Reputation
Pricing
Pay per usage
Business Email & Domain Reputation
Under maintenanceValidate 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.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
jts
Actor stats
0
Bookmarked
2
Total users
1
Monthly active users
4 days ago
Last modified
Categories
Share
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.
Input example
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.
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
Deploy
