On 17 Nov 2025, at 15:52, Edward Shryane <eshryane@ripe.net> wrote: [..]
An example WHOIS entry on how this could look like could be a good example.
I think having both the URL of the company register (so that one does not have to figure out what it is), be that a link to a contact address that one has to call to get details, or that has a public lookup interface can help a lot. Eg Switzerland has https://zefix.admin.ch <https://zefix.admin.ch/> enter the name and one can see what is behind the company and if that looks like something that is legal or barely legal.
We plan to include a URL to the company register on the database web query page, where possible (based on the number format and the legal country: attribute value).
However I'd prefer not to encode the number as a URL in the reg-nr: attribute itself. Making a link for interactive users to click is convenient but makes it harder for client programs to parse (there's no standard URL format for registration numbers that I'm aware of). Also we may not be able to identify a URL for all types of registration numbers (it depends on the registry). And if a URL ever changes, it's easier to update the web application than re-synchronise all affected registration numbers to the RIPE database.
Agree, a separate attribute, eg "reg-url" would be the way to go indeed. Maybe a "reg-country" option separately to indicate the country could be useful (e.g. in the case of Germany as one example), while the "reg-url" could point directly to the registration entity's site. It would also allow easily grouping which registry each comes from, thus per URL, similar to 'source'. To then automate or so automatic fetching would be something the user can do. though most of these sites do not allow automation and require payment, but that is then upto the client to handle, RIPE NCC should not be bothered with that.
At least, it will solve the big problem of companies claiming to have a POBox in one country and then having their "company" registered in the fun countries that do not seem to have any legal process or escalation paths whatsoever. Unfortunately there are many of those.
Correct, in addition to the legal country attribute, the aim is to make it easier to identify the resource holder.
One additional thing would be as it is not GPDR sensitive, that this information is also exposed in a DB dump, so that one can easily take such a dump, and mark prefixes as 'fun traffic'. This will help with scoring in various locations to what extent traffic might actually just be anonymous / disrespecting of the law or not. And yes, it sucks then for entities that are actually located in those countries, they are trying to get by and sucked into that too :(...
If I understand correctly, this is already possible using the country: attribute which identifies the legal address of the resource holder organisation.
Not for quite a few who have "POBoxes" in countries other than the registry is claimed to be a "registered company". These additions will make all that much more visible though, thanks! Greets, Jeroen