Email Validation In MailerLogic: How It Works

Email validation in MailerLogic helps you check whether an email address is safe to send to before you email it. This reduces bounces, protects your sender reputation, and improves overall deliverability.

This article explains how MailerLogic email validation works, what happens behind the scenes, and how to use it efficiently.

Does Email Validation Work Automatically?

No.

Email validation in MailerLogic is on-demand only.

This means validation happens only when you request it, either through the API or a batch request. MailerLogic does not automatically scan your email lists or validate addresses in the background.

Each time you call the validation API, MailerLogic performs a fresh validation and returns the result immediately.

Does MailerLogic Remember Validated Emails?

No. MailerLogic does not cache or reuse previous validation results.

Even if you validate the same email address multiple times, each request is treated as a new validation and counts toward your monthly validation limit.

Why this matters:

• Email addresses can become invalid over time

• Domains can expire or change mail servers

• Disposable email domains are updated frequently

Because of this, MailerLogic always performs live checks to ensure accuracy.

What Happens During Email Validation?

When you validate an email address, MailerLogic performs several real-time checks to determine whether it’s safe to send to.

These checks include:

• Syntax check
  Confirms the email address format is correct

• Disposable email detection
  Checks against a large and frequently updated list of disposable and temporary email domains

• Role-based detection
  Identifies role addresses like admin@, support@, or info@

• DNS and mail server checks
  Verifies that the domain exists and can receive emails

• Risk score calculation
  Combines all signals into a risk score to help you decide whether to send

Each validation typically takes only a few hundred milliseconds and uses one validation credit.

What MailerLogic Stores (And Why)

MailerLogic keeps a validation history for audit and reporting purposes only.

This includes:

• Which email was validated

• When it was validated

• The validation result

• Which account performed the validation

This history is used for:

• Usage tracking and billing

• Compliance and audit needs

• Analytics and reporting

It is not used to skip or shortcut future validations.

Why MailerLogic Does Not Cache Results

Caching validation results can lead to inaccurate data. Email validity is not permanent.

For example:

• A domain that worked last month may no longer accept emails

• New disposable domains are added regularly

• DNS records can change at any time

To ensure accuracy and fairness across all customers, MailerLogic follows the industry standard of performing fresh validation every time.

How Validation Quotas Work

Each email validation uses one credit from your monthly quota.
Your quota depends on your MailerLogic plan and resets automatically every month.

You can check your usage and remaining validations anytime from your dashboard or via API.

When to Use the API

Common use cases include:

• Validating emails during user signup

• Checking contacts before adding them to your list

• Cleaning lists before sending campaigns

• Periodic list hygiene checks

API Endpoint

POST

/api/v1/address/validate

This endpoint validates one email address per request.

Authentication

All API requests must include your API key in the request headers.

Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

Single Email Validation Example

Request

{
  "email": "user@example.com"
}

Response

{
  "email": "user@example.com",
  "valid": true,
  "deliverability": "deliverable",
  "is_disposable": false,
  "is_role_based": false,
  "risk_score": 5,
  "checks": {
    "syntax": { "valid": true },
    "dns": { "valid": true, "has_mx": true },
    "disposable": { "is_disposable": false }
  }
}

Understanding the Response

Key Fields Explained

• valid
  Indicates whether the email passed validation checks.

• deliverability
  Shows whether the email is safe to send to (deliverable, risky, or undeliverable).

• is_disposable
  Identifies temporary or throwaway email services.

• is_role_based
  Detects role-based addresses like admin@, support@, or info@.

• risk_score
  A numeric score (0–100). Higher values mean higher delivery risk.

Batch Email Validation

To validate multiple email addresses in one request, use the batch endpoint.

Endpoint

POST /api/v1/address/validate/batch

Request Example

{
  "emails": [
    "user1@example.com",
    "user2@example.com",
    "user3@example.com"
  ]
}

Each email in the batch consumes one validation credit.

Credit Usage & Quotas

• Every validation request uses 1 credit per email

• Validating the same email multiple times will use credits each time

• Credits reset monthly based on your plan

You can check your usage using:

GET /api/v1/address/validate/quota

Best Practices For Using Email Validation

• Validate emails at signup or import

• Avoid validating the same email repeatedly

• Revalidate only when necessary (for example, after 30 days)

• Use batch validation for large lists

• Store validation results on your side

If you want to avoid re-validating the same email multiple times, implement client-side caching in your application.

Common Errors

The Email Validation API gives you fast, real-time insight into email quality. Each request performs a fresh validation and counts toward your quota, making it reliable, accurate, and predictable. For best results, combine the API with smart usage and client-side result storage.