A configurable Go email validator that verifies addresses via regex, DNS, SMTP, and more to ensure validity and existence.
Truemail-go is a framework-agnostic email validation library for Go that performs multi-layered verification to confirm email addresses are both syntactically correct and actually exist. It helps developers prevent fake or invalid email submissions in their applications by combining multiple validation techniques, including regex pattern matching, DNS (MX) record checks, MX blacklisting, and SMTP connection verification.
Go developers building applications that require robust email validation, such as user registration systems, contact forms, or any service where preventing fake or invalid email submissions is critical.
Developers choose Truemail-go for its configurable, multi-layered validation approach that balances strictness with practicality, ensuring emails are valid and deliverable without overcomplicating integration. Its unique selling points include support for internationalized emails, disposable email detection, whitelist/blacklist overrides, and an SMTP debugger for troubleshooting.
🚀 Configurable Golang 📨 email validator/verifier. Verify email via Regex, DNS, SMTP and even more. Be sure that email address valid and exists.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Performs regex, DNS, MX blacklist, and SMTP checks to verify email syntax, domain existence, and deliverability, as outlined in the synopsis and validation features.
Offers extensive customization via ConfigurationAttr, including validation layers, timeouts, domain-specific rules, and whitelist/blacklist overrides, demonstrated in the usage examples.
Validates internationalized email addresses (EAI) and detects disposable emails through MX blacklist validation, per the features list and configuration options.
Includes an SMTP debugger for troubleshooting validation sessions, mentioned in the key features, aiding in diagnosing SMTP-related issues.
MX lookup does not strictly comply with RFC 5321, which the README admits might lead to inaccuracies or false positives in domain verification.
Requires configuring numerous parameters like verifier email, validation types, and timeouts, which can be overwhelming for quick integrations, as shown in the ConfigurationAttr struct.
DNS and SMTP validations rely on external network calls, introducing latency and potential points of failure, especially in high-throughput or unreliable network environments.