PLEASE DON'T DISCLOSE SECURITY-RELATED ISSUES PUBLICLY, SEE BELOW.
| Version | Supported |
|---|---|
| 1.x | ✅ |
This package produces signals from the checks you configure. It reaches no
network by itself: DNS happens only when you supply an MxResolver, and HTTP
only when you register a check that makes requests. It renders no verdict, so
no output of this package is proof that a mailbox exists or is trustworthy.
Two things worth weighing when you assemble a pipeline:
- Checks you register run with your credentials and your egress. Treat a third-party plugin as you would any dependency that talks to the network, and read what it sends before you route customer addresses through it.
Report::toArray()contains the address. It is designed to be persisted for auditability; store it wherever you already store the address itself, and no more widely.
Keep your lists fresh: stale data causes both false negatives (new providers unrecognized) and false positives (retired entries still blocking real users).
If you discover a security vulnerability within this package, please send an email to Alejandro Morelos at info@domainvalidity.dev. All security vulnerabilities will be promptly addressed.