WHOIS IP — full information about ip-address and subnets.

The WHOIS IP service makes it possible to determine which person or organization owns a particular ip-address, what range of ip-addresses belongs to this organization, and you can see information about the belonging of subnets of classes such as B and C. In addition, with WHOIS IP, you can determine who is administering Class A subnets.


Structure of WHOIS IP records
Inetnum Contains information about the assignment and allocation of IPv4 address space.
netname The name of the network.
descr The full name of the organization.
country ISO-3166 code of the country in which the network is located.
admin-c Identifier of the organization representative for administrative contact.
tech-c The name of the contact person of technical personnel (organization).
status The possible values for this attribute are:
ALLOCATED PA: This address space was allocated to the LIR, and no assignment or sub-selection made from it is portable. Assignments and sub-selections can not be saved when switching to another vendor.
ALLOCATED PI: This address space has been allocated to LIR or RIR, and all assignments made therefrom are portable. Assignments can be saved for as long as the original assignment criterion preserves the effect. Sub-selection from this type of address space can not be performed.
ALLOCATED UNSPECIFIED: This address space was allocated by LIR or RIR. Assignments can be PA or PI. This status is intended for documenting past allocations, where there are assignments of both types. It is not used for new ones. Sub-selection from this type of address space can not be performed.
SUB-ALLOCATED PA: This LIR address space is sub-allocated for the network operator, which will produce the destination from it. All assignments made therefrom are PA. They can not be saved when switching to another vendor.
LIR-PARTITIONED PA: This allows the LIR to document the allocation and transfer control of the allocated space within its organization. The address space with the LIR-PARTITIONED status is not considered to be used. When addresses are used, a more specific inetnum must be registered.
LIR-PARTITIONED PI: This allows the LIR to document the allocation and transfer control of the allocated space within its organization. The address space with the LIR-PARTITIONED status is not considered to be used. When addresses are used, a more specific inetnum must be registered.
EARLY-REGISTRATION: This is used by the RIPE database administration when transferring the era registrations to the RIR from the ARIN database. This value can be changed by database users. Only RIPE database administrators can create objects with this value.
NOT-SET: This means that the registration was made before the "status:" attribute became mandatory for inetnum objects. The object has not been adjusted since. New objects can not be created with this value. The value can be changed by database users.
ASSIGNED PA: This address space was assigned to the end user to use the services provided by the issuing LIR. It can not be saved after the use of the services provided by this LIR is completed.
ASSIGNED PI: This address space was assigned to the end user and can be stored for it as long as desired, as long as the original destination criterion is valid.

Creating an inetnum object with the status "ASSIGNED PA" or "ASSIGNED PI" is possible only if there is no smaller or larger space-specific address of the inetnum object with the status "ASSIGNED". The address space without an explicitly specified type in the attribute "status:" is taken as PI. LIRs should clearly label all new assignments in the RIPE database as "PA" or "PI", respectively. The RIPE NCC no longer allocates the PI address space. Consequently, many LIRs do not have PI addresses allocated to them, from which they can assign PI addresses. If the LIR has an end user who requires PI address space, it can support it by sending requests to the RIPE NCC from the end user's name. This support includes helping end-users prepare an appropriately documented request. RIPE NCC will assign PI addresses when it is justified.
mnt-by This field is required. Using the maintainer allows you to protect the network information in the RIPE database using various methods of authorizing the requestor to create / modify / delete an object in the RIPE database (more about the maintainer). Usually, the provider maintainer / Registry is used.
changed E-mail address of the person who last changed the application.
created Date of creation.
last-modified Last modified date.
Source Indicates the registrar with which this object is registered. For the RIPE database, the value of this attribute must be "RIPE".
Person It is a list of at least 2 words separated by a space. The first and last words can not end with a period. The following words are not allowed: "Dr", "Prof", "Mv", "Ms", "Mr", etc., regardless of whether they end with a dot or not. The word consists of letters, numbers, underscores "_ " and dashes "- ". The first character of the name must be a letter, and the last one should be a letter or a digit.
address Full postal address of the contact person.
phone Contact number.
e-mail E-mail address.
nic-hdl Denotes the NIC-nickname of the role or person. When creating an object, you can specify that the NIC-nickname will be automatically generated. Usually it looks like this: from 2 to 4 letters, then to 5 digits and after "-" follows the source specifier.
mnt-by This field is required. Using the maintainer allows you to protect information about your network in the RIPE database using various methods of authorizing the requestor to create / modify / delete an object in the RIPE database (more about the maintainer). Usually, the provider maintainer / Registry is used.
changed E-mail address of the person who last changed the application.
origin Unique number AS.

Facebook VKontakte Twitter Google+ Blogger Delicious LinkedIn Pinterest Print