We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Its possible to bypass the validation by using subdomains of the disposable domains. e.g.
[email protected] [email protected]
The root domains are blocked, but the validation logic does not detect these, since it checks the entire domain as single string.
I am seeing cases of people abusing this in the wild. I assume the disposable providers offer dynamic subdomains as an option.
The text was updated successfully, but these errors were encountered:
Validation is performed similarly to what disposable/disposable offers for JS: See https://github.com/disposable/disposable/blob/7c19066bc3765767d5427f6da8334a3e70687f82/disposable.js#L11-L12
But I'm open for a PR with tests providing a configuration option for that.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Its possible to bypass the validation by using subdomains of the disposable domains. e.g.
The root domains are blocked, but the validation logic does not detect these, since it checks the entire domain as single string.
I am seeing cases of people abusing this in the wild. I assume the disposable providers offer dynamic subdomains as an option.
The text was updated successfully, but these errors were encountered: