as-block

Range of AS numbers.
-

descr

A short decription related to the object. A sequence of ASCII characters.

remarks

Contains remarks.A sequence of ASCII characters.

org

Points to an existing organisation object representing the entity that holds the resource. The 'ORG-' string followed by 2 to 4 characters, followed by up to 5 digits followed by a source specification. The first digit must not be "0". Source specification starts with "-" followed by source name up to 9-character length.

admin-c

References an on-site administrative contact. From 2 to 4 characters optionally followed by up to 5 digits optionally followed by a source specification. The first digit must not be "0". Source specification starts with "-" followed by source name up to 9-character length.

tech-c

References a technical contact. From 2 to 4 characters optionally followed by up to 5 digits optionally followed by a source specification. The first digit must not be "0". Source specification starts with "-" followed by source name up to 9-character length.

zone-c

References a zone contact. From 2 to 4 characters optionally followed by up to 5 digits optionally followed by a source specification. The first digit must not be "0". Source specification starts with "-" followed by source name up to 9-character length.

notify

Specifies the e-mail address to which notifications of changes to an object should be sent. This attribute is filtered from the default whois output. An e-mail address as defined in RFC 2822.

mnt-by

Specifies the identifier of a registered mntner object used for authorisation of operations performed with the object that contains this attribute.
Made up of letters, digits, the character underscore "_", and the character hyphen "-"; the first character of a name must be a letter, and the last character of a name must be a letter or a digit. The following words are reserved by RPSL, and they can not be used as names: any as-any rs-any peeras and or not atomic from to at action accept announce except refine networks into inbound outbound Names starting with certain prefixes are reserved for certain object types. Names starting with "as-" are reserved for as set names. Names starting with "rs-" are reserved for route set names. Names starting with "rtrs-" are reserved for router set names. Names starting with "fltr-" are reserved for filter set names. Names starting with "prng-" are reserved for peering set names. Names starting with "irt-" are reserved for irt names.

mnt-lower

Specifies the identifier of a registered mntner object used for hierarchical authorisation.
Protects creation of objects directly (one level) below in the hierarchy of an object type. The authentication method of this maintainer object will then be used upon creation of any object directly below the object that contains the "mnt-lower:" attribute. Made up of letters, digits, the character underscore "_", and the character hyphen "-"; the first character of a name must be a letter, and the last character of a name must be a letter or a digit. The following words are reserved by RPSL, and they can not be used as names: any as-any rs-any peeras and or not atomic from to at action accept announce except refine networks into inbound outbound Names starting with certain prefixes are reserved for certain object types. Names starting with "as-" are reserved for as set names. Names starting with "rs-" are reserved for route set names. Names starting with "rtrs-" are reserved for router set names. Names starting with "fltr-" are reserved for filter set names. Names starting with "prng-" are reserved for peering set names. Names starting with "irt-" are reserved for irt names.

mnt-ref

Specifies the maintainer objects that are entitled to add references to the organisation object from other objects. Made up of letters, digits, the character underscore "_", and the character hyphen "-"; the first character of a name must be a letter, and the last character of a name must be a letter or a digit. The following words are reserved by RPSL, and they can not be used as names: any as-any rs-any peeras and or not atomic from to at action accept announce except refine networks into inbound outbound Names starting with certain prefixes are reserved for certain object types. Names starting with "as-" are reserved for as set names. Names starting with "rs-" are reserved for route set names. Names starting with "rtrs-" are reserved for router set names. Names starting with "fltr-" are reserved for filter set names. Names starting with "prng-" are reserved for peering set names. Names starting with "irt-" are reserved for irt names.

changed

Specifies who submitted the update, and when the object was updated. This attribute is filtered from the default whois output. An e-mail address as defined in RFC 2822, followed by a date in the format YYYYMMDD.

source

Specifies the registry where the object is registered. Should be "AFRINIC" for the AFRINIC Database. Made up of letters, digits, the character underscore "_", and the character hyphen "-"; the first character of a registry name must be a letter, and the last character of a registry name must be a letter or a digit.

members

Lists the members of the set. or

mbrs-by-ref

