Registrant Contact Information Policy (2010-07)

PDF version

Policy No: 2010-07
Publication Date: 20/12/2010
Status: Current

1. BACKGROUND

1.1 This document sets out auDA's policy on the collection and maintenance of registrant contact information in the registry database (known as "contact objects") in the open 2LDs (asn.au, com.au, id.au, net.au, org.au) and the community geographic 2LDs (act.au, qld.au, nsw.au, nt.au, sa.au, tas.au, vic.au, wa.au).

1.2 This document does not detail the technical steps required to create, update, transfer or delete a contact object in the registry database. This information is contained in the registry's technical procedures manual, which is made available to all auDA accredited registrars.

2. COLLECTION OF REGISTRANT CONTACT INFORMATION

2.1 Registrant contact information must be collected by the registrar at the time the domain name is registered.

2.2 There are four types of contact object stored in the registry database. The table below indicates the information that registrars must enter for each contact object.

Contact Object

Information to be entered by Registrar

Registrant Contact

MANDATORY

Contact person or role (eg. "General Manager") nominated by the registrant. In the case of individual registrants, must be the registrant himself or herself. In the case of corporate registrants, must be a principal, employee or member of the registrant.

MUST NOT be the registrar of record or their reseller, unless the registrar or reseller has received express written consent from the registrant in that regard (refer to section 4 below).

Technical Contact

MANDATORY

Contact person or role (eg. "General Manager") nominated by the registrant.

May be the registrar of record or their reseller.

Administrative Contact

OPTIONAL

Contact person or role (eg. "General Manager") nominated by the registrant.

May be the registrar of record or their reseller.

Billing Contact

OPTIONAL

Contact person or role (eg. "General Manager") nominated by the registrant.

May be the registrar of record or their reseller.

2.3 The sole purpose of the Registrant Contact and Technical Contact fields is to provide general contact details and technical contact details for the registrant.

2.4 Registrants must not:

a) use the Registrant Contact or Technical Contact fields for any purpose other than as set out in paragraph 2.3. In particular, the Registrant Contact and Technical Contact fields must not contact any data which can be construed as advertising, marketing, promotion or listings of any kind (eg. "This domain name is for sale", "Renew your domain name at [name of provider])"; or

b) do anything which may have the effect of concealing the true identity of the registrant or the registrant contact (eg. by using a private or proxy registration service), unless specifically permitted otherwise by another auDA published policy.

3. MAINTENANCE OF REGISTRANT CONTACT INFORMATION

3.1 Under the Registrant Agreement, registrants are obliged to notify the registry, through the registrar, of any changes to their information. The Certificate of Registration includes a statement that failure to notify changes to contact or other information may result in revocation of the registrant's domain name licence.

3.2 Under the Registrar Agreement, registrars must update registrant data in the registry database within 5 business days of receiving the updated information from the registrant.

4. PROHIBITION ON REGISTRARS AND RESELLERS USING THEIR OWN CONTACT DETAILS AS REGISTRANT CONTACT INFORMATION

4.1 It is a fundamental policy principle that registrant contact information must belong to the registrant, for two main reasons:

a) to ensure that the registrant receives important information in relation to their domain name, including domain name renewal notices, from their registrar of record or from auDA; and

b) to enable the registrant to retrieve their domain name password if they wish to transfer their domain name to another registrar.

4.2 Registrars and resellers are not permitted to use their own contact details as registrant contact information, unless they have received express written consent from the registrant in that regard.

4.3 Where a registrar is notified by auDA that a reseller is using their own contact details as registrant contact information, without express written consent from the registrant, the registrar must update the registrant contact information to be compliant with this policy.

Last Updated: 20/12/2010 12:06