Skip to content
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

Add an option to specify the "-r" flag when querying RIPE NCC #292

Open
wiki-ST47 opened this issue Oct 28, 2020 · 1 comment · May be fixed by #295
Open

Add an option to specify the "-r" flag when querying RIPE NCC #292

wiki-ST47 opened this issue Oct 28, 2020 · 1 comment · May be fixed by #295
Assignees
Milestone

Comments

@wiki-ST47
Copy link

RIPE's Acceptable Use Policy places a limit of 1000 queries "returning personal data sets" per day. This includes any query that returns person or role objects. IP addresses that exceed this limit may be blocked. See for example their policy at https://www.ripe.net/manage-ips-and-asns/db/support/documentation/ripe-database-acceptable-use-policy/why-did-i-receive-an-error-201-access-denied

"Person" and "role" objects are normally returned by default, but RIPE's whois service allows you to decline this using the "-r" flag. As far as I can tell, only RIPE supports/requires this flag. If you do specify this flag, then RIPE will not automatically include referenced objects like "person" or "role", the query will not count towards the 1000/day limit, and you won't get blocked.

I wrote a patch to add this option. It adds a get_recursive option to lookup_whois, which defaults to True. If set to False, and it is a RIPE address, it adds the -r option to the query string.

@secynic secynic self-assigned this Nov 3, 2020
@secynic
Copy link
Owner

secynic commented Nov 3, 2020

Thanks. Can you submit a PR to the dev branch for this? I will test more extensively when I get a chance.

@secynic secynic added this to the 1.3.0 milestone Nov 3, 2020
@secynic secynic linked a pull request Nov 15, 2020 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants