Notice

About result of query:

1. Duplicated records are displayed only one time for status and roles fields, but not for other fields.

About the process:

1. NFKC is provided only in the domain and nameserver query or search,and these parameters are stored in the database after formatted by NFKC,and all letters must be lowercase.
2. For unicode character in domain and nameserver search，query them directly instead of encode by punycode.
3. For [tel] field in {vcard} section and is irregular,it is not displayed. If it is in {entity} section,the rule is:
   • <1> MUST start with +
   • <2> contains one digital number at least
   • <3> composed of - . ( ) and digital number after +
   • <4> composed of - . ( ) and digital number in extention part
4. For [entities] nested in {entity}，if the inner entity is the same with the outer entity,we do not display it.
5. For the space character before or after the url parameter in querying {entity}, we trim the space.
6. Count the reverse domain in the nameserver as the common domain, that is, not query reverse nameserver by its original-network.
7. For redirection to multi-ip,display only one in the return Header Location.The only one is the first item of the result which queried from database.
8. Redirect: For domain and nameserver query,if the url parameter does not belong to a registry,redirect it. For ip and autnum query,if it does not exist in the database,redirect it. If the url which is redirected is the same with your server,return 404.Otherwise,return 301.

About source data:

1. If the [ref] field value is "self" or "related",the [type] field value MUST be "application/rdap+json". The source data provider MUST keep this relationship correctly.
2. 'description' is required in Notices ,remarks,help.Once the fields value from RDAP_NOTICE is unconsistent with the ones from RDAP_NOTICE_DESCRIPTION,the description field will not be displayed.
   • NOTICE: if the source data from database is unconsistent with the requirement,we still display them.
3. It is suggested that / ? and * characters can not be displayed in [handle] and [fn] field when query entity.
4. If the high ip address in ipv6 is NULL in the database,this item is not considered as a query result. So is the case which the low ip address in ipv4 is larger than 2 to the power of 32.

Others:

1. The policy configuration will be functional after restart the system. If a field which is required is also in the policy configuration,the field still complies with policy. It is strongly suggested that do not put the required field in the policy.
2. Conformance and errormessage service will take effect after restart the system.
3. The system does not verify the HTTP version.
4. The system does not support the share of resource cross-domain.
5. Tested Operating environment:Red Hat Enterprise Linux Server release 5.3; CentOS release 5.7; Windows7; Windows8