This attribute can be used in all "set" objects; it allows indirect population of a set. If this attribute is used, the set also includes objects of the corresponding type (aut-num objects for as-set, for example) that are protected by one of these maintainers and whose "member-of:"attributes refer to the name of the set. If the value of a "mbrs-by-ref:" attribute is ANY, any object of the corresponding type referring to the set is a member of the set. If the "mbrs-by-ref:" attribute is missing, the set is defined explicitly by the "members:" attribute. | ANY remarks Contains

aut-num

The autonomous system number. An "AS" string followed by an integer in the range from 1 to 65534

as-name

A descriptive name associated with an AS. Made up of letters, digits, the character underscore "_", and the character hyphen "-"; the first character of a name must be a letter, and the last character of a name must be a letter or a digit. The following words are reserved by RPSL, and they can not be used as names: any as-any rs-any peeras and or not atomic from to at action accept announce except refine networks into inbound outbound Names starting with certain prefixes are reserved for certain object types. Names starting with "as-" are reserved for as set names. Names starting with "rs-" are reserved for route set names. Names starting with "rtrs-" are reserved for router set names. Names starting with "fltr-" are reserved for filter set names. Names starting with "prng-" are reserved for peering set names. Names starting with "irt-" are reserved for irt names.

mnt-routes

This attribute references a maintainer object which is used in determining authorisation for the creation of route6 objects. This entry is for the mnt-routes attribute of aut-num class. After the reference to the maintainer, an optional list of prefix ranges inside of curly braces or the keyword "ANY" may follow. The default, when no additional set items are specified, is "ANY" or all more specifics.

[ { list of (/or /) } | ANY ]

nserver

Specifies the nameservers of the domain. Nameserver name as specified in RFC 1034 with or without trailing dot ("."). The total length should not exceed 254 characters (octets). The nameserver name may be optionally followed by IPv4 address in decimal dotted quad form (e.g. 192.0.2.1) or IPv6 address in lowercase canonical form (Section 2.2.1, RFC 4291). The nameserver name may be followed by an IP address only when the name is inside of the domain being delegated.

sub-dom

Specifies list of sub-domains of a domain. Domain names are relative to the domain represented by the domain object that contains this attribute. Domain name as specified in RFC 1034 with or without trailing dot ("."). The total length should not exceed 254 characters (octets).

dom-net

List of IP networks in a domain. An IPv4 address is represented as a sequence of four integers in the range from 0 to 255 separated by the character dot ("."). For example, 128.9.128.5 represents a valid IPv4 address.

refer

Specifies the referral type, hostname and port that the server should use to redirect the query when using referral mechanism for lookups for domain objects.[]specifies the type of referral to be used. Supported types are SIMPLE, INTERNIC, RIPE, and CLIENTADDRESS.is the DNS name orof the referred host.is an integer specifying TCP port number at which queries are accepted by the referred host. Ifis omitted, the default number of 43 is used.

inet6num

Specifies a range of IPv6 addresses in prefix notation. /

country

Identifies the country. Valid two-letter ISO 3166 country code.

rev-srv

Specifies a DNS nameserver for a range of IP addresses represented by the inetnum object that contains this attribute. Domain name as specified in RFC 1034 with or without trailing dot ("."). The total length should not exceed 254 characters (octets). status Specifies the status of the address range represented by inetnum or inet6num object. Status can have one of these values:

ref-nfy

Specifies the e-mail address to be notified when a reference to the organisation object is added or removed. This attribute is filtered from the default whois output when at least one of the objects returned by the query contains an abuse-mailbox attribute. An e-mail address as defined in RFC 2822.

status for inet6num

Specifies the status of the address range represented by inetnum or inet6num object.

Status can have one of these values:

o ALLOCATED-BY-RIR
o ASSIGNED PA
o ASSIGNED PI

status for inetnum

o SUB-ALLOCATED PA
o NOT-SET
o EARLY-REGISTRATION
o ALLOCATED PA
o ALLOCATED PI
o UNSPECIFIED
o ASSIGNED PA
o ASSIGNED PI

mnt-domains

