2002-17 - Guidelines for Accredited Registrars on the Interpretation of Policy Rules for Open 2LDs
Policy No: 2002-17
Publication Date: 28/06/2002
Status: Replaced by Policy No 2003-07
1. BACKGROUND
1.1 This document sets out guidelines for auDA accredited registrars on the interpretation of the Domain Name Eligibility and Allocation policy rules for the open 2LDs. At the time of publication, the open 2LDs are asn.au, com.au, id.au, net.au and org.au. The Domain Name Eligibility and Allocation policy rules are available on auDA's web site at http://www.auda.org.au/policy
2. PURPOSE OF GUIDELINES
2.1 The policy rules for the open 2LDs are divided into two types of criteria:
a) Eligibility - is the registrant eligible to license a domain name in the requested 2LD?; and
b) Allocation - can the requested domain name be allocated to the registrant?
2.2 The Eligibility criteria require the registrant to provide the relevant identification details for the 2LD that they want to license their domain name in. For example, if the registrant wants to license a domain name in com.au, they must provide identification details such as Australian registered company name and Australian Company Number (ACN).
2.3 The Allocation criteria require the registrant to give a reason why the requested domain name can be allocated to them. The reasons available in each 2LD are:
a) exact match of the registrant's name; or
b) abbreviation or acronym of registrant's name; or
c) close and substantial connection to the registrant.
2.4 The purpose of these guidelines is to provide clarification for registrars on how the Eligibility and Allocation criteria of the policy should be interpreted.
3. DOMAIN NAME APPLICATIONS
3.1 Registrars may design their own domain name application form for registrants.
3.2 Application forms should prompt the registrant to provide all the information that the registrar needs to make a responsible decision about whether or not the application meets the policy rules. In some cases, registrars will be able to make a decision based on minimal information. For example, a registrar may be able to determine that a registrant called "Jane the Florist Pty Ltd" has a close and substantial connection with the domain name "janesflowers.com.au", without requesting further information from the registrant. In other cases, registrars will need to seek more information to support the registrant's claims. For example, a registrar would not be able to determine that a registrant called "Jane's Shop Pty Ltd" has a close and substantial connection with the domain name "janesflowers.com.au", without obtaining further information from the registrant about their business activities.
3.3 As a matter of best practice, registrars are advised to make sure that they collect sufficient information to enable them to explain or justify their decision in the case of dispute, or if requested to do so by auDA under the terms and conditions of the Registrar Agreement.
3.4 Application forms should also include a warranty statement that the registrant must agree to before they submit the application. An example of a warranty statement is provided at Schedule A of this document.
3.5 Each domain name application must be assessed on its own merits. It is not acceptable for the registrant merely to refer to previous decisions in order to support their claims. For example, the mere fact that a registrant called "Jane's Shop Pty Ltd" was able to license "janesflowers.com.au" is not sufficient to support the claims of "John's Shop Pty Ltd" to license "johnsflowers.com.au".
4. RULES FOR ALL OPEN 2LDS
4.1 Before determining that a domain name application meets the specific Eligibility and Allocation criteria for the particular 2LD, registrars must check that each domain name application complies with the general rules that apply in all open 2LDs.
4.2 Domain names are allocated on a "first come, first served" basis. Provided that the registrant meets the relevant policy rules, the registrar may process the registration and issue a domain name licence to the registrant. Registrars are not required to decide whether or not the domain name potentially infringes the rights of a third party.
4.3 Registrars must check that the requested domain name:
a) is from 2 to 63 characters long;
b) contains only letters (a-z), numbers (0-9) or hyphens (-), or a combination of these;
c) starts and ends with a letter or a number, not a hyphen; and
d) does not contain hyphens in the third and fourth position (eg. ab--cd.com.au).
4.4 In addition, registrars must check that the requested domain name is not on auDA's reserved list. The reserved list is available on auDA's web site at http://www.auda.org.au/policy. The list mostly contains words that are restricted by statute. It also contains existing gTLDs and ccTLDs.
4.5 auDA's reserved list does not contain objectionable words. Registrars are not required to decide whether or not a domain name is potentially objectionable. However, auDA supports the right of registrars to choose not to process a domain name registration if it breaches their own "acceptable use" policy.
5. VERIFICATION OF REGISTRANT ELIGIBILITY CRITERIA
5.1 Registrants must provide sufficient identification to demonstrate that they meet the eligibility criteria for the particular 2LD. Registrars must verify the registrant's identification details to confirm that the registrant meets the eligibility criteria. The table in Schedule B lists the registrant types for each 2LD, the identification details to be provided by the registrant, and the verification source that registrars must use to check those details.
5.2 Most verification sources are available online, however there are a couple of cases where the registrar must obtain further documentation from the registrant, as follows:
a) incorporated associations that are not listed on the Australian Securities and Investments Commission (ASIC) database must provide a copy of their Certificate of Incorporation; and
b) commercial statutory bodies must provide a copy (or extract) of the relevant Act of Parliament.
5.3 When verifying registrant details on official databases, registrars should check the status entry, as follows:
a) on the ASIC database, "association strike off status (ASOS), "de-registered (DRGD)", "pending (PEND)", "removed (RMVD)" and "reserved (RSVD)" are not an acceptable basis for domain name registration ; and
b) on the Australian Trade Mark Online Search System (ATMOSS), "refused", "rejected", "removed" and "never registered" are not an acceptable basis for domain name registration.
5.4 In cases where there is no verification source available, registrars are entitled to rely on the registrant's warranty that they meet the eligibility criteria, as follows:
a) sporting and special interest clubs that do not have an Australian Business Number must warrant that they are a club;
b) registrants in id.au must warrant that they are an Australian citizen or resident; and
c) non-profit organisations, in addition to providing the identification details relevant to their corporate status, must warrant that they are non-profit.
5.5 It is not necessary to obtain a statutory declaration from the registrant. Where a registrant has made a false warranty, or otherwise acted in bad faith in order to obtain the domain name licence, auDA reserves the right to revoke the domain name licence.
5.6 Please note that registrars are expected to act with integrity and use their common sense in determining whether the registrant's warranty is bona fide. Under the terms and conditions of the Registrar Agreement, auDA reserves the right to take action against a registrar where it has reasonable grounds to believe that the registrar has acted negligently or recklessly in approving a domain name application in breach of the relevant policy rules.
6. ALLOCATION CRITERIA - MEANING OF "EXACT MATCH"
6.1 An "exact match" is where the requested domain name matches one, some or all of the words comprising the name used by the registrant to establish their eligibility. The words must be used in the same order as they appear in the name. Refer to the examples in Schedule C.
7. ALLOCATION CRITERIA - MEANING OF "ABBREVIATION"
7.1 An "abbreviation" is where the requested domain name is used to represent or stand for the complete form, of the name used by the registrant to establish their eligibility. The abbreviation can contain letters or numbers that do not appear in the registrant's name. Words do not have to be used in the same order as they appear in the name. Refer to the examples in Schedule C.
7.2 Please note that this rule is NOT the same as the old derivation rule in com.au and net.au, which allows registrants to derive a domain name that is entirely unrelated to their own name by using a consecutive sequence of letters. The abbreviation must "represent or stand for the complete form". This means that the abbreviation must be a close approximation of, and have a related meaning to, the complete form. A "close approximation" refers to the way the words look. In general, partial words or words that contain the same letters in a similar sequence will be a close approximation. "Related meaning" refers to the accepted dictionary definition of the words. Although there might be a close approximation between the words, derivations are not acceptable if there is no related meaning. Similarly, although there might be a related meaning between the words, synonyms are not acceptable if there is no close approximation.
7.3 In the case of personal names, common alternatives may be acceptable as abbreviations, even if there is no obvious connection. This is most likely to occur in the case of non-English names. For example, a registrant called "Yahnni" could license "john.id.au" because "John" is the English version of "Yahnni". Registrars are not expected to have an exhaustive knowledge of common alternatives for personal names, but are entitled to rely on the registrant's warranty. Where a registrant has made a false warranty, or otherwise acted in bad faith in order to obtain the domain name licence, auDA reserves the right to revoke the domain name licence. In addition, an aggrieved party has the right to file a complaint against the registrant under the .au Dispute Resolution Policy (auDRP).
7.4 Please note, however, that registrars are expected to act with integrity and use their common sense in determining whether the registrant's warranty is bona fide. Under the terms and conditions of the Registrar Agreement, auDA reserves the right to take action against a registrar where it has reasonable grounds to believe that the registrar has acted negligently or recklessly in approving a domain name application in breach of the relevant policy rules. As noted in paragraph 3.3, registrars are advised to make sure that they collect sufficient information to enable them to explain or justify their decision in the case of dispute, or if requested to do so by auDA under the Registrar Agreement.
8. ALLOCATION CRITERIA - MEANING OF "ACRONYM"
8.1 An "acronym" is where the requested domain name comprises the initial letters only of each word of the name used by the registrant to establish their eligibility. If the requested domain name comprises more than the initial letters of each word, then it will most likely fall within the definition of abbreviation (for example, "auda.org.au" is an abbreviation of .au Domain Administration Ltd, not an acronym). Refer to the examples in Schedule C.
8.2 Please note the following qualifications:
- Commercial status identifiers such as "Pty Ltd" or "Co" do not need to be included.
- DNS identifiers such as ".com.au" do not need to be included.
- Pronouns such as "a", "the", "and" or "of" do not need to be included.
9. ALLOCATION CRITERIA - MEANING OF "CLOSE AND SUBSTANTIAL CONNECTION"
9.1 A "close and substantial connection" is where the requested domain name is connected to the registrant in accordance with the listed categories for each 2LD.
9.2 The purpose of the close and substantial connection rule is to allow some flexibility for registrants who do not want to license a domain name that is directly related to their name (or cannot do so, because the domain name has already been licensed by another registrant with the same or similar name). It is important to note that this rule is NOT intended as a "free for all", and the degree of flexibility is limited by the categories of close and substantial connection outlined in the policy rules.
9.3 The close and substantial connection rule is inherently subjective and registrars often will be required to make their own judgements about whether the requested domain name should be allocated to the registrant. Beyond seeking further information or clarification from the registrant where necessary, registrars are not required to take action to investigate the registrant's claims. For example, a registrar is not required to visit the premises of "Jane's Shop Pty Ltd" to verify that the registrant sells flowers and is thus eligible to license "janesflowers.com.au". Registrars are entitled to rely on the registrant's warranty. Where a registrant has made a false warranty, or otherwise acted in bad faith in order to obtain the domain name licence, auDA reserves the right to revoke the domain name licence. In addition, an aggrieved party has the right to file a complaint against the registrant under the .au Dispute Resolution Policy (auDRP).
9.4 Please note, however, that registrars are expected to act with integrity and use their common sense in determining whether the registrant's warranty is bona fide. Under the terms and conditions of the Registrar Agreement, auDA reserves the right to take action against a registrar where it has reasonable grounds to believe that the registrar has acted negligently or recklessly in approving a domain name application in breach of the relevant policy rules. As noted in paragraph 3.3, registrars are advised to make sure that they collect sufficient information to enable them to explain or justify their decision in the case of dispute, or if requested to do so by auDA under the Registrar Agreement.
Close and substantial connection rule - asn.au, com.au, net.au and org.au
9.5 In com.au and net.au,the categories of close and substantial connection are:
a) a product that the registrant manufactures or sells; or
b) a service that the registrant provides; or
c) an event that the registrant organises or sponsors; or
d) an activity that the registrant facilitates, teaches or trains; or
e) a venue that the registrant operates; or
f) a profession that the registrant's employees practise.
9.6 In asn.au and org.au, the categories are:
a) a service that the registrant provides; or
b) a program that the registrant administers; or
c) an event that the registrant organises or sponsors; or
d) an activity that the registrant facilitates, teaches or trains; or
e) a venue that the registrant operates; or
f) a profession that the registrant's members practise.
9.7 The requested domain name does not have to be the same as the registrant's product, service, etc. The domain name must only refer to the registrant's product, service, etc. This allows the registrant to license variations or descriptions of their product, service, etc (for example, "Jane the Florist Pty Ltd" could license "bestflowers.com.au", "flowersonline.net.au", "redroses.com.au", "cheapflowers.net.au" and so on). Refer to the examples in Schedule C.
9.8 The Registrant Agreement (Domain Name Licence), that each registrant must enter into when they register or renew a domain name, places an obligation on the registrant not to register a domain name for the purpose of selling it. Therefore, it is not acceptable for registrants to use the close and substantial connection rule to engage in domain name speculation or warehousing; these practices do not constitute a "service" or an "activity" under the policy rules.
Close and substantial connection rule - id.au
9.9 In id.au, the close and substantial connection rule is deliberately more restrictive than in the other 2LDs, in order to minimise the risk of cybersquatting. There are two categories:
a) derived from one or more words of the registrant's personal name; or
b) includes one or more words of the registrant's personal name.
9.10 Nicknames are only acceptable if they are derived from one or more words of the registrant's personal name, or if they include one or more words of the registrant's personal name. Domain names may include words that do not appear in the registrant's personal name, but only in conjunction with one or more words of the registrant's personal name. Refer to the examples in Schedule C.
9.11 Please note that each category refers back to the registrant's personal name. This means that the registrant can't use an abbreviation or acronym as the basis for a close and substantial connection. For example, "Jonathon Smith" could license "john.id.au" as an abbreviation of his name, but he could not license "johnonline.id.au", because "john" is not a word in his name. Similarly, "Jonathon Smith" could license "js.id.au" as an acronym of his name, but he could not license "js1970.id.au" because "js" is not a word in his name.
10. DOMAIN NAME RENEWALS
10.1 To process a domain name renewal, registrars must obtain confirmation from the registrant that their eligibility details are still current. If the registrant's details have not changed, registrars are not required to perform any policy compliance checks and are entitled to rely on the registrant's warranty that they still meet the relevant policy rules.
10.2 If the registrant's details are no longer current, it may affect their eligibility to hold the domain name licence. The registrar is therefore required to undertake some checks before they can process the renewal. The cases where this is most likely to occur are:
a) Where a business name registration has lapsed. If the registrant is able to re-register the same business name, then the registrar must simply verify that the re-registration has taken place. They do not need to perform any further policy compliance checks, because the registrant's name has not changed.
b) Where a company has been de-registered or a business name has been removed. The registrant is unable to resurrect the original basis for their domain name registration, so they must provide entirely new eligiblity details (eg. a new business name). The registrar must perform full policy compliance checks, because the registrant's new eligibility details may no longer have any connection with the domain name.
c) Where an application for an Australian Registered Trade Mark has not been accepted for registration. The registrant is unable to resurrect the original basis for their domain name registration, so they must provide entirely new eligiblity details (eg. a company or business name). The registrar must perform full policy compliance checks, because the registrant's new eligibility details may no longer have any connection with the domain name.
11. REVIEW OF REGISTRAR DECISIONS
11.1 Where a domain name application has been rejected by a registrar because it does not meet the relevant policy rules, the registrant has the right to seek an independent review of the registrar's decision under auDA's Domain Name Application Appeals Process (AAP). The registrar is not required to take part in this process, however they may choose to file a response if they wish.
11.2 More information about the AAP is available on auDA's web site.
12. POLICY COMPLIANCE - ADVICE AND MONITORING
12.1 As manager of the .au domain, one of auDA's primary responsibilities is to preserve the policy integrity of the .au namespace. auDA intends to fulfil that responsibility in two main ways:
a) by providing advice and assistance to registrars in performing policy compliance checks; and
b) by conducting random audits of domain name registry records on a regular basis.
12.2 Registrars may contact auDA's Chief Policy Officer at any time for advice and assistance in performing policy compliance checks. auDA's intention is that these guidelines will be revised and updated from time to time to reflect the marketplace experience of registrars in dealing with registrants. auDA welcomes and encourages feedback from registrars about the usefulness of these guidelines in particular, as well as the level of support and assistance received from auDA's Chief Policy Officer and other staff.
12.3 Registrars must record the policy reason for each domain name registration in the registry database. This enables auDA to monitor the performance of registrars by conducting random audits of the registry records. It also enables auDA to undertake a full investigation if it receives a complaint or is otherwise notified that a registrar is not performing its policy compliance checks with due care and integrity.
13. REVIEW OF GUIDELINES
13.1 From time to time, auDA may update this document for the purposes of clarification or correction, or to maintain consistency with other auDA published policies. Under the terms and conditions of the Registrar Agreement, there is a 30 day grace period for registrars to comply with any variations of procedures or practices under this document.
SCHEDULE A
EXAMPLE OF REGISTRANT WARRANTY STATEMENT
It is the responsibility of all registrants, in accordance with their registration application and subsequent agreement, to ensure that they satisfy the relevant policy rules. To that end, a registrant is required to warrant to the registrar that they satisfy the rules.
Registrars may use the warranty text provided below in their domain name application form:
By submitting this Application Form, you (the Registrant):
- warrant that all the information contained in this Application Form, and all supporting documents provided to the Registrar, are true and accurate to the best of your knowledge;
- give the Registrar permission to contact third parties, investigate, request and obtain additional information and documentation, and otherwise verify the information contained in this Application Form;
- waive liability on the part of the Registrar for its actions in verifying the information provided in this Application Form, and on the part of any third parties who provide truthful, material, relevant information about you;
- waive liability on the part of the Registrar if your application is accepted or rejected on the basis of any false or misleading information contained in this Application Form;
- acknowledge that if your application is accepted on the basis of any false or misleading information contained in this Application Form, auDA reserves the right to cancel your domain name licence at any time; and
- acknowledge that your entitlement to a domain name may be challenged by a third party with legitimate rights in the domain name.
SCHEDULE B
VERIFICATION OF REGISTRANT ELIGIBILITY
|
Registrant Type |
Registrant ID |
Verification Source |
|
asn.au |
|
|
|
a) Australian incorporated association |
(i) Incorporated association name; and |
Australian Securities and Investment Commission (ASIC) |
|
b) Australian political party |
(i) Party Name Australian |
Electoral Commission |
|
c) Australian trade union or organisation under Workplace Relations Act 1996 |
(i) Union or organisation name; and |
Australian Industrial Relations Commission |
|
d) Australian sporting or special interest club If no ABN provided, registrant must warrant that they are a club |
(i) Club name; and |
Registrant warranty, or if ABN provided |
|
com.au and net.au |
|
|
|
a) Australian registered company |
(i) Company name; and |
ASIC |
|
b) Trading under an Australian registered business name |
(i) Registered business name; |
ASIC |
|
c) Australian partnership or sole trader
|
(i) Trading name; and |
ABR |
|
d) Foreign company licensed to trade in Australia |
(i) Company name; and |
ASIC |
|
e) Australian Registered Trade Mark owner |
(i) Name of owner; and |
Australian Trade Mark Online Search System (ATMOSS) |
|
f) Australian Registered Trade Mark applicant
|
(i) Name of applicant; and |
ATMOSS |
|
g) Australian incorporated association |
(i) Incorporated association name; and |
ASIC |
|
h) Australian commercial statutory body trading under statutory body name |
(i) Statutory body name; and |
Relevant Act of Parliament |
|
id.au |
|
|
|
a) Australian citizen or resident Registrant must warrant that they are an Australian citizen or resident |
(i) Registrant name; and |
Registrant warranty |
|
org.au |
|
|
|
a) Charity operating in Australia
|
(i) Charitable institution or fund name; and |
ABR |
|
b) Non-profit organisation operating in Australia - might also be
Registrant must warrant that they are a non-profit organisation |
(i) Organisation name; and
|
Registrant warranty, and ABR Registrant warranty, and ASIC Registrant warranty, and ASIC Registrant warranty, and ASIC |
SCHEDULE C
ALLOCATION CRITERIA EXAMPLES
Table A - Examples of exact match, abbreviation and acronym in all open 2LDs
|
Registrant Type |
Example Name |
Exact Match |
Abbreviation |
Acronym |
|
asn.au |
|
|
|
|
|
a) Australian incorporated association |
Internet Industry Association |
internetindustryassociation.asn.auinternetindustry.asn.au |
iiassoc.asn.au |
iia.asn.au |
|
b) Australian political party |
Australian Democrats |
australiandemocrats.asn.au |
austdemocrats.asn.au |
ad.asn.au |
|
c) Australian trade union or organisation under Workplace Relations Act 1996 |
National Union of Workers |
nationalunionworkers.asn.au |
natunion.asn.au |
nuw.asn.au |
|
d) Australian sporting or special interest club |
Bendigo Cricket Club |
bendigocricketclub.asn.au |
bendigocc.asn.au |
bcc.asn.au |
|
com.au and net.au |
|
|
|
|
|
a) Australian registered company |
Coles Myer Pty Ltd |
colesmyer.com.au |
cmyer.com.au |
cm.net.au |
|
b) Trading under an Australian registered business name |
Jane's Cake Shop |
janescakeshop.com.au |
janescakes.com.au |
jcs.com.au |
|
c) Australian partnership or sole trader |
Turner and Turner James Turner |
turnerandturner.com.au
|
turners.com.au jamest.com.au |
tt.com.au jt.net.au |
|
d) Foreign company licensed to trade in Australia |
Singapore Airlines |
singaporeairlines.com.au |
singaporeair.com.au |
sa.com.au |
|
e) Australian Registered Trade Mark owner |
Coca Cola |
cocacola.com.au |
coke.com.au |
cc.net.au |
|
f) Australian Registered Trade Mark applicant |
Old-Fashioned Lemonade |
oldfashionedlemonade.com.au |
oldlemonade.com.au |
ofl.com.au |
|
g) Australian incorporated association |
Professional Golfers Assocation |
professionalgolfersassociation.com.au |
profgolfersassoc.com.augolfersassoc.net.au |
pga.com.au |
|
h) Australian commercial statutory body trading under statutory body name |
Australia Post |
australiapost.com.au |
auspost.com.au |
ap.com.au |
|
id.au |
|
|
|
|
|
a) Australian citizen or resident |
Jonathon Paul Smith |
jonathon.id.au |
john.id.au |
jps.id.au |
|
org.au |
|
|
|
|
|
a) Charity operating in Australia |
The Salvation Army |
salvationarmy.org.au |
salvos.org.au |
sa.org.au |
|
b) Non-profit organisation operating in Australia |
.au Domain Administration Ltd |
audomainadministration.org.au |
auda.org.au |
ada.org.au |
Table B - Examples of close and substantial connection in asn.au and org.au
|
Close and substantial connection category |
Example 1 |
Example 2 |
Example 3 |
Example 4 |
|
|
Registrant is a Church |
Registrant is a Trade union |
Registrant is the Salvation Army |
Registrant is an RSL Army Club |
|
(i) Service that registrant provides |
prayer.org.au |
workplacerelations.org.au |
welfare.org.au |
counselling.org.au |
|
(ii) Program that registrant administers |
soupkitchen.org.au |
livingwage2002.org.au |
employmentplus.org.au |
poppies.org.au |
|
(iii) Event that registrant organises or sponsors |
churchfete.org.au |
mayday.org.au |
redshieldappeal.org.au |
rememberanceday.org.au |
|
(iv) Activity that registrant facilitates, teaches or trains |
maritalguidance.org.au |
ohs.org.au |
familytracing.org.au |
lawnbowls.org.au |
|
(v) Venue that registrant operates |
church.org.au |
tradeshall.org.au |
hostel.org.au |
rslclub.org.au |
|
(vi) Profession that registrant's members practise |
ministers.org.au |
workers.org.au |
socialworkers.org.au |
veterans.org.au |
Table C - Examples of close and substantial connection in com.au and net.au
|
Close and substantial connection category |
Example 1 |
Example 2 |
Example 3 |
Example 4 |
|
|
Registrant is in the automotive industry |
Registrant is in the hospitatlity industry |
Registrant is in the IT industry
|
Registrant operates a women's clothing store
|
|
(i) Product that registrant manufactures or sells |
cars.com.au |
food.com.au |
computers.com.au |
clothing.com.au |
|
(ii) Service that registrant provides |
car-repairs.com.au |
catering.com.au |
webhosting.com.au |
tailoring.com.au |
|
(iii) Event that registrant organises or sponsors |
car-rally.com.au |
weddings.com.au |
itworld.com.au |
fashionshow.net.au |
|
(iv) Activity that registrant facilitates, teaches or trains |
learntodrive.com.au |
hospitality.com.au |
htmlskills.com.au |
wardrobeconsulting.com.au |
|
(v) Venue that registrant operates or sponsors |
calderpark.com.au |
hotel.com.au |
internetcafe.com.au |
store.com.au |
|
(vi) Profession that registrant's employees practise |
mechanics.com.au |
waiters.com.au |
engineers.com.au |
tailors.net.au |
Table D - Examples of close and substantial connection in id.au
|
Close and substantial connection category |
Example 1 |
Example 2 |
Example 3 |
Example 4 |
|
|
Registrant's name is John Smith |
Registrant's name is Catherine Evans |
Registrant's name is Van Nguyen |
Registrant's name is Ann Poulos |
|
(i) Derived from one or more words of registrant's personal |
johnny.id.au |
kate.id.au (because Kate is a common derivate of Catherine) |
vanny.id.au |
annie.id.au |
|
(ii) Includes one or more words of registrant's personal |
johnonline.id.au |
catherine99.id.au |
nguyen888.id.au |
crazyann.id.au |