--- title: "Email Verification Service & Domain Intelligence | Emvero" description: "Email verification for single addresses, lists and signups. Inspect a domain’s mail routing, provider, SPF and DMARC with Domain Intelligence." url: https://emvero.io/ language: en updated: 2026-10-08 --- Emvero email verification service # Email verification and Domain Intelligence. Check whether an email address can receive mail, or inspect how its domain handles email. Emvero returns the findings and shows where the answer remains uncertain. Email verification Domain Intelligence Pricing Start for free View pricing 1,000 credits when you confirm a new account No credit card required Address checks ## Email verification Check an address and get a status, a recommended action and reason codes explaining the findings. Use the checker in your account for one address, or the API for lists and signup forms. No verification email is sent. - Syntax, domain and mail routing checks - Mailbox evidence when the receiving server permits it - Uncertain results reported as unknown See an example check Domain profiles ## Domain Intelligence Enter a domain to see its mail routes, provider and published email settings. The profile also shows the networks behind its mail and website addresses. It does not check individual mailboxes. - MX records show where incoming mail goes - SPF and DMARC describe published sending policies - Extended adds registration details when available Inspect a domain Domain Intelligence ## Read a domain’s mail configuration. Start with the mail route and receiving provider. Then review the domain’s published SPF and DMARC records, which describe authorised senders and how receivers should handle messages that fail authentication. Standard includes these settings and mail and website networks. It also reports known temporary-mail and public mailbox providers, and any known catch-all behaviour, where a server accepts arbitrary recipients. Extended adds registration details when available. The profile does not test a sent message or verify a mailbox. Inspect a domain What a domain profile includes Mail routing MX records and whether the domain has a mail route Incoming mail provider Identified from MX records when possible Published sending policies SPF and DMARC records IP addresses and networks Mail and website IP addresses, network numbers (ASN), and recognised CDN or proxy providers Registration · Extended Registration date, age, expiry and registrar when available Each part of the profile shows its source and available observation dates. Missing or uncertain findings are labelled. Email Verification ## Check one address, a list or a new signup. The account checker and API return the same statuses, recommended actions and reason codes. Choose how to submit addresses based on your workflow. 01 / Single ### Check one address in your account. Enter an address in your account to review its status and the evidence from each stage that ran. The recommended action helps you decide how to handle it. See an example check Example address check alex@studio.co Deliverable Recommended action: `allow` Mail routing MX found Mailbox probe Recipient accepted Disposable provider No Role account No `SMTP_RCPT_ACCEPTED` Illustrative example using Emvero’s result fields. No live check runs here. 02 / Bulk ### Check a list through the API. Read a list you control, send one API request per address and save the results in your own system. You manage the processing and output; Emvero has no hosted file uploader or bulk-run dashboard. Explore bulk verification Outcome breakdown 125,420 rows | | | | --- | --- | | Deliverable | 104,852 | | Risky | 9,112 | | Undeliverable | 9,804 | | Unknown | 1,652 | Illustrative figures for a fictional list, not measured customer results. 03 / Real-time ### Check an address while the user is entering it. Call the API from your server during signup, lead capture or checkout. Use the recommended action to accept the address, ask the user to confirm it by email, or reject it. A check may return pending first; poll after the supplied retry interval. Explore real-time verification POST /v1/verifications ``` // request { "email": "person@mailinator.example" } // response { "status": "risky", "action": "allow", "confidence": 0.65, "reason_codes": ["SMTP_RCPT_ACCEPTED", "DISPOSABLE_DOMAIN"] } ``` Illustrative example using Emvero’s result fields. No live check runs here. The confidence field is an evidence score from 0 to 1, not a delivery probability. Acceptable use ## Use verification for addresses you already hold. Emvero checks addresses you submit. It does not supply contacts or establish permission to send messages. ### No address discovery Emvero does not find, guess, enrich, sell or suggest email addresses. Submit addresses you have already collected. ### Permission to send A deliverable result describes technical findings about the address. Permission to contact its owner depends on how you obtained the address and what the recipient agreed to. ### Prohibited uses Mailbox enumeration, verification of purchased, scraped or harvested lists, and uses that support unsolicited messaging are prohibited. Patterns consistent with enumeration are treated as abuse at any volume and lead to credential suspension. See the [terms](https://emvero.io/terms/). ### No verification email A full check may contact the receiving mail server. The SMTP session stops before any message data is submitted, so the check sends no email to the address. Verification stages ## How an address is checked. Emvero checks the address format, domain and mail route before attempting a mailbox check. Domain depth stops at the mail route. Full depth can continue to the receiving server when it permits a check. A permanent failure stops later stages. 1. 01 Syntax Check that the address has a valid structure, including its local part and domain. This stage needs no network connection. 2. 02 Domain Look up the domain in DNS, the system that publishes domain records. If it does not exist, the check stops. 3. 03 Mail routing Find where the domain receives mail. MX records name its mail servers; some domains use a fallback route or explicitly declare that they accept no mail. 4. 04 Mailbox probe At full depth, ask the receiving mail server about the recipient over SMTP. Stop before the `DATA` stage, so no email is sent. 5. 05 Classification Combine the findings into a status and recommended action. Reason codes identify the evidence behind the result. A server’s acceptance supports the result, but does not guarantee future delivery or prove who controls the mailbox. Catch-all behaviour or hidden recipient information can leave the result risky or unknown. What you get back ## What the four result statuses mean. The status describes what the checks established. The recommended action tells you whether to accept the address, ask the user to confirm it by email, or reject it. Reason codes explain the findings behind that recommendation. Deliverable The receiving server accepted the recipient and no risk signals were found. This supports mail acceptance, but does not guarantee delivery. Typically: Mail exchangers configured · Recipient accepted · No risk flags Action: `allow` Risky A finding such as a catch-all domain, disposable-mail provider or a reported mailbox problem needs review. Read the reason codes and recommended action to decide how to handle the address. Typically: Catch-all domain · Disposable provider Action: `allow_with_email_confirmation` / `allow` Undeliverable The check found a definite technical failure, such as invalid syntax, a non-existent domain or a domain that explicitly accepts no mail. Typically: Bad syntax · Domain does not exist · Domain accepts no mail Action: `reject` Unknown The available evidence could not settle the address. A timeout, temporary restriction or provider that hides recipient information can leave the mailbox uncertain. Typically: Timed out · Greylisted · Provider throttled · Mailbox existence hidden Action: `allow_with_email_confirmation` **Pending means the check is still running.** If the API returns `pending`, wait for the interval in `retry_after_ms` before polling again. The completed check returns one of the four statuses above. Choosing a check ## Match the check to the decision you need to make. A working domain mail route does not establish that a particular mailbox exists. Choose the product according to what you need to know. ### Email verification Use email verification to decide how to handle a specific address. A full check can collect mailbox evidence; a check at domain depth stops at syntax, domain and routing findings, with no SMTP session. ### Domain Intelligence Use Domain Intelligence to investigate a domain’s mail setup or add provider and network details to your records. Standard covers configuration and networks. Extended adds registration details when available. Neither mode checks a mailbox. Pricing ## One prepaid balance for both products. Both products use prepaid credits, with no subscription. An email check’s cost depends on its depth; Domain Intelligence shows the cost before you submit a lookup. Purchased credits expire twelve calendar months after payment is confirmed. View pricing Questions ## Common questions **What does Domain Intelligence check?** Both Standard and Extended show mail routing, MX records, the receiving provider when identified, published SPF and DMARC, and IP networks. Extended also looks up registration details, such as the date, age, expiry and registrar, when available. The profile labels missing or uncertain observations. It does not test individual mailboxes. **Do the two products share credits?** Yes. You buy prepaid credits for one account balance and can use them for either product, in your account or through the APIs. The charge depends on the operation you choose and the result. The pricing page explains the rates. **What is the difference between a full check and domain depth?** Both check the address format, domain and mail routing. A full check can also ask the receiving server about the recipient when the provider permits it. Domain depth opens no SMTP session, so it cannot establish that an individual mailbox exists. Both report relevant known signals, such as disposable domains and role accounts. **Does verification send an email?** No. A mailbox check opens an SMTP session, names the recipient and stops before the `DATA` stage. No subject or message body is submitted, so nothing is delivered to the address. **What does “unknown” mean?** The checks did not find enough evidence to settle the address. For example, the server may time out, temporarily restrict checks or hide recipient information. Keep `unknown` separate from `undeliverable`. If you need to establish that the user controls the mailbox, ask them to confirm their address by email. **Can catch-all addresses be verified?** A full check can identify a domain that accepts arbitrary recipients. On such a domain, acceptance does not establish that the particular mailbox you entered exists. Read the reason codes alongside the `risky` or `unknown` result. Domain Intelligence reports known catch-all findings without opening a new SMTP session. **Is the address I check stored?** Yes. Verification records are retained for 30 days. Retention is separate from evidence freshness: storing a record does not make its findings current for the whole period. The [security page](https://emvero.io/security/) and [privacy policy](https://emvero.io/privacy/) explain storage and deletion. Getting started ## Create an account to run your first check. Confirm your account’s email address to receive 1,000 starting credits. Then open the email checker or Domain Intelligence in your account. No credit card is required. Start for free Contact sales