Specifies the identifier of a registered mntner object used for reverse domain authorization. Protects domain objects. The authentication method of this maintainer object will be used for any encompassing reverse domain object. Made up of letters, digits, the character underscore "_", and the character hyphen "-"; the first character of a name must be a letter, and the last character of a name must be a letter or a digit. The following words are reserved by RPSL, and they can not be used as names: any as-any rs-any peeras and or not atomic from to at action accept announce except refine networks into inbound outbound Names starting with certain prefixes are reserved for certain object types. Names starting with "as-" are reserved for as set names. Names starting with "rs-" are reserved for route set names. Names starting with "rtrs-" are reserved for router set names. Names starting with "fltr-" are reserved for filter set names. Names starting with "prng-" are reserved for peering set names. Names starting with "irt-" are reserved for irt names.

mnt-irt

May appear in an inetnum or inet6num object. It points to an irt object representing a Computer Security Incident Response Team (CSIRT) that handles security incidents for the address space specified by the inetnum or inet6num object. An irt name is made up of letters, digits, the character underscore "_", and the character hyphen "-"; it must start with "irt-", and the last character of a name must be a letter or a digit.

inetnum

Specifies a range of IPv4 that inetnum object presents. The ending address should be greater than the starting one.

-

key-cert

Defines the public key stored in the database. PGPKEY- is the PGP key ID of the public key in 8-digit hexadecimal format without "0x" prefix.

method

Defines the type of the public key. Currently, only PGP keys are supported.

owner

Specifies the owner of the public key. A sequence of ASCII characters.

fingerpr

A fingerprint of a key certificate generated by the database. Attribute generated by server.

certif

Contains the public key. The value of the public key should be supplied either using multiple "certif:" attributes, or in one "certif:" attribute. In the first case, this is easily done by exporting the key from your local key ring in ASCII armored format and prepending each line of the key with the string "certif:". In the second case, line continuation should be used to represent an ASCII armored format of the key. All the lines of the exported key must be included; also the begin and end markers and the empty line which separates the header from the key body.

limerick

Specifies the title of the limerick. LIM-can include alphanumeric characters, and "_" and "-" characters.

text

Text of the limerick. Must be humorous, but not malicious or insulting. A sequence of ASCII characters.

author

References a limerick author. From 2 to 4 characters optionally followed by up to 5 digits optionally followed by a source specification. The first digit must not be "0". Source specification starts with "-" followed by source name up to 9-character length.

role

Specifies the full name of a role entity, e.g. AFRINIC DBM. A list of at least 2 words separated by white space. The first and the last word cannot end with dot ("."). The following words are not allowed: "Dr", "Prof", "Mv", "Ms", "Mr", no matter whether they end with dot (".") or not. A word is made up of letters, digits, the character underscore "_", and the character hyphen "-"; the first character of a name must be a letter, and the last character of a name must be a letter or a digit.

address

Full postal address of a contact. A sequence of ASCII characters.

phone

Specifies a telephone number of the contact. Contact telephone number. Can take one of the forms: '+' '+' "(" ")" '+' ext.'+' "(" integer list ")" ext.

fax-no

The fax number of a contact. Contact telephone number. Can take one of the forms: '+' '+' "(" ")" '+' ext.'+' "(" integer list ")" ext.

e-mail

The e-mail address of a person, role, organisation or irt team. This attribute is filtered from the default whois output when at least one of the objects returned by the query contains an abuse-mailbox attribute. An e-mail address as defined in RFC 2822.

organisation

Specifies the ID of an organisation object. When creating an object, one has to specify an "AUTO" ID by setting the value of the attribute to "AUTO-1" or "AUTO-1, so the database will assign the ID automatically. The 'ORG-' string followed by 2 to 4 characters, followed by up to 5 digits followed by a source specification. The first digit must not be "0". Source specification starts with "-" followed by source name up to 9-character length.

org-name

Specifies the name of the organisation that this organisation object represents in the whois database. This is an ASCII-only text attribute. The restriction is because this attribute is a look-up key and the whois protocol does not allow specifying character sets in queries. The user can put the name of the organisation in non-ASCII character sets in the "descr:" attribute if required. A list of words separated by white space. A word is made up of letters, digits, the character underscore "_", and the character hyphen "-"; the first character of a word must be a letter or digit; the last character of a word must be a letter, digit or a dot.

org-type

Specifies the type of the organisation.

org-type can have one of these values:

o IANA
o RIR
o LIR
o EU-PI
o EU-AS
o MEMBER-ONLY

as-set

Defines the name of the set.

An as-set name is made up of letters, digits, the character underscore "_", and the character hyphen "-"; it must start with "as-", and the last character of a name must be a letter or a digit.

