Extract Email Addresses From Text

Standard addresses: a local part of letters, numbers, dots, percent signs, plus signs and hyphens, then an at sign, a dot-separated domain and a top-level domain of at least two letters. That covers the shape of almost every everyday address.

It compares addresses without regard to case, so Bob@Site.com and bob@site.com are treated as the same. The first spelling encountered is the one kept, so your original casing is preserved.

No. Sorting is case-insensitive, so Amy@site.com and amy@other.com are ordered by their letters rather than by uppercase coming before lowercase. The addresses themselves are left exactly as written.

Yes. A full address like first.last+tag@mail.example.co.uk is matched intact, including the subdomain and the gmail-style plus tag, so nothing is truncated at the first dot.

Usually yes. Because it scans raw text, an address written as mailto:someone@site.com still yields someone@site.com. It reads whatever characters are present, so pasting page source works as well as plain prose.

By design it skips obfuscated forms such as name at domain dot com, quoted or exotic RFC 5322 local parts, addresses that use an IP literal for the domain, and internationalized addresses with non-ASCII letters. The trade-off keeps false positives from creeping in.

No. This is pattern matching, not verification. It confirms an address looks valid but does not query DNS, check the mailbox or confirm anyone can receive mail there.

There is no fixed cap. The scan runs in your browser, so the practical ceiling is your device memory. Even a long log file is searched almost instantly.

Yes. The whole scan happens locally in your browser and nothing is uploaded to a server, so a list of customer or contact addresses never leaves your device.