Web - Validation

Free Email Validation API Endpoint

This free email validation API endpoint answers two questions in one POST request: does the address parse, and can its domain receive mail at all. No account, no API key, and no SMTP probe against anyone's mailbox.

  • No API key
  • Syntax + DNS
  • No third party
  • No SMTP probe

Validate an address

POST/email_validate

https://aisenseapi.com/services/v1/email_validate

Validate an address

The free email validation API endpoint takes the address in a data field and returns its syntax and DNS results. There is no header to set beyond the content type.

curl -X POST https://aisenseapi.com/services/v1/email_validate \
  -H "Content-Type: application/json" \
  -d '{"data": "test@gmail.com"}'
{
  "email": "test@gmail.com",
  "valid_syntax": true,
  "domain": "gmail.com",
  "has_mx": true,
  "mx_hosts": ["gmail-smtp-in.l.google.com", "alt1.gmail-smtp-in.l.google.com", "alt2.gmail-smtp-in.l.google.com", "alt3.gmail-smtp-in.l.google.com", "alt4.gmail-smtp-in.l.google.com"],
  "has_address_record": true,
  "mail_route": "mx"
}

Every value there is a fact about text and DNS. The address parsed, gmail.com publishes MX records, and five of them came back in preference order.

Input is trimmed but never rewritten. Posting " Test@GMAIL.COM " gives back "Test@GMAIL.COM" in email and "gmail.com" in domain, so the echo stays faithful to what you sent while the domain arrives lowercased and ready to compare.

Try it

Check an address here: its syntax, and the mail servers its domain publishes. Your browser sends it in a JSON body, as the quick start does. Use a test address, or one you are free to share.

What the free email validation API endpoint returns

FieldTypeDescription
emailstringThe address as received, trimmed.
valid_syntaxbooleanWhether the address parses as an email address.
domainstring or nullThe domain part, lowercased. Null when syntax fails.
has_mxbooleanWhether the domain publishes MX records, including an explicit null MX.
mx_hostsarrayUp to five MX hosts, lowest preference first.
has_address_recordbooleanTrue when the domain publishes an MX record or has an address record for fallback.
mail_routestringmx, implicit_mx, no_mail, unknown or invalid_syntax.

Use mail_route to decide what to do with an address. The other fields show which records the resolver found.

The mx_hosts cap of five matters for large providers. Gmail publishes exactly five, so the list above is complete, but a domain with more will hand you the five lowest preferences and stop there. The array is a diagnostic aid, not a routing table.

How the API chooses a mail route

  1. Check the syntax

    An address that fails to parse gets invalid_syntax. The DNS lookup starts only when the address parses.

  2. Look for a mail server

    A domain that names a mail exchanger gets mx. A domain can also explicitly decline email with a null MX record. That produces no_mail even when the same domain serves a website.

  3. Check the fallback

    When there is no MX record, an A or AAAA record provides a delivery route called implicit_mx. If DNS confirms that there is no route, the result is no_mail. An inconclusive lookup produces unknown and can be retried.

Here is an example of a well-formed address with no route.

curl -X POST https://aisenseapi.com/services/v1/email_validate \
  -H "Content-Type: application/json" \
  -d '{"data": "someone@this-domain-does-not-exist-zzz9.no"}'
{
  "email": "someone@this-domain-does-not-exist-zzz9.no",
  "valid_syntax": true,
  "domain": "this-domain-does-not-exist-zzz9.no",
  "has_mx": false,
  "mx_hosts": [],
  "has_address_record": false,
  "mail_route": "no_mail"
}

Syntax passed. DNS confirmed there was no delivery route for this domain.

What DNS tells you about a mailbox

Try two different addresses on the same domain. The lookup can produce the same mail route for both.

curl -X POST https://aisenseapi.com/services/v1/email_validate \
  -H "Content-Type: application/json" \
  -d '{"data": "no-such-mailbox-zzq7431@gmail.com"}'
{
  "email": "no-such-mailbox-zzq7431@gmail.com",
  "valid_syntax": true,
  "domain": "gmail.com",
  "has_mx": true,
  "mx_hosts": ["gmail-smtp-in.l.google.com", "alt1.gmail-smtp-in.l.google.com", "alt2.gmail-smtp-in.l.google.com", "alt3.gmail-smtp-in.l.google.com", "alt4.gmail-smtp-in.l.google.com"],
  "has_address_record": true,
  "mail_route": "mx"
}

The local part before the @ can change without affecting the DNS answer. To confirm that someone controls the inbox, send a code or a link that the recipient can use.

A bad address is a result, not an error

Rejection arrives with HTTP 200 and a normal body.

curl -X POST https://aisenseapi.com/services/v1/email_validate \
  -H "Content-Type: application/json" \
  -d '{"data": "not-an-email"}'
{
  "email": "not-an-email",
  "valid_syntax": false,
  "domain": null,
  "has_mx": false,
  "mx_hosts": [],
  "has_address_record": false,
  "mail_route": "invalid_syntax"
}

Missing input or an input value of the wrong type returns HTTP 400. For example, an empty request returns this error.

{"error":"No email address provided."}

For a well-formed request, read mail_route in the response. If it is unknown, retry the lookup later.

One case catches people out. Internationalized domains are not converted to punycode, so post@blåbær.no comes back with valid_syntax false. Convert such domains yourself before calling if your forms accept them.

Where an address check pays for itself

Signup forms

AI SENSE Pro uses this check when someone registers. A domain with no mail route gets flagged on the form. A temporary DNS problem prompts the customer to try again.

Agent input checking

Verify an address a language model extracted from a document before anything downstream tries to use it.

List hygiene

Flag stored contacts whose domains have stopped publishing mail records, which is a common sign of a company that no longer exists.

Support tooling

Show an agent whether a customer-supplied address could receive mail at all, before anyone starts hunting for a missing message.

All four share a shape. They use the free email validation API endpoint to reject the clearly impossible, then let a real message settle the rest.

Privacy and limits

The address travels in the POST body, not the URL, so it never appears in request paths, logs or referrer headers. DNS questions about the domain go through this server's own resolver, as any lookup must, and no third party sees the address.

The service-wide limit is 5000 requests per IP per day, with no key and no account behind it. Cache results per domain rather than per address: the DNS half of the answer is identical for every address at the same domain, which cuts the request count sharply on a large list.

Every endpoint on the service is listed in the free public REST APIs reference. When you have a domain but no address, the Domain IP Lookup API endpoint answers the resolution half on its own, and the Validation API endpoint covers the other input types a signup form has to check. The Health Check API endpoint is the one to poll before you build a batch job against any of them.