An as-set name can also be hierarchical. A hierarchical set name is a sequence of set names and AS numbers separated by colons ":". At least one component of such a name must be an actual set name (i.e. start with "as-"). All the set name components of a hierarchical as-name have to be as-set names.

domain

Domain name.

Domain name as specified in RFC 1034 with or without trailing dot ("."). The total length should not exceed 254 characters (octets).

netname

The name of a range of IP address space. Made up of letters, digits, the character underscore "_", and the character hyphen "-"; the first character of a name must be a letter, and the last character of a name must be a letter or a digit.

mntner

A unique identifier of the mntner object.

Made up of letters, digits, the character underscore "_", and the character hyphen "-"; the first character of a name must be a letter, and the last character of a name must be a letter or a digit. The following words are reserved by RPSL, and they can not be used as names: any as-any rs-any peeras and or not atomic from to at action accept announce except refine networks into inbound outbound Names starting with certain prefixes are reserved for certain object types. Names starting with "as-" are reserved for as set names. Names starting with "rs-" are reserved for route set names. Names starting with "rtrs-" are reserved for router set names. Names starting with "fltr-" are reserved for filter set names. Names starting with "prng-" are reserved for peering set names. Names starting with "irt-" are reserved for irt names.

upd-to

Specifies the e-mail address to be notified when an object protected by a mntner is unsuccessfully updated. An e-mail address as defined in RFC 2822.

auth

Defines an authentication scheme to be used.

Description

CRYPT-PW encrypted This scheme is our weeakest form password, produced of authentication. It is by by UNIX crypt(3) no means meant to keep out a routine determined malicious attacker. The crypt function is vulnerable to exhaustive search by (lots of) fast machines and programs to do the searching are widely available. For this reason it is strongly discouraged to use encrypted passwords also used for other purposes such as UNIX login accounts in this scheme. As you are publishing the encrypted password in the database, it is open to attack. The usual caveats about crypt passwords apply, so it is not very wise to use words or combinations of words found in any dictionary of any language.

MD5-PW encrypted This scheme is similar to the CRYPT-PW password, produced scheme, except that it uses an MD5 using the FreeBSD hash rather than DES encryption to crypt_md5 generate the password. The main algorithm benefit over CRYPT-PW is that pass phrases longer than 8 characters may be used. All of the dangers of CRYPT-PW also apply to MD5-PW.

referral-by

This attribute is required in the maintainer object. It may never be altered after the addition of the maintainer. This attribute refers to the maintainer that created this maintainer. It may be multiple if more than one signature appeared on the transaction creating the object. Made up of letters, digits, the character underscore "_", and the character hyphen "-"; the first character of a name must be a letter, and the last character of a name must be a letter or a digit. The following words are reserved by RPSL, and they can not be used as names: any as-any rs-any peeras and or not atomic from to at action accept announce except refine networks into inbound outbound Names starting with certain prefixes are reserved for certain object types. Names starting with "as-" are reserved for as set names. Names starting with "rs-" are reserved for route set names. Names starting with "rtrs-" are reserved for router set names. Names starting with "fltr-" are reserved for filter set names. Names starting with "prng-" are reserved for peering set names. Names starting with "irt-" are reserved for irt names.

person

Specifies the full name of an administrative, technical or zone contact person for other objects in the database. Person name cannot contain titles such as "Dr.", "Prof.", "Mv.", "Ms.", "Mr.", etc. It is composed of alphabetic characters. A list of at least 2 words separated by white space. The first and the last word cannot end with dot ("."). The following words are not allowed: "Dr", "Prof", "Mv", "Ms", "Mr", no matter whether they end with dot (".") or not. A word is made up of letters, digits, the character underscore "_", and the character hyphen "-"; the first character of a name must be a letter, and the last character of a name must be a letter or a digit.

nic-hdl

Specifies the NIC handle of a role or person object. When creating an object, one can also specify an "AUTO" NIC handle by setting the value of the attribute to "AUTO-1" or AUTO-1. In such case the database will assign the NIC handle automatically. From 2 to 4 characters optionally followed by up to 5 digits optionally followed by a source specification. The first digit must not be "0". Source specification starts with "-" followed by source name up to 9-character length.