ILHAM AUSTRALIA™

ILHAM EMAIL VALIDATION

Know an email before you trust it.

Validate email addresses in real time with syntax, DNS, MX, SMTP, disposable, catch-all, role and sender-risk checks — backed by a database of 1M+ known spam, junk, scam and phishing senders.

iev-validator
IEV EMAIL VALIDATION ENGINE
─────────────────────────────────────
iev@api:~$
EMAIL VERIFIED
—
Syntax validMX foundSMTP passedNo disposableLow risk
API RESPONSE200 OK
1M+Known sender records
SMTPMailbox-level verification
DNS + MXMail infrastructure checks
APIBuilt for busines
Validation engine

JUST checking an @ symbol.

A valid email format doesn't mean the address is deliverable, useful or safe to accept. IEV checks the address, its domain, its mail infrastructure and known sender intelligence.

Syntax validation

Check the structure of the address before sending it anywhere or storing it in your database.

Domain & DNS

Check whether the domain exists and whether its DNS configuration supports email delivery.

MX checking

Find the mail exchange servers responsible for receiving messages for the domain.

SMTP verification

Check mailbox-level signals through the receiving mail server without sending an actual email.

Disposable detection

Detect temporary and throwaway email addresses commonly used for unwanted signups and low-quality submissions.

Catch-all detection

Identify domains that accept mail for addresses that may not have an individually verifiable mailbox.

Role detection

Flag shared addresses such as info@, sales@, support@ and admin@.

Typo & gibberish detection

Identify suspicious or malformed addresses and common domain mistakes before they become bad data.

Risk signals

Combine technical validation with sender intelligence to identify addresses that deserve extra attention.

IEV sender intelligence
1M+

sender records checked during validation

spam_sender
junk_sender
scam_sender
phishing_sender
abuse_sender
Sender intelligence

Don't just check the mailbox.

Some addresses can pass basic technical checks and still be unwanted. IEV checks the address against a database containing more than 1 million spam, junk, scam and phishing sender records.

This gives your application another signal when deciding whether an address should be accepted, flagged or rejected.

Spam sender detectionIdentify known spam-related sender records.
Scam & phishing signalsCheck against known problematic sender records.
Junk sender intelligenceFilter addresses associated with unwanted traffic.
Shopify-focused protectionUseful for stores receiving public form submissions.
Checks

Every signal has a purpose.

IEV gives your application individual validation signals so you can decide how strict your own acceptance rules should be.

Syntax

Validate the email structure.

Domain

Check whether the domain exists.

MX

Check mail exchange records.

SMTP

Check receiving mail-server signals.

Disposable

Detect temporary email providers.

Catch-all

Detect accept-all mail domains.

Role account

Detect shared departmental addresses.

Sender risk

Check IEV sender intelligence.

Built for real websites

Validate before you store.

Put IEV between your users and your database. Validate an address before it becomes another record your application has to deal with later.

FORMS

Contact forms

Check addresses submitted through public contact, enquiry and lead-generation forms.

SHOPIFY

Shopify stores

Add another validation layer to customer-facing forms, signups and ecommerce workflows.

SAAS

SaaS signups

Validate addresses during registration before creating accounts or triggering onboarding email.

CRM

Lead capture

Keep questionable addresses out of your CRM and sales automation.

CHECKOUT

Checkout flows

Check customer email data before it enters an order or customer record.

API

Backend validation

Call IEV directly from your application and make validation part of your own backend logic.

Developer API

One request. Useful data.

IEV returns individual validation signals so your application can decide exactly what to do with an address.

POST /v1/validateapplication/json
{
  "email": "[email protected]",
  "valid": true,
  "syntax": true,
  "domain": true,
  "mx": true,
  "smtp": true,
  "disposable": false,
  "catch_all": false,
  "role": false,
  "spam": false,
  "scam": false,
  "phishing": false,
  "risk": "low"
}
Email validation by ILHAM

Don't let bad email data reach your database.

Validate the address. Check the infrastructure. Check the sender. Then decide what your application should do.