-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
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
[Bug] Verisign's whois server returns No match for
which can not be handled by whoiser
#117
Comments
I can help submiting a PR to fix this. |
Another example found:
The keyword is |
And another example:
The keyword is |
And another example:
The keyword is |
Another example:
The keyword is |
Another example:
The keyword is |
And another example:
The keyword is |
And another example:
The keyword is |
And this:
The keyword is |
Version(s) affected: 1.18.0
Description
How to reproduce
It should log an empty object, but
whoiser
is trying to parse the not found message instead.Possible Solution
Update this line to include
No match for
:whoiser/src/parsers.js
Line 27 in 9724674
The text was updated successfully, but these errors were encountered: