Email Validation
Know which addresses are worth your time. Domain, MX record, mailbox type, and the date the mailbox was last active. Resolve recent activity with Gmail and other providers in one request.
Your first $5 of validations are on us, valid for 30 days. No card required.
Email address check
Enter an address and run a live check.
Results by e-mail address
The deliverability verdict, the last-seen date, the provider and tags run on an account. Normalization, domain and MX stay open.
1234567891011121314151617181920212223
For demonstration purposes and business use only. Terms · Data & opt-out
Validating phone numbers instead? Run a live check on the Phone Validation page.
A mail server accepts your message. Whether anybody opens the message is a different question, and you find out after the send.
01
A hard bounce tells the mailbox provider your list is stale. deliverability.status returns false before anything is sent, and last_seen dates the rest.
02
A mail server keeps accepting mail for a mailbox nobody has opened. last_seen returns when the mailbox last showed activity, from digital footprint signals.
03
A vanity domain says nothing about what runs the mailbox. mx_record returns the host that actually receives the mail.
04
A sequence written for a named buyer lands in a shared company inbox. sub_status classifies the mailbox behind a valid address.
05
A contact row carries an address and a number, bought from two vendors. score.email.validation and score.phone.scoring run on one token, in one request envelope.
06
A row arrives with no history. An old import and a live signup look the same. score.email.tags returns which of 21 interest categories an address has turned up in, and when.
One request returns the verdict, the technical evidence and the last-seen date.
Check incoming addresses 2,000 to 10,000 at a time with sequential methods, or run a whole file through the batch methods.
Upload a CSV or XLSX in the workspace, up to 5 MB and 200,000 rows. Map columns, pick methods, see the price, and export the scored file.
JSON-RPC 2.0. Send 2,000 to 10,000 addresses per request to the sequential methods, or run a whole file as a batch job, up to 10 concurrent jobs.
Developers →Our team sets up the first runs with you: file mapping, method choice and the export format your systems import.
Standard email validation checks the syntax, resolves the domain and its MX records, then opens an SMTP conversation with the receiving mail server. The verdict is whatever that server’s response code says.
Standard validation answers whether a mail server will take the message. ScoreMachine returns that answer and the date the mailbox was last active.
Product tour
Five steps from an empty workspace to a validated, exportable list. Plays on its own. Click any step to jump.
Seven steps from a QR code to a validated address, without leaving Telegram. Plays on its own. Click any step to jump.
Three calls, from a token to a validated address. Every request below runs as written against https://api.scoremachine.ai.
Audiences are added inside the project after creation.
Reseller list, cleaned before handover · created just now
Audiences
0
Contacts
0
Validated
—
No audiences yet
An audience holds the contacts you want validated. Name it EMEA email refresh to start.
Drop your file here
or click to browse · max 5 MB · up to 200,000 rows
2 of 3 columns auto-detected from the header row. Override any of them before continuing.
Estimated run
$69.08
18,420 addresses · Email validation
Growth tier — 18,420 addresses at $0.00375 each.
Validating in progress · Email validation
0%
0 / 18,420 addresses checked
eu-contacts-sep · run took 14s
Per-address verdicts are on the audience screen and in the export.
Share Your Phone Number?
The bot will know your phone number. This can be useful for integration with other services.
⚠ Warning! Never enter your Telegram login codes in mini apps.
Scan the QR
The bot is the fastest way in. Nothing to install, and the same account works in the workspace and the API afterwards.
Created your account in Telegram? Use Forgot password with the email you gave the bot.
Same fields, same values as the API response and the workspace export. The channel changes; the object does not.
123456789101112
1234567891011121314
The token arrives in the Token response header, not in the body. The body carries the user record. Tokens last 24 hours; call auth.login again when one expires.
A successful call here confirms the token is live and the account is funded. Balances are floating-point USD. For batch jobs, audiences.score.price quotes the run before it starts.
emails takes 2,000 to 10,000 addresses per request. deliverability.status is the verdict; last_seen is the last-seen date.
Errors come back in the standard JSON-RPC envelope with code, message and optional data. Retry transient failures with backoff. Full method reference, error list and troubleshooting at doc.scoremachine.ai.
doc.scoremachine.ai →12345678910
Errors return HTTP 200 with an error object in place of result. Check for error before reading result.
Contacts you submit should be ones you are entitled to contact. See Terms and Data & opt-out.
Three ways in, one account behind them. Start in whichever fits your team. The results are the same object.
Validation fits where your data already lives.
Where validation fits
Drop what will not accept mail, then sort the file on the last-seen date.
Lead Gen & GTM →One account validates the address and the number on the same contact row.
SMS Providers →score.email.validation returns the verdict and last_seen dates the mailbox.
Call Centers →Email validation confirms the address format, the domain, and whether the mail server accepts mail. ScoreMachine returns the mail host behind the domain and the mailbox classification. last_seen returns when the mailbox was last active.
Last-seen resolves for more than half of addresses globally, Gmail included.
A syntax checker confirms an address could exist. ScoreMachine resolves the domain and returns mx_record, the host that receives the mail. sub_status classifies the mailbox. last_seen returns when the mailbox was last active.
Sending to addresses that no longer accept mail is the largest controllable cause of hard bounces. Validating before a send removes those addresses from the file. What you send after that is your own.
Yes. CSV or XLSX upload takes up to 5 MB and 200,000 rows. The API takes 2,000 to 10,000 addresses per request. The Web UI tab of the tour above runs a file end to end, from upload to export.
Every field the page shows describes the address or the mailbox. Format, domain, MX record, mailbox classification and the last-seen date. Tags come back named and dated, exactly as recorded.
We delete query data within 24 hours. Operational logs and backups are kept for 30 days, then deleted.
Yes. Phone and email run on one account, one token and one request envelope. See Phone Validation.
The widget at the top of this page runs a live check on any address. Book a call to walk through your setup with an expert.