Can ChatGPT verify whether an email address is valid?

Confirming a mailbox takes two live network steps. First comes a DNS query to find the domain's mail servers, then an SMTP conversation with one of them about your recipient. Both answers change from day to day, and neither one can be recalled from training data. Our page on whether verification sends an email walks through the five SMTP steps.

Ask a chatbot whether john.smith@acme.com is valid and you'll get a confident reply either way. It's matching patterns in text, and a plausible address at a real company is exactly the input that produces a confident wrong answer. A mailbox deleted last month looks identical to a live one.

Code tools and browsing don't close the gap. Sandboxed environments block outbound port 25, because sending on that port is precisely what abuse rules exist to stop. So even a model that writes a perfect SMTP script can't run it from inside the chat.

An assistant can still get a real answer by calling a real verifier. Give it a tool that sends the address to the ZapBounce API, and the verdict comes from the mail server's reply, not from the model. The verification API is a single HTTP call, so any assistant that can call a tool can run that same check.

The rest of the work suits a model well. It can spot a column that mixes three formats, draft the regex for a first syntax pass, or explain a 550 in a bounce log. It can also write the script that reads your CSV and calls the verification API. See whether regex is enough for how far a syntax check goes on its own.

You can see the limit for yourself. Pick five addresses where you know the truth. Use your own working address, and a colleague's. Add a mailbox at your company that was deleted last year and a made-up name at your own domain. Finish with an address at a domain that doesn't exist.

Paste them into a chatbot and ask which are valid. Watch what it goes on. It will likely approve the first four, because they all look like normal addresses at a real company. You may even get an explanation of its reasoning in a confident tone. The deleted mailbox and the made-up one are the tell, since nothing in the text separates them from the real ones.

Now run the same five through a real verifier. The deleted mailbox comes back invalid, because your mail server said so. Only a tool that asked the server can know that.

A model is good at the work around verification. Ask it to write a script that reads contacts.csv and sends each address in the work_email column to a verification API. Have it write the result into a new column. You'll have working code in a minute, and the check itself still happens where it should.

It's also handy for cleanup before upload. It can spot that one column mixes three date formats, or that some rows hold two addresses split by a semicolon.

Be careful with what you paste, though. A customer list is personal data. Dropping 5,000 names and addresses into a chat window shares them with another company, and your privacy terms may not allow that. Ask for the script, run it on your own machine, and keep the list out of the chat.

When a verification vendor advertises AI, ask one thing: does the verdict come from a server's reply, and can you see that reply?