Enable WHOIS Support ARIN, RIPE NCC, APNIC #89

Closed
opened 2025-12-29 15:32:14 +01:00 by adam · 7 comments
Owner

Originally created by @ryanmerolle on GitHub (Jun 29, 2016).

Function: Be able to provide basic WHOIS information (urls, owners, etc.) for Subnets & AS Numbers
Use Case: Allow for further verification of "asset owners," eventually allow for AS origin, and contact details

Helpful Links:

Originally created by @ryanmerolle on GitHub (Jun 29, 2016). **Function**: Be able to provide basic WHOIS information (urls, owners, etc.) for Subnets & AS Numbers **Use Case**: Allow for further verification of "asset owners," eventually allow for AS origin, and contact details **Helpful Links**: - https://www.arin.net/resources/whoisrws/whois_api.html - https://github.com/RIPE-NCC/whois/wiki/WHOIS-REST-API - https://www.apnic.net/apnic-info/whois_search/using-whois
adam closed this issue 2025-12-29 15:32:14 +01:00
Author
Owner

@doon commented on GitHub (Jun 30, 2016):

Do you mean for doing integrated whois lookups on customer(end user) provided IP space? Or are you looking for the ability to do SWIP /RPSL via an RIR integration?

@doon commented on GitHub (Jun 30, 2016): Do you mean for doing integrated whois lookups on customer(end user) provided IP space? Or are you looking for the ability to do SWIP /RPSL via an RIR integration?
Author
Owner

@ryanmerolle commented on GitHub (Jun 30, 2016):

I think SWIP / RPSL is interesting for multitennacy, but with this I was only talking about pulling meta deta about subnets and ASNs to track usage of the public resources.

@ryanmerolle commented on GitHub (Jun 30, 2016): I think SWIP / RPSL is interesting for multitennacy, but with this I was only talking about pulling meta deta about subnets and ASNs to track usage of the public resources.
Author
Owner

@doon commented on GitHub (Jun 30, 2016):

Gotcha. For us (Colo/Datacenter / Regional ISP), RIR integration is on of the biggest features we use on our current IPAM (6Connect provision) Since we need to keep track of report / all our allocations back

@doon commented on GitHub (Jun 30, 2016): Gotcha. For us (Colo/Datacenter / Regional ISP), RIR integration is on of the biggest features we use on our current IPAM (6Connect provision) Since we need to keep track of report / all our allocations back
Author
Owner

@MrDragon commented on GitHub (Jul 1, 2016):

Full integration (rwhois etc) would be sweet, but for now I'd settle for a customer-ID field per prefix - that way I could cross-reference with our customer database/CRM, shuffle the data, and create whatever I need (rwhois, SWIP, IRR, documentation, etc)
Or should this be a separate feature request?

@MrDragon commented on GitHub (Jul 1, 2016): Full integration (rwhois etc) would be sweet, but for now I'd settle for a customer-ID field per prefix - that way I could cross-reference with our customer database/CRM, shuffle the data, and create whatever I need (rwhois, SWIP, IRR, documentation, etc) Or should this be a separate feature request?
Author
Owner

@camwin commented on GitHub (Aug 10, 2016):

I, too, would really like SWIPing. Currently, the only free IPAM I know of that offers SWIPing is IPPlan.

@camwin commented on GitHub (Aug 10, 2016): I, too, would really like SWIPing. Currently, the only free IPAM I know of that offers SWIPing is IPPlan.
Author
Owner

@The-Loeki commented on GitHub (Nov 24, 2016):

Would RDAP not be a much better fit? It's basically billed as the JSON successor to whois, and it's actually already a requirement for name registries to provide it:
https://en.wikipedia.org/wiki/Registration_Data_Access_Protocol

@The-Loeki commented on GitHub (Nov 24, 2016): Would RDAP not be a much better fit? It's basically billed as the JSON successor to whois, and it's actually already a requirement for name registries to provide it: https://en.wikipedia.org/wiki/Registration_Data_Access_Protocol
Author
Owner

@jeremystretch commented on GitHub (Mar 1, 2017):

This feature request is pretty nebulous. I'm going to close out this issue as it lacks a clear definition and scope, but please feel free to propose a new, specific request including a detailed use case.

@jeremystretch commented on GitHub (Mar 1, 2017): This feature request is pretty nebulous. I'm going to close out this issue as it lacks a clear definition and scope, but please feel free to propose a new, specific request including a detailed use case.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#89