EmailVerify for .NET

Key Features

* Advanced syntax validation: EmailVerify for .NET features a complete syntactical email validation engine that obeys to the current IETF standards, including RFC 1123, RFC 2821, RFC 2822, RFC 3490, RFC 3696, RFC 4291, RFC 5321, RFC 5322 and RFC 5336. It fully supports quoted strings, quoted pairs, internationalized domain names (IDN) and mailboxes, as well as comments and domain literals. * Disposable email addresses (DEA) detection: The component automatically detects temporarily email addresses generated by certain free services on the Internet collectively known as disposable email address providers, like Mailinator, 10MinuteMail, GuerrillaMail, TempInbox, MailEater, TrashMail and about 2000 more. * Mailbox existence check: EmailVerify for .NET can check if an email address exists without sending email messages; it does so by emulating the behavior of common mail exchangers and employing the SMTP protocol wisely, while respecting the Netiquette rules to avoid the originating IP address being tagged as a potential source of spam. * Catch-all domain test: With the term catch-all, we mean a mailbox on a domain that will receive all of the email messages addressed to that domain, even if their addresses do not exist in the mail server; EmailVerify for .NET detects catch-all domains automatically and gives back a specific status code that signal the presence of such a domain. * Greylisting support: EmailVerify for .NET automatically detects the temporarily unavailability of the mailbox under test, a condition known as greylisting (or graylisting). * Yahoo! mailbox validation: Our email validation technology includes an integration feature modeled after the Yahoo! mail exchangers architecture; EmailVerify for .NET can validate Yahoo! email address up to the CatchAll level (the highest) and check if a given Yahoo! mailbox exist or not. * Detailed email validation results: With 40 different result statuses and a dedicated class hierarchy, EmailVerify for .NET includes great tools for investigating the reason of a specific email validation failure and inspecting the details of every aspect of the verification process, including the result of the syntax analysis, the DNS output (along with the MX records) and the complete SMTP transcript.