Email Address Validator (2025)

Overview

This actor validates email addresses to improve data quality and campaign deliverability. It checks email syntax, domain configuration, and mailbox existence, then provides a quality score and a clear send/don't-send recommendation.

Key Features

• Multi-layered Validation: Checks format, domain MX records, and SMTP server response.
• Quality Scoring: Assigns a 0-100 score to each address.
• Clear Classification: Identifies valid, risky, and invalid emails with , ️, indicators.
• Email Typology: Flags disposable, free, or role-based (e.g., support@) addresses.
• Typo Suggestions: Offers corrections for common misspellings in domains or usernames.

How to Use

Provide a list of email addresses as input. The actor processes each one through its validation pipeline and returns structured results for analysis.

Input/Output

Input: Pass an array of email addresses via the emails field in the input JSON.

{
  "emails": [
    "contact@company.com",
    "info@example.com",
    "john.doe@gmail.com",
    "support@nonexistentdomain123.com"
  ]
}

Output: For each email, you receive a detailed result object.

{
  "email": "security@company.com",
  "domain": "company.com",
  "validation_status": "Okay to Send",
  "validation_analysis": "Accepted"
}

Understanding the Output

The validation_status is the primary actionable field:
* ** Okay to Send: Email is valid and can receive messages.
* ️ Risky to Send: Potential deliverability issues (e.g., catch-all domain, temporary mailbox).
* ** Do not Send: Email is invalid, non-existent, or uses a disposable domain.

These statuses are determined by several checks:
* Format: Validates basic email syntax.
* MX Records: Confirms the domain can receive mail.
* SMTP: Verifies the specific mailbox exists.
* Catchall: Detects if the domain accepts all addresses, which can be a risk indicator.

Use Cases

• Cleaning email lists before marketing campaigns to reduce bounce rates.
• Validating customer emails in a CRM or during data migration.
• Screening email addresses collected via lead generation forms.
• Verifying user registration emails to prevent fake accounts.