Parse local email addresses, convert internationalized domains to browser-normalized ASCII form, and output one domain per address.
These tools work locally on text. Syntax validation is not mailbox verification: no DNS/MX lookup, SMTP connection, account-existence check, or deliverability test is performed.
Normalize internationalized domains to ASCII A-label form for stable grouping while keeping list cleanup local and exportable.
These tools intentionally stop at local parsing, normalization and URI construction. A syntactically valid address can still have no MX service, no mailbox, a catch-all domain, or delivery restrictions; v266 does not label those network states without actually checking them.
Whitespace, mixed case, comments, display names, and duplicate addresses can make a domain inventory misleading. Extract the address portion first, normalize the domain case, then count unique values separately from total occurrences. Preserve the original input when the inventory must be audited later.
An email domain may appear as Unicode or as an ASCII-compatible punycode form. Treat those as representation choices, not automatically as different organizations. When comparing lists across systems, normalize to one representation and keep the display form available for human review.
Finding text after the @ sign does not prove that a mailbox exists, that the domain accepts mail, or that a message will pass authentication and spam checks. DNS, MX, SPF, DKIM, DMARC, recipient policy, and server reputation are separate questions. Use the extracted list as an inventory, not as a delivery guarantee.
Email lists can contain personal or confidential information. Browser-local extraction reduces unnecessary transmission, but copied output can still be pasted into tickets, spreadsheets, or chat systems. Share only the minimum domain-level information needed for the task and retain the full address list only when required.
WebToolArc