-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Whois Protocol Support (using rdap) #1354
Conversation
basic example template: id: basic-whois-example
info:
name: test template for WHOIS
author: pdteam
severity: info
whois:
- query: "{{Host}}"
extractors:
- type: kval
kval:
- "expiration date"
- "registrar" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm!
Also, we should consider adding support for Debug mode whois response since currently no additional info is printed when running rdap protocol templates with |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As @Ice3man543 suggested, we can add support for debug/debug-req/debug-resp
flag.
Will there be support for querying whois/rdap servers directly? For example:
However, if I use the posix
|
We can specify a custom rdap domain ( Example template: id: basic-whois-example
info:
name: test template for WHOIS
author: pdteam
severity: info
whois:
- query: "{{Host}}"
server: https://rdap.namecheap.com
extractors:
- type: kval
kval:
- "expiration date"
- "registrar" |
That's great. Is there a chance we can define the custom rdap server as an environmental variable so we don't have to maintain 200+ templates? |
that's a great idea, ENV variable, and CLI flag to feed custom whois server to use will ease the process. cc @parrasajad |
Proposed changes
Checklist