Email Verification API – Response Guide

Example Response:

{
  "IsValid": true,
  "Score": 95,
  "Email": "validemailnet@gmail.com",
  "State": "Deliverable",
  "Reason": "ACCEPTED EMAIL",
  "Domain": "gmail.com",
  "Free": true,
  "Role": false,
  "Disposable": false,
  "AcceptAll": false,
  "Tag": false,
  "MXRecord": "gmail-smtp-in.l.google.com.",
  "EmailAdditionalInfo": []
}

Field Breakdown

Field	Type	Description
IsValid	boolean	true if the email is syntactically and technically valid.
Score	integer (0–100)	Confidence score. Recommended ≥ 80.
Email	string	The queried email address.
State	string	Deliverable (email server accepted) or Not Deliverable.
Reason	string	ACCEPTED EMAIL or INVALID MAIL.
Domain	string	Email domain (e.g., gmail.com).
Free	boolean	true if the domain is from a free provider like Gmail or Yahoo.
Role	boolean	true if the email is role-based (e.g., info@, support@).
Disposable	boolean	true if it's a temporary/disposable email address.
AcceptAll	boolean	true if the domain accepts all emails regardless of address validity.
Tag	boolean	true if the email contains a plus-tag (e.g., user+tag@domain.com).
MXRecord	string	Mail Exchange server responsible for receiving emails.
EmailAdditionalInfo	array	Reserved for future enhancements.

Best Practices

✅ Send only to emails with IsValid: true and Score ≥ 80.
🚫 Avoid role-based emails for marketing campaigns.
⚠️ Exclude disposable emails to improve deliverability and reputation.
🔍 Be cautious with Accept-All domains—they may give false positives.
📬 Log/tag emails using aliases for tracking or security.