Syntax validation
Check the structure of the address before sending it anywhere or storing it in your database.
ILHAM AUSTRALIA™
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.
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.
Check the structure of the address before sending it anywhere or storing it in your database.
Check whether the domain exists and whether its DNS configuration supports email delivery.
Find the mail exchange servers responsible for receiving messages for the domain.
Check mailbox-level signals through the receiving mail server without sending an actual email.
Detect temporary and throwaway email addresses commonly used for unwanted signups and low-quality submissions.
Identify domains that accept mail for addresses that may not have an individually verifiable mailbox.
Flag shared addresses such as info@, sales@, support@ and admin@.
Identify suspicious or malformed addresses and common domain mistakes before they become bad data.
Combine technical validation with sender intelligence to identify addresses that deserve extra attention.
sender records checked during validation
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.
IEV gives your application individual validation signals so you can decide how strict your own acceptance rules should be.
Validate the email structure.
Check whether the domain exists.
Check mail exchange records.
Check receiving mail-server signals.
Detect temporary email providers.
Detect accept-all mail domains.
Detect shared departmental addresses.
Check IEV sender intelligence.
Put IEV between your users and your database. Validate an address before it becomes another record your application has to deal with later.
Check addresses submitted through public contact, enquiry and lead-generation forms.
Add another validation layer to customer-facing forms, signups and ecommerce workflows.
Validate addresses during registration before creating accounts or triggering onboarding email.
Keep questionable addresses out of your CRM and sales automation.
Check customer email data before it enters an order or customer record.
Call IEV directly from your application and make validation part of your own backend logic.
IEV returns individual validation signals so your application can decide exactly what to do with an address.
{
"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"
}Validate the address. Check the infrastructure. Check the sender. Then decide what your application should do.