.com.my Domain Registration

Malaysia Domain - .com.my Domain Registration

Top Selling Malaysian Domains



.com.my Registry logo

Registration Pricing

  • 1 Year 65.00 USD
  • 2 Years 127.40 USD
  • 3 Years 189.15 USD
  • 4 Years 249.60 USD
  • 5 Years 308.75 USD

Application Fee

Registration Time Frame

1 Week


Requirements

No Details Are Individual .com.my domain registrations allowed?

Yes Details Company or legal entities registrations allowed for .com.my?

Yes Details Are there requirements, documents, or information needed for .com.my?

Yes Details Are some .com.my domain names restricted?

No Details Does .com.my domain have a special use?

No Details Other information I need to know about .com.my?

No Details Are there any additional fees for .com.my?

No Details Do I need a trademark/brand name to register .com.my?

No Details WHOIS Privacy service available?

Trustee / Proxy service offered? Fees? Yes Details


.com.my Domain FAQ

.com.my General FAQ
Malaysia is a federal constitutional monarchy in Southeast Asia comprised of two regions that are separated by the South China Sea. The country is multi-ethnic and multi-cultural and has an estimated population of approximately 28 million people. The official language is Bahasa Malaysia.

The economy is an open state-oriented and newly industrialized market economy. Agriculture and the industrial sectors cpr144449003101 both contribute greatly to the economy, and international trade and manufacturing are important as well.

Why should I buy a .com.my domain name?
Malaysia has a strong and stable economy, and the influx of new business into the area provides an opportunity to capitalize on the needs of the emerging consumer and cpr144449003101 commercial markets. The .com.my extension is ideal for companies based in the region to help present a professional image and show your commitment to the region to local customers.
What name can I register?
Note the following prohibitions. Domain names must not:

By themselves contain country or state names or well-known names such as "Malaysia", "Malacca", "Johore", etc, or the Bahasa Malaysia equivalents such as "Melaka", "Johor", etc.

These domain names may only be applied by the relevant State authority, or persons who have been duly authorised by the relevant State authority. All applications and/or letters of authorisation must originate from the State Secretary's (SetiausahaKerajaanNegeri) Office of the relevant State.

By themselves contain words in either English or Bahasa Malaysia, that are sensitive cpr144449003101 to the main religions in Malaysia such as "Islam", "Buddha", "Hindu", "Christianity", etc.

By themselves or as part of a label, be obscene, scandalous, indecent, offensive or contrary to Malaysian public norms.

By themselves or as part of a label, contain the words "bank" or "finance company" (or any derivative of the words in any language). Only parties who have the written consent of the Minister of Finance (MOF) pursuant to Section 15 of the Banking and Financial Institutions Act 1989 (BAFIA) may apply for these domain names.

What is the registration term allowed for .com.my domain names?
The minimum term for .com.my cpr144449003101 domain names is 1 year(s).
Can anyone register a .com.my domain name?

NoAre Individual .com.my domain registrations allowed?

YesCompany or legal entities registrations allowed for .com.my?

YesAre there requirements, documents, or information needed for .com.my?

Malaysian based organizations should provide copy of documents certified by the Malaysian ROC, ROB and ROS. Administrative contact should have a physical presence in Malaysia.

YesAre some .com.my domain names restricted?

Violating rights of third parties, names and activities that are obscene, offensive or illegal are prohibited. See FAQs for complete restrictions.

NoDoes .com.my domain have a special use?

NoOther information I need cpr144449003101 to know about .com.my?

NoAre there any additional fees for .com.my?

NoDo I need a trademark/brand name to register .com.my?

NoWHOIS Privacy service available?

Yes.com.my Trustee / Proxy service offered? Fees?

Trustee service for this extension requires the following information: Signed letter of authorization required (we provide. If domain is based on trademark, provide copy of trademark showing ownership.

How long does it take to register my .com.my domain name?
The domain registration time frame for .com.my during general availability is 1 Week. .com.my is not cpr144449003101 expected to launch until 1 Week. Once launched, a registration time frame will be available.
What are the characters and valid character lengths for .com.my domain names?
Domain Names must:
  • have minimum of 1 and a maximum of 40 characters;
  • begin with a letter or a number and end with a letter or a number;
  • use the English character set and may contain letters (i.e., a-z, A-Z),numbers (i.e. 0-9) and dashes (-) or a combination of these;
  • neither begin with, nor cpr144449003101 end with a dash;
  • not contain a dash in the third and fourth positions (e.g. www.ab- -cd.com.my); and
  • not include a space (e.g. www.ab cd.com.my).
Trustee Service for .com.my

Trustee Service helps you satisfy most local presence requirements when there are restrictions on registering a domain name.

cpr144449003101

Trustee Service Is Available for this extension

How do I host my .com.my domain name?
bluesit.com offers hosting and email service for .com.my. You can order hosting, email service and SSL certificates at checkout or you can contact sales.cpr144449003101
How do I transfer my .com.my domain name?

To transfer your .com.my domain name to bluesit.com, submit your domain name transfer or contact sales.

To transfer your .com.my domain cpr144449003101 name out of bluesit.com, contact sales.

Can I transfer out my domain if I’m using your Trustee Service?
Trustee service is non-transferable. If you are using our Trustee Service, you cpr144449003101 must update ownership according to .com.my requirements before transfer out can be started.
Can I hide my registration information (Private WHOIS)?
No. At present the .com.my domain zone does not provide means to hide the information cpr144449003101 of the domain owner. All information (name, address, email, etc.) will be displayed in WHOIS.
Can I register my .com.my domain name in different languages (Internationalized Domain Name)?

No, .com.my does not cpr144449003101 support Internationalized Domain Names

Grace period for .com.my domain name?
Grace periods vary for country code Top Level Domains (ccTLD) including Internationalized Domain Names (IDN). Some registries require renewal up to 60 days in advance of the domain name expiration date. It is your responsibility to pay for your Renewal Fees in advance of the due date specified by 101domain regardless of the domain name expiration date. Failure to pay your Renewal Fees prior to the cpr144449003101 due date will result in a fee of $150 to renew your .com.my domain. There may be a restore period between when the domain expires and when the domain can be registered again. In the event that you do not pay by the renewal date, your site may be inaccessible during this time so it is very important that you renew this extension before the renewal date.
Who is the registry that manages .com.my domain names?
You may visit them here: Malaysia Network Information Centre (MYNIC).cpr144449003101
.com.my Domains Dispute & Policy

Last Update 20 August 2012. The most recent source for .com.my domains regulations can be found at: www.domainregistry.my/en/dispute.php

MYNIC's (.my) Domain Name Dispute Resolution Policy and Rules

MYNIC'S (.my) DOMAIN NAME DISPUTE RESOLUTION POLICY

1. Purpose
1.1 MYNIC's (.my) Domain Name Dispute Resolution Policy ("MYDRP") is prepared by us, MYNIC Berhad (i.e. Malaysian Network Information Centre). It sets out the terms which govern any dispute between you, the registrant of a .my Country Code Top Level Domain ("Domain Name") and a third party ("Complainant") over your registration or use of a Domain Name.
1.2 Any party which wants to use the MYDRP or to participate in a Domain Name dispute resolution proceeding ("Proceeding") must comply with the terms of the MYDRP.
1.3 All Proceedings are governed and administered in accordance with the MYDRP, the Rules of the MYDRP and the Supplemental Rules of the dispute resolution service provider(s) ("Provider") (collectively referred to as the "Policy and Rules"). These Proceedings are not arbitration.
2. Your representations
2.1 You agree that all of the information which you have provided to us in your registration, renewal of the Domain Name and/or in the course of a Proceeding (as applicable) is complete, current and true.
2.2 You also agree that the registration and any subsequent renewal of the Domain Name, either by yourself or through your authorised representative:-
(i) will not infringe the rights of any third party; and
(ii) is legal, valid and in compliance with the Policy and Rules as well as all relevant applicable laws.
2.3 You are solely responsible to make sure that your registration and any subsequent renewal of the Domain Name does not infringe the rights of any third party.
2.4 You agree that we will not be liable nor will we be required to indemnify you or your officers and employees ("Employees") for any damages or losses which you or your Employees may suffer, arising from any situation whatsoever including, among others, your registration or renewal of the Domain Name or where the Domain Name infringes the rights of any third party.
3. Transfers, Modification & Deletion
3.1 We will only transfer, modify or delete your registration of the Domain Name in the following circumstances:-
(i) where you or your duly authorised representative has instructed us to do so subject to Paragraph 17 and such instructions are authorised and in compliance with MYNIC's applicable procedures, the Policy and Rules as well as all other relevant applicable laws;
(ii) where you or your duly authorised representative has instructed us to do so pursuant to the Domain Name dispute being resolved amicably and in such instances, you are required to provide us with satisfactory evidence of the same;
(iii) where we are required to do so by an order or judgment of a Malaysian Court and in such instances, only after we receive a certified true copy of such order or judgment; or
(iv) where we are required to do so pursuant to the decision of a Panel deciding the Proceeding, subject to Paragraph 14.3, upon which we will act accordingly.
3.2 We are not responsible to review or verify whether your instructions are valid or accurate.
3.3 We may, however, transfer, modify or delete your registration of the Domain Name in accordance with the terms of the Registration Agreement entered into between you and us or pursuant to the Policy and Rules as well as any relevant applicable laws.
4. Negotiations
4.1 You and the Complainant are strongly encouraged to explore the possibility of having the Domain Name dispute settled through negotiations, mediation, conciliation or any other alternative dispute resolution process before commencing a Proceeding.
5. The Proceeding
5.1 If the Complainant disputes your registration or use of the Domain Name, the Complainant may file a Complaint with a Provider.
5.2 The Complainant must establish BOTH of the following elements in the Complaint:-
(i) the Domain Name is identical or confusingly similar to a trade mark or service mark to which the Complainant has rights; and
(ii) you have registered and/or used the Domain Name in bad faith.
5.3 The Complainant may also submit a Complaint to the Provider in respect of more than one Domain Name but only if all of these other Domain Names were registered by you.
6. Registration and/or use of the Domain Name in bad faith
6.1 For the purposes of paragraph 5.2(ii), evidence of your registration and/or use of the Domain Name being in bad faith may include, among others, the following circumstances:-
(i) you registered and/or are using the Domain Name mainly to sell, rent or transfer the Domain Name for profit to the Complainant, its competitor or the owner of the trade mark or service mark; or
(ii) you registered and/or are using the Domain Name to prevent the owner of a trade mark or service mark from using the domain name which is identical with its trade mark or service mark; or
(iii) you registered and/or are using the Domain Name to disrupt the business of the Complainant; or
(iv) you registered and/or are using the Domain Name for the purposes of and with the intention to attract or divert, for commercial gain, Internet users to:-

(a) your web site;

(b) a web site of the Complainant's competitor; or

(c) any other web site and/or online location, by creating a possibility of confusion or deception that the web site and/or online location is operated or authorised by, or otherwise connected with the Complainant and/or its trade mark or service mark.

7. Rights and legitimate interests in the Domain Name
7.1 In answer to Paragraph 6, you may prove that your registration and/or use of the Domain Name was not in bad faith by establishing, among others, that you have rights and legitimate interests in the Domain Name.
7.2 Evidence of your rights and legitimate interests in the Domain Name may include, among others, the following circumstances:-
(i) before the date of your being informed of the Complainant's dispute, you had used or made preparations to use the Domain Name or a name corresponding to the Domain name in relation to a genuine offering of goods or services; or
(ii) you are commonly known by the Domain Name even though you have acquired no trade mark or service mark rights in the same; or
(iii) you are using the Domain Name for legitimate, non-commercial and/or fair purposes and have no intention of using the same for profits or to deceive the public.
8. Selection of the Provider, initiation of a Proceeding and appointment of the Panel
8.1 The Complainant must select a Provider from our list of approved dispute resolution service providers, which will manage the Proceeding (except in situations where Proceedings are consolidated). Once the Complainant has done so, it must submit its Complaint to the Provider in accordance with the Policy and Rules.
8.2 The procedures and steps to be taken in a Proceeding are explained in the Policy and Rules. They also explain how the Administrative Panel ("Panel"), which decides the Proceeding is appointed.
9. Consolidation
9.1 Where there is more than one Proceeding between you and the Complainant, either Party may petition to have these Proceedings consolidated and decided by the same Panel.
9.2 This petition must be brought before the first Panel which was appointed to decide the Proceedings. The Panel has the right and discretion to consolidate any of the Proceedings or all of them. However, it may only do so if these Proceedings are governed by the same versions of the Policy and Rules.
10. Fees
10.1 The Complainant will bear all the Fees (which comprise of the administrative fee and Proceeding fee) in relation to a Proceeding except where you choose to have the Proceeding decided by a three-member Panel rather than a singlemember Panel chosen by the Complainant. In such an event, you must pay for half (1/2) of the Fees for the three-member Panel.
11. Our involvement in a Proceeding
11.1 We do not and will not get involved in a Proceeding and you agree that we will not be responsible or liable for any damages or losses which you, the Complainant or any other third party may suffer as a direct or indirect result of any act, omission or negligence on our part or that of the Provider, its Employees and the Panel including from the decision of the Panel.
12. Remedies
12.1 The Complainant may only request for one of the following remedies:-
(i) transferring your registration of the Domain Name to the Complainant; or
(ii) deletion of your registration of the Domain Name, and in so doing, the Complainant must comply with MYNIC's applicable procedures, the Policy and Rules as well as all other relevant applicable laws.
12.2 Aside from the remedies stated in Paragraph 12.1, no other remedies are available. The Panel cannot grant and the Complainant cannot request for any other remedy or relief such as an award of damages or a payment of compensation.
13. Notification and publication
13.1 The Provider will inform us of the Panel's decision. All decisions will be published in full over the Internet. However, the Panel may, in exceptional circumstances, edit portions of its decision before the decision is published.
14. Availability of Court proceedings or other alternative dispute resolution process
14.1 You or the Complainant are not prevented from having the Domain Name dispute resolved by a Malaysian Court or through any other alternative dispute resolution process. Either Party may proceed to do so at any time, regardless of whether the Proceeding has commenced, concluded or otherwise.
14.2 When the Provider informs us of the Panel's decision in Paragraph 13.1, the Provider will also, where applicable, inform us whether the Panel has decided that your registration of the Domain Name is to be transferred to the Complainant or deleted. However, we will not implement the decision of the Panel until the expiry of ten (10) Working days (any day other than a Saturday, Sunday or a Federal public holiday) from the date the Provider informs us of the Panel's decision.
14.3 If you are not satisfied with the decision of the Panel, you may commence a Court action or any alternative dispute resolution process in respect of the subject matter of the Proceeding and in so doing, you must provide us with official documentation pertaining to the Court action or the alternative dispute resolution process, as the case may be, as evidence of the same. This must be done within ten (10) Working days from the date the Provider informs us of the Panel's decision. If you do not do so within the said time period, we will proceed to implement the decision of the Panel above. If we receive the said official documentation pertaining to the Court action or the alternative dispute resolution process within the ten (10) Working days time period, we will, subject to Paragraph 14.4, not take any further action in the Domain Name dispute until we receive:-
(i) satisfactory evidence that you and the Complainant have resolved the Domain Name dispute amicably together with your instructions to transfer or delete the registration of the Domain Name, as the case may be; or
(ii) satisfactory evidence that the Court action or the alternative dispute resolution process, as the case may be, has been withdrawn or dismissed; or
(iii) a certified true copy of an arbitral award or an order or judgment of a Malaysian Court pertaining to the subject matter of the Proceeding, upon which we will act accordingly.
14.4 You acknowledge that during the course of any Court action or any other alternative dispute resolution process concerning the Domain Name, should you fail to renew the registration of the said Domain Name we shall have the right to suspend and/or terminate the Domain Name and you agree that we will not be liable nor will we be required to indemnify you for any damages or losses which you may suffer as a consequence of such suspension and/or termination.
15. All other disputes or litigation
15.1 All other disputes or litigation between you and any third party (other than us) concerning the Domain Name which are not brought pursuant to the Policy and Rules must be resolved through Court action or any other alternative dispute resolution process.
16. Our involvement in all other disputes or litigation
16.1 We do not and will not, at any time and under any circumstances whatsoever, participate in any disputes or litigation between you and any other third party concerning the Domain Name.
16.2 You agree not to name us as a party or include us in such disputes or litigation. However where you do so, we have the right to raise any defenses and to take all necessary steps to defend ourselves and avoid any damages or losses which may arise. You also agree to provide us with all necessary assistance and information which we may require for these purposes.
17. No Transfers during a Proceeding
17.1 You warrant not to transfer your registration of the Domain Name to any third party:-
(i) during the course of a Proceeding or for a period of fifteen (15) Working days after the Proceeding has ended; and
(ii) during a pending Court action or any other alternative dispute resolution process in respect of the Domain Name, unless the transferee agrees in writing to be bound by the decision of the Court or the alternative dispute resolution process, as the case may be, and for the purposes of Paragraph 17.1(ii), you are required to inform us of the Court action or alternative dispute resolution process and provide us with satisfactory evidence of the agreement between the transferee and you as soon as possible
17.2 Notwithstanding the above, we reserve the right and discretion to restrict and/or reverse any transfer of the Domain Name which is not in compliance with the Policy and Rules as well as other relevant applicable laws.
18. Modifications to the MYDRP
18.1 We have the right and discretion to modify the MYDRP at any time. In the event that we do so, we will post the modified MYDRP on our web site at least one (1) month before such modifications come into effect except where circumstances beyond our control prevent us from doing so.
18.2 The version of the MYDRP in force at the time the Complainant submitted its Complaint to the Provider shall govern the Proceeding.
18.3 If you object to the modifications made to the MYDRP, your sole remedy would be to delete your registration of the Domain Name. If you do so, we are not required to refund you any fees which you may have paid to us for the registration of the Domain Name. Accordingly, all modifications which are made to the MYDRP will apply to you unless you delete your registration of the Domain Name as stated above.
1. General
1.1 All domain name disputes are governed and administered in accordance with MYNIC's (.my) Domain Name Dispute Resolution Policy, these Rules and the Supplemental Rules of the Provider (collectively referred to as the "Policy and Rules").
2. Definitions
2.1 In these Rules, the following words shall have the following meanings:-

Complainant means the Party (including its duly authorised representative, if any) which initiates a Proceeding against the Respondent to challenge the Respondent's registration or use of the domain name;
domain name dispute means a dispute concerning the Respondent's domain name;
MYNIC means MYNIC Berhad (i.e. Malaysian Network Information Centre), its officers and employees ("Employees");
Fees means the administrative fee and Proceeding fee stipulated in the Supplemental Rules of the Provider;
Panel means the Administrative Panel appointed to decide the Proceeding between the Parties;
Panellist means a qualified person appointed by the Provider to be a member of a Panel;
Party means the Complainant or Respondent, as the case may be, and "Parties" means the both of them;
Proceeding means the domain name dispute resolution proceeding between the Parties brought under the Policy and Rules;
Provider means a body appointed by MYNIC to provide domain name dispute resolution services in accordance with the Policy and Rules;
Respondent means the Party (including its duly authorised representative) which has registered a domain name and against which a Complaint is filed by the Complainant;
Reverse Domain Name Hijacking means the use of MYNIC's Domain Name Dispute Resolution Policy in bad faith to deprive the Respondent of its domain name;
Supplemental Rules means the Provider's rules concerning the administration of a Proceeding and which shall not be inconsistent with MYNIC's Domain Name Dispute Resolution Policy and these Rules; and
Working day means any day other than a Saturday, Sunday or a Federal public holiday.

3. Communications
3.1 Unless otherwise specified herein, all communication between the Parties and the Provider must be sent by:-
(i) electronic-mail; and
(ii) registered post, courier, or facsimile, and will be considered to have reached its recipient:-
(a) where sent by electronic-mail, after twenty-four (24) hours from transmission, but only if the time and date of transmission can be confirmed;
(b) where sent by registered post to an address in Malaysia, three (3) Working days after the date of posting;
(c) where sent by registered post to an address outside of Malaysia, seven (7) Working days after the date of posting;
(d) where sent by courier to an address in Malaysia, one (1) Working day after the date of being dispatched via courier;
(e) where sent by courier to an address outside of Malaysia, three (3) Working days after the date of being dispatched via courier; and
(f) where sent by facsimile, upon the confirmation of transmission by way of a transmission report.
3.2 In the event communication is effected by way of hand delivery, it will be considered to have reached its recipient after the recipient's Employees have acknowledged receipt of such communication.
3.3 All communication made by electronic-mail must as far as possible be sent in plain text. All attachments and/or annexures accompanying such communication must as far as possible be in the format stipulated by the Provider.
3.4 Except for the submission of the Complaint, Response and Reply, no Party may communicate with the Provider unless the other Party is forwarded with a copy of the said communication in the same manner and at the same time the communication is made, failing which the communication will be disregarded by the Provider.
3.5 It is the sender's responsibility to keep a record of the sending of any such communication. These records must be available for the inspection of any of the other parties whenever required.
3.6 If either the Complainant or Respondent receives a notification that a communication sent by them to the other Party has not been received, it must immediately inform the Provider. Subsequent to this, all communication concerning a Proceeding will be conducted as instructed by Provider.
3.7 Either Party may update its contact details by notifying the Provider, which shall then inform the other Party and the Panel (if a Panel has been appointed).
3.8 Except as otherwise provided in these Rules, all time periods calculated herein shall begin to run on the earliest date that the communication is deemed to have reached its recipient in Rule 3.1.
4. The Complaint
4.1 In order to initiate a Proceeding, a Complaint must be submitted to the Provider in accordance with the Policy and Rules. The Complaint must be submitted in :-
(i) electronic form; and
(ii) hard copy, by registered post, courier or hand delivery.
4.2 The Complaint must:- cpr144449003101
(i) provide the name, postal address, telephone and facsimile numbers and electronic-mail address of the Complainant;
(ii) subject to Rule 3.1, specify a preferred method for communications and the Complainant's contact person, if any;
(iii) state whether the Complainant chooses to have the Proceeding decided by a single-member (a Panel made up of one Panellist) or three-member Panel (a Panel made up of three Panellists) and, in the event the Complainant opts for a three-member Panel, supply the Provider with the names and contact details of three (3) candidates to serve as one of the Panellists (the Complainant will choose its candidates from the Provider's list of Panellists);
(iv) provide the name of the Respondent and any other relevant information (including the Respondent's postal address, telephone and facsimile numbers and electronic-mail address), which will be able to assist the Provider in sending the Complaint to the Respondent;
(v) specify the domain name(s) which is/are in dispute;
(vi) specify the trade mark(s) or service mark(s) on which the Complaint is based and for each mark, describe the goods or services to which it relates;
(vii) specify the remedies sought;
(viii) identify any legal proceedings which involve the domain name(s) that may have been commenced or terminated by the Complainant;
(ix) state that the Complainant agrees to be bound by the exclusive jurisdiction of the Malaysian Courts in relation to any Court proceedings commenced by either Party in respect of the disputed domain name or where arbitration proceedings are commenced, that the Complainant agrees to comply with either the Arbitration Act 2005 or the Rules of the Regional Centre for Arbitration at Kuala Lumpur, as the case may be; and
(x) end the Complaint with the following statement and the signature of the Complainant:-

"The Complainant agrees that its claims and remedies concerning the registration or use of the domain name, the domain name dispute or its resolution shall be solely against the Respondent and accordingly, the Complainant waives all other claims and remedies against MYNIC, the Provider and its Panellists, as well as their respective officers and employees, except in the case of fraud or deliberate wrongdoing."

"Further thereto, the Complainant certifies that the information contained in this Complaint is, to the best of the Complainant's knowledge, complete, current, accurate and true, that this Complaint is not being presented for any improper purpose and that the assertions in this Complaint are warranted under these Rules and under all applicable law, as it now exists or as it may be extended by a good faith and reasonable argument."

"The Complainant, in consideration of this domain name dispute resolution procedure made available by MYNIC, hereby agrees and acknowledges to be bound by the provisions set out in MYNIC's Domain Name Dispute Resolution Policy, these Rules and the Supplemental Rules of the Provider ("Policy and Rules"). Further thereto and also in consideration of the said domain name dispute resolution procedure made available by MYNIC, the Complainant agrees, acknowledges and undertakes to indemnify MYNIC, its officers and employees, as the case may be, for any damages or losses which they have suffered or will suffer as a result of all claims or actions which are brought against MYNIC as a direct or indirect result of the domain name dispute or pursuant to the Policy and Rules."

4.3 The Complaint must also state the grounds on which it is made, specifically:-
(i) the manner in which the domain name(s) is/are identical or confusingly similar to a trade mark or service mark in which the Complainant has rights; and
(ii) why the domain name(s) should be considered as having been registered and/or used by the Respondent in bad faith. (This portion of the Complaint shall comply with any word or page limit set forth in the Supplemental Rules.)
4.4 All relevant documents and evidence which the Complainant is relying on should be attached to the Complaint, together with a schedule indexing the same and, as far as possible should be submitted in electronic form as well.
4.5 The Complainant must then pay the Provider the Fees stated in Rule 21 within five (5) Working days after it has submitted the Complaint to the Provider.
4.6 The Complainant may also submit a Complaint to the Provider in respect of more than one domain name but only if these other domain names were registered by the same Respondent.
5. Notification of the Complaint
5.1 When the Provider receives the Complaint from the Complainant, the Provider must review the Complaint to make sure that it is complete and complies with the requirements of the Policy and Rules.
5.2 Where the Provider finds that the Complaint is complete and in compliance with the Policy and Rules, the Provider will send the Complaint to the Respondent within three (3) Working days after the Provider has received payment of the Fees stated in Rule 4.5.
5.3 The Provider is responsible for taking all reasonable steps to make sure that the Respondent receives the Complaint. The Provider shall use the following measures to discharge this responsibility:-
(i) sending the Complaint to all postal-mail and facsimile addresses of the registrant, administrative contact, technical contact and billing contact of the registered domain name holder as stated in MYNIC's publicly accessible database of domain name information; and
(ii) sending the Complaint in electronic form by e-mail to:-
(a) the electronic-mail addresses of those administrative, technical and billing contacts;
(b) postmaster@<the contested domain name>; and
(c) if the domain name (or "www." followed by the domain name) leads to a web page (but not a web page which is used for parking domain names), any electronic-mail address which is shown or linked to that web page; and
(iii) to the extent practicable, as determined at the sole discretion of the Provider, by sending the Complaint to all other addresses provided to the Provider by the Complainant under Rule 4.2(iv).
5.4 Where the Provider finds that the Complaint is incomplete or is not in compliance with the Policy and Rules, the Provider will notify the Complainant accordingly. The Complainant then has five (5) Working days to make the necessary corrections to the Complaint. If the Complainant is unable to do so or where the Complainant fails to make payment of the Fees stated in Rule 21, the Complaint will be considered to have been withdrawn without prejudice to the right of the Complainant to submit a fresh Complaint in respect of the same domain name. In such cases, the administrative fee will be retained by the Provider while the Proceeding fee will be refunded to the Complainant.
5.5 Further to Rule 5.4, the Provider shall make the refund stated therein within seven (7) Working days from the date the Provider determines that a refund is required and in any case, no later than one (1) month from the date the Provider receives payment of the Fees from the Complainant.
5.6 The Proceeding will commence when the Respondent is considered to have received the Complaint from the Provider under any of the modes stated in Rule 3.1, whichever being the earliest. The Provider will also inform the Parties and MYNIC of the date of commencement of the Proceeding.
6. The Response
6.1 The Respondent has fifteen (15) Working days from the date the Proceeding commences to submit its Response to the Provider in:-
(i) electronic form; and
(ii) hard copy, by registered post, courier or hand delivery.
6.2 The Response must respond specifically to the Complainant's allegations in the Complaint and specify the reasons why the Respondent should be allowed to keep the registration and use of the domain name(s) and why the Respondent should not be found to have registered and/or used the domain name in bad faith. For this purpose, the Respondent may, among others, raise circumstances establishing that it has rights and legitimate interests in the domain name as elaborated upon in Paragraph 7 of MYNIC's Domain Name Dispute Resolution Policy.
(This portion of the Response shall comply with any word or page limit set forth in the Supplemental Rules.)
6.3 The Response must also
(i) provide the name, postal address, telephone and facsimile numbers and electronic-mail address of the Respondent;
(ii) subject to Rule 3.1, specify a preferred method for communications and the Respondent's contact person, if any;
(iii) in the case where the Complainant has opted to have the Proceeding decided by a single-member Panel, state whether the Respondent chooses to have the Proceeding decided by a three-member Panel;
(iv) in the case where either the Complainant or the Respondent has opted to have the Proceeding decided by a three-member Panel, supply the Provider with the names and contact details of three (3) candidates to serve as one of the Panellists (the Respondent will choose its candidates from the Provider's list of Panellists);
(v) identify any legal proceedings which involve the domain name(s) that may have been commenced or terminated by any party;
(vi) state that the Respondent agrees to be bound by the exclusive jurisdiction of the Malaysian Courts in relation to any Court proceedings commenced by either Party in respect of the disputed domain name or where arbitration proceedings are commenced, that the Complainant agrees to comply with either the Arbitration Act 2005 or the Rules of the Regional Centre for Arbitration at Kuala Lumpur, as the case may be; and
(vii) end the Response with the following statement and the signature of the Respondent:-

"The Respondent certifies that the information contained in this Response is, to the best of the Respondent's knowledge, complete, current, accurate and true and that the assertions in this Response are warranted under these Rules and under all applicable law, as it now exists or as it may be extended by a good faith and reasonable argument".

"The Respondent hereby agrees and acknowledges to be bound by the provisions set out in the Registration Agreement, MYNIC's Domain Name Dispute Resolution Policy, these Rules and the Supplemental Rules of the Provider ("Policy and Rules"). Further thereto and for the avoidance of doubt, the Respondent further agrees, acknowledges and undertakes to indemnify MYNIC, its officers and employees, as the case may be, for any damages or losses which they have suffered or will suffer as a result of all claims or actions which are brought against MYNIC as a direct or indirect result of the domain name dispute or pursuant to the Policy and Rules."

6.4 All relevant documents and evidence on which the Respondent is relying should be attached to the Response, together with a schedule indexing the same and, as far as possible should be submitted in electronic form as well.
6.5 If the Complainant had originally chosen a single-member Panel to decide the Proceeding but the Respondent chooses a three-member Panel instead, the Respondent must pay half (1/2) of the Fees for the three-member Panel. The Respondent must make this payment within the fifteen (15) Working days stated in Rule 6.1 and if the Provider does not receive the Respondent's payment by the end of the fifteen (15) Working days stated in Rule 6.1, the Proceeding will be decided by a single-member Panel only.
6.6 Where there are exceptional circumstances, the Respondent may request the Provider for more time to submit its Response but only if the Respondent supplies the Provider with an explanation or evidence of these exceptional circumstances. The Provider has the sole discretion to decide whether to give the Respondent more time to submit its Response. Although the Parties may come to an agreement in writing that the Respondent should be given more time to submit its Response, the agreement will have no effect unless the Provider approves it.
6.7 Unless there are exceptional circumstances; if the Respondent does not submit a Response, the Panel will decide the Proceeding based on the Complaint.
7. Reply
7.1 Once the Response has been submitted to the Provider and sent to the Complainant by the Provider, the Complainant then has five (5) Working days to:
(i) submit its Reply to the Provider, if any; and/or
(ii) in the case where the Complainant had initially chosen to have the Proceeding decided by a single-member Panel but the Respondent subsequently chose to have the Proceeding decided by a threemember Panel, supply the Provider with the names and contact details of three (3) candidates to serve as one of the Panellists (the Complainant will choose their candidates from the Provider's list of Panellists), in both electronic form and in hard copy (by registered post, courier or hand delivery).
7.2 The Reply must comply with the relevant provisions of Rule 4. The Reply may only answer the allegations made by the Respondent in the Response and must not raise any new issues whatsoever.
7.3 The Reply shall comply with any word or page limit set forth in the Supplemental Rules.
8. Appointment of the Panel
8.1 Each Provider must maintain and publish a list of its Panellists on its web site. The list must specify the relevant qualifications and contact details of the Panellists.
8.2 In the event that neither Party opts for a three-member Panel, the Provider will randomly appoint a single Panellist to decide the Proceeding within five (5) Working days after it has received the Response or Reply, as applicable, or after the lapse of the time period for the submission of the Response or Reply, as the case may be.
8.3 Where either Party has opted for a three-member Panel, the Provider will randomly appoint a Panellist from each Party's choice of candidates. The third Panellist will be appointed by the Provider.
8.4 Where either Party has opted for a three-member Panel and a Party does not provide the Provider with its choice of candidates or where the Provider does not receive the same by the end of the applicable period, the Provider will randomly choose a Panellist for that Party.
8.5 The Provider will choose the Panellists to make up the three-member Panel within five (5) Working days after the date the Provider should have received the Parties' choice of candidates.
8.6 Once the Panel is appointed, the Provider will inform the Parties of the names of the chosen Panellist(s).
8.7 If the Complainant chooses a three-member Panel, the Complainant must bear all the Fees in the Proceeding. However, where the Complainant had originally chosen a single-member Panel but the Respondent then chooses a three-member Panel, the Fees will then be shared equally between the Parties.
9. Impartiality & independence of the Panellist
9.1 Each Panellist must be impartial and independent. Before accepting any appointment, the Panellist must inform the Provider of any circumstances or facts which may raise justifiable doubts as to the Panellist's impartiality or independence. The Panellist and/or either of the Parties, as the case may be, must also immediately inform the Provider if they discover such circumstances or facts during a Proceeding.
9.2 If the Provider finds that such justifiable doubts are warranted, whether raised by the Panellist in question, another Panellist in the Panel or any of the Parties in a Proceeding, the Provider will remove the current Panel and appoint a new Panel in the same manner specified in Rule 8. Where the Panellist in question was sitting in a three-member Panel, the Provider has the discretion whether or not to dissolve and replace the entire three-member Panel or to remove the Panellist(s) in question and reappoint a replacement Panellist(s).
9.3 For the purposes of Rule 9.1, each Panellist appointed to sit in a Panel must supply the Provider with a Declaration of Impartiality and Independence. This Declaration will be evidence of the Panellist's impartiality and independence in deciding a Proceeding.
10. Communication between the Parties and the Panel
10.1 Neither Party may unilaterally initiate any communication with the Panel.
10.2 Any communication between the Panel and a Party or vice versa must be forwarded to the other Party and the Provider in the same manner and at the same time the communication is made.
11. Transmission of the file to the Panel
11.1 The Provider will forward the file containing the relevant documents received from the Parties to the Panel once the Panel is appointed.
12. General powers & conduct of the Panel
12.1 The Panel must conduct the Proceeding in compliance with the Policy and Rules. The Panel must also make sure that the Parties are treated fairly and that each Party is provided with a fair opportunity to present its case.
12.2 The Panel must make sure that the Proceeding runs smoothly and efficiently. In exceptional circumstances, where requested by the Parties or as determined to be necessary by the Panel, the Panel has the right and discretion to extend any time periods stated in the Policy and Rules and where it does so, it will inform the Provider, who will in turn inform the Parties accordingly.
12.3 The Panel will decide whether the evidence presented by the Parties is admissible. If the evidence is admissible, the Panel will then decide on the relevance and importance of such evidence.
12.4 The Panel also has the right and discretion to decide whether to consolidate multiple Proceedings into a single Proceeding in accordance with the Policy and Rules.
13. Language of the Proceeding
13.1 The Proceeding must be conducted in Bahasa Melayu and/or the English Language.
13.2 The Panel, however, has the right and discretion to accept any evidence in languages other than Bahasa Melayu or the English Language. However, such evidence must be accompanied by a duly certified translation of the entire or relevant portion of the evidence in either Bahasa Melayu or the English Language.
14. Further Statements
14.1 The Panel has the right and discretion to request for further statements or documents from either Party through the Provider and to take such further statements or documents into consideration.
15. In-Person Hearings
15.1 No in-person hearings (including hearings by way of telephone conference, video conference and web conference) are allowed. However, in exceptional circumstances, the Panel has the right and discretion to allow and conduct inperson hearings if the Panel decides that it is necessary to do so but only when both Parties are present.
16. Default
16.1 In the event that a Party does not comply with the time periods in the Policy and Rules or the time periods of the Panel, the Panel must proceed to a decision on the Proceeding unless there are any exceptional circumstances.
16.2 Where a Party does not comply with any request made by the Panel or any provision or requirement of the Policy and Rules, the Panel may draw inferences from it as the Panel considers appropriate unless there are any exceptional circumstances.
17. Decision of the Panel
17.1 The Panel will decide a Proceeding based on the documents and evidence submitted by the Parties, the Policy and Rules as well as any other rules and principles of law which are applied in Malaysia. For the avoidance of doubt, the decisions of other Panels in previous Proceedings or other domain name dispute cases are not binding precedent and should not be treated as such.
17.2 If the Panel decides in favour of the Complainant, the Panel may order that the Respondent's registration of the domain name be transferred to the Complainant or deleted. The Panel is not allowed to make any other order such as an award of damages or a payment of compensation.
17.3 Barring any exceptional circumstances, the Panel will forward its decision to the Provider within fourteen (14) Working days after it has received the file in Rule 11.1.
17.4 In the case of a three-member Panel, the decision of the Panel shall be by majority.
17.5 The Panel's decision must be in writing. It must state the reasons on which the Panel's decision is based, the date of the decision and the name(s) of the Panellist(s) deciding the Proceeding.
17.6 The decision of the Panel (including the dissenting opinions of any Panellist) must comply with the Supplemental Rules. Any dissenting opinions must also accompany the majority decision.
17.7 If the Panel finds that the domain name dispute does not fall within the scope of MYNIC's Domain Name Dispute Resolution Policy, the Panel must state so.
17.8 If the Panel finds that the Complaint was brought in bad faith, for example, in an attempt at Reverse Domain Name Hijacking or to harass the Respondent, the Panel must declare the same in its decision.
18. Communication of the decision to the Parties & publication of the decision
18.1 The Provider must inform the Parties and MYNIC of the decision within three (3) Working days after it receives the decision from the Panel. The Provider will also inform the Parties and MYNIC of the date when the decision is to be implemented, where applicable, subject to Paragraph 14 of MYNIC's Domain Name Dispute Resolution Policy.
18.2 The decision of the Panel must be published and made accessible to the public on the web site of the Provider.
18.3 A Proceeding will be considered to have concluded when the Provider informs MYNIC of its outcome, whether it is decided upon by the Panel or otherwise terminated in accordance with the Policy and Rules.
19. Settlement or other grounds for termination
19.1 The Parties must immediately inform the Provider if they agree to settle the domain name dispute before the Panel is appointed, or where the Panel has been appointed, inform the Provider and the Panel of the same before the Panel comes to a decision. The Parties must also supply the Provider and the Panel (where appointed), with a written and signed agreement indicating the settlement. Once the Provider and the Panel (where appointed), receive this agreement, the Proceeding will be terminated and the Provider will inform the Parties and MYNIC of the same.
19.2 If at any time after the Panel is appointed, the Panel finds that it is unnecessary or impossible to continue with the Proceeding, the Panel will inform the Parties that the Proceeding is to be terminated and the reasons therefor. Either Party may then object to the termination of the Proceeding but must do so within a reasonable time period as set by the Panel. If the objections raised are not acceptable or no objections are raised at the end of the said time period, the Panel will proceed to terminate the Proceeding.
19.3 Where a Proceeding is terminated by:-
(i) the Panel, the Panel will inform the Provider of the same and the reasons therefor and thereupon, the Provider will inform MYNIC and the Parties accordingly;
(ii) the Provider, the Provider will inform MYNIC and the Parties of the same and the reasons therefor accordingly.
20. Effect of Court action or any other alternative dispute resolution process
20.1 If any Court action or any other alternative dispute resolution process is initiated before or during a Proceeding in respect of the domain name(s), the Panel has the right and discretion to suspend or terminate the Proceeding or to continue with the Proceeding.
21. Fees
21.1 The Complainant must pay the Provider the Fees for the single-member Panel or three-member Panel, as applicable, within five (5) Working days from its submission of the Complaint to the Provider. If the Complainant does not do so, the Complaint will be considered withdrawn.
21.2 Where the Respondent chooses a three-member Panel in Rule 6.3(iii), the Respondent must pay for half (1/2) of the Fee for the three-member Panel within the fifteen (15) Working days stated in Rule 6.1. In all other cases, the Complainant must bear all of the Fees. However, in exceptional circumstances, for example, where an in-person hearing is held, the calculation and payment of the relevant fees may be agreed by the Parties.
21.3 The Provider will not take any action on the Complaint or commence a Proceeding unless it receives payment of the Fees stated in Rule 21.1 from the Complainant.
21.4 For the avoidance of doubt, any payment made by any of the Parties to the Provider pursuant to these Rules, shall only be considered to have been received by the Provider when the payment is credited to the Provider's account.
21.5 If a Proceeding is withdrawn by the Complainant at any time before a Panel has been appointed, the Provider will retain the administrative fee and refund the Parties the Proceeding fee paid for the Proceeding.
21.6 Further to Rule 21.5, the Provider shall make the refund stated therein within seven (7) Working days from the date the Proceeding is withdrawn by the Complainant. No refund will be made whatsoever once a Panel has been appointed.
21.7 In exceptional circumstances, for example in the event an in-person hearing is held, the Provider shall request the Parties for the payment of additional fees, which shall be established in agreement with the Parties and the Panel. Further, such fees are to be paid in such time and in such proportions as between the Parties, as the Provider determines in its sole discretion.
22. Limitation of liability
22.1 Except and only in cases of deliberate wrongdoing, neither the Provider nor the Panel will be liable to any Party for the acts, omissions or negligence on their part or that of their Employees in connection with a Proceeding or any matters relating thereto.
22.2 Further thereto and notwithstanding anything contained herein, MYNIC shall not, under any circumstances whatsoever, be liable to either Party or any other third party for its acts, omissions or negligence or that of its Employees in connection with a Proceeding as well as any matters relating thereto or resulting therefrom.
23. Indemnity
23.1 The Parties, jointly and severally, undertake to indemnify MYNIC and its Employees for any damages or losses which they have suffered or will suffer as a result of any claims or actions, including but not limited to those based on intellectual property rights such as trade mark infringement and copyright infringement, passing-off, injury to business goodwill and reputation, which are brought against MYNIC as a direct or indirect result of the disputed domain name or pursuant to the Policy and Rules.
23.2 Further to Rule 23.1, the Parties agree that MYNIC reserves the sole rights and discretion as to which Party to claim an indemnity against and for the avoidance of doubt, where a claim for indemnity is brought by MYNIC against one Party, such claim shall not pre-empt, extinguish or limit MYNIC's rights and discretion to claim an indemnity against the other Party. MYNIC shall also be entitled to exercise its rights and discretion to claim an indemnity against the Parties in any order or concurrently and MYNIC's delay or failure to exercise its said rights and/or discretion herein shall not be deemed as a waiver of the same.
24. Amendments
24.1 The version of these Rules which are in force when the Complaint is submitted to the Provider will govern the Proceeding.
24.2 MYNIC may amend these Rules from time to time as it considers fit. The amended Rules will be posted on MYNIC's web site at least one (1) month before becoming effective except where circumstances beyond the control of MYNIC prevent it from doing so.
25. Miscellaneous
25.1 Words applicable to natural persons shall include any body of persons, company, corporation, firm or partnership incorporated or unincorporated and vice versa.
25.2 Words importing any gender shall include any other gender.
25.3 Words importing the singular number shall include the plural number and vice versa, including the definitions referred to in Rule 2.1 herein.
.com.my Glossary of Technical Terms

.INT
A top-level domain devoted solely to international treaty organizations that have independent legal personality. Such organizations are not governed by the laws of any specific country, rather by mutual agreement between multiple countries. IANA maintains the domain registry for this domain.

A record
The representation of an IPv4 address in the DNS system.

AAAA record
The representation of an IPv6 address in the DNS system.

Administrative contact
Majority of the registries require 4 contacts for a successful domain registration: Registrant, Administrative, Technical and Billing. The Administrative contact is intended to represent the Registrant(owner) of the domain, in any non-technical matters, regarding the management of the domain. Certain extensions require Administrative contact to confirm requests and accept notices about the domain name.

A-label
The ASCII-compatible encoded (ACE) representation of an internationalized domain name, i.e. how it is transmitted internally within the DNS protocol. A-labels always commence the with the prefix "xn--". Contrast with U-label.

ARPA
Originally a reference to the US Government agency that managed some of the Internet’s initial development, now a top-level domain used solely for machine-readable use by computers for certain protocols — such as for reverse IP address lookups, and ENUM. The domain is not designed for general registrations. IANA manages ARPA in conjunction with the Internet Architecture Board.

ASCII (American Standard Code for Information Interchange)
The standard for transmitting English (or "Latin") letters over the Internet. DNS was originally limited to only Latin characters because it uses ASCII as its encoding format, although this has been expanded using Internationalized Domain Names(IDN) for Applications.

Authoritative Name Server
A domain name server configured to host the official record of the contents of a DNS zone. Each Malaysian .com.my domain name must have a set of these so computers on the Internet can find out the contents of that domain. The set of authoritative name servers for any given domain must be configured as NS records in the parent domain.

Automatic Renewal
The service of automatic renewal allows the customers the convenience of automatic billing for the services ordered through the domain registrar. If the automatic renewal is selected, customer's credit card will be automatically charged for the service, which will avoid the interruption in service.

Billing Contact
Majority of the registries require 4 contacts for a successful domain registration: Registrant, Administrative, Technical and Billing. The Billing contact is responsible for the payment of the domain, and is usually assigned to the registrar managing the domain.

Caching Resolver
The combination of a recursive name server and a caching name server.

Cloaking Forwarding
Domains can be forwarded to another URL by using a forwarding service. Cloaking forwarding differs from Apache 301 forwarding by showing the content of the URL being forwarded to, however the URL bar displays the original domain name.

CNAME Record
A CNAME record is an abbreviation for Canonical Name record and is a type of resource record in the Domain Name System (DNS) used to specify that a domain name is an alias for another domain, the "canonical" domain. CNAME has a very specific syntax rule. CNAME can only be set up for the unique subdomain, meaning that it cannot be set up for any subdomain, which has already been set up for the domain. Thus CNAME is most commonly set up for WWW subdomain.

Country-code top-level domain (ccTLD)
A Class of Top Level Domains, generally assigned or reserved by a country, sovereign state, or territory. IANA is the organization, responsible for the ccTLD assignments. Since 2010 there 2 types of ccTLDs: 2 letter ASCII characters TLDs and IDN TLDs, which consist of the native language characters. Each country/territory is able to implement certain restrictions and requirements on the ccTLD assigned to them.

Cross-Registry Information Service Protocol (CRISP)
The name of the working group at the IETF that developed the Internet Registry Information Service (IRIS), a next-generation WHOIS protocol replacement.

Delegation
Any transfer of responsibility to another entity. In the domain name system, one name server can provide pointers to more useful name servers for a given request by returning NS records. On an administrative level, sub-domains are delegated to other entities. IANA also delegates IP address blocks to regional Internet registries.

Deletion
Deletion of the domain results in the domain record being removed from the registry's database. Domain deletion procedure and availability differs depending on each of the TLD's policy. Certain extensions require additional payment to delete a domain name.

DNS zone
A section of the Domain Name System name space. By default, the Root Zone contains all domain names, however in practice sections of this are delegated into smaller zones in a hierarchical fashion. For example, the .com zone would refer to the portion of the DNS delegated that ends in .com.

DNSSEC
A technology that can be added to the Domain Name System to verify the authenticity of its data. The works by adding verifiable chains of trust that can be validated to the domain name system.

Domain lock
In order to prevent unwanted changed to the domain names, customers have an ability to change the locks on their domain names. The domain lock availability depends on individual TLD, and includes clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited, clientRenewProhibited.

Domain Name
A unique identifier with a set of properties attached to it so that computers can perform conversions. A typical domain name is "icann.org". Most commonly the property attached is an IP address, like "208.77.188.103", so that computers can convert the domain name into an IP address. However the DNS is used for many other purposes. The domain name may also be a delegation, which transfers responsibility of all sub-domains within that domain to another entity. domain name label a constituent part of a domain name. The labels of domain names are connected by dots. For example, "www.iana.org" contains three labels — "www", "iana" and "org". For internationalized domain names, the labels may be referred to as A-labels and U-labels.

Domain Name Registrar
An entity offering domain name registration services, as an agent between registrants and registries. Usually multiple registrars exist who compete with each other, and are accredited. For most generic top-level domains, domain name registrars are accredited by ICANN.

Domain Name Registry
A registry tasked with managing the contents of a DNS zone, by giving registrations of sub-domains to registrants.

Domain Name Server
A general term for a computer hardware or software server, which answers requests to convert domain names into something else. These can be subdivided into authoritative name servers, which store the database for a particular DNS zone; as well as recursive name servers and caching name servers.

Domain Name System (DNS)
The global hierarchical system of domain names. A global distributed database contains the information to perform the domain name conversations, and the most central part of that database, known as the root zone is coordinated by IANA.

Dot or “."
Common way of referring to a specific top-level domain. Dot generally precedes the Top Level domain, such as dot com is written down as “.com.my”.

Expiration date
The expiration date determines when the domain registration period ends. In order to avoid downtime for the domain, renewal of the domain at least two weeks before expiration date is strongly encouraged. After the expiration date passes, some registries maintain the record of the domain name under the same owner, however the DNS services are put on hold.

Extensible Provisioning Protocol (EPP)
A protocol used for electronic communication between a registrar and a registry for provisioning domain names.

Extension
Refers to the last portion of the domain name, located after the dot. Domain extension helps determine the registry, to which domain pertains, and allows to accurately classify the domain name.

First Come, First Served (FCFS)
Multiple applications for the same domain name are not accepted. The domain will be awarded to the first registrar who submits a registration request.

FTP
File Transfer Protocol does exactly what it says. The standard network protocol allows the transfer of files from one host to another. There are many FTP clients(programs) available, which allow you to connect to your host and transfer your completed content to your hosting provider's space.

Fully-Qualified Domain Mame (FQDN)
A complete domain name including all its components, i.e. "www.icann.org" as opposed to "www".

GAC Principles
A document, formally known as the Principles for the Delegation and Administration of ccTLDs. This document was developed by the ICANN Governmental Advisory Committee and documents a set of principles agreed by governments on how ccTLDs should be delegated and run.

General Availability Phase
Domains are awarded on first come first serve basis, granted that the domains are available after the previous phases have concluded.

Generic top-level domains (gTLDs)
A class of top-level domains that are used for general purposes, where ICANN has a strong role in coordination (as opposed to country-code top-level domains, which are managed locally).

Glue Record
An explicit notation of the IP address of a name server, placed in a zone outside of the zone that would ordinarily contain that information. All name servers are in-bailiwick of the Root Zone, therefore glue records is required for all name servers listed there. Also referred to as just "glue".

Hints File
A file stored in DNS software (i.e. recursive name servers) that tells it where the DNS root servers are located.

Hostname
The name of a computer. Typically the left-most part of a fully-qualified domain name.

Http
HyperText Transfer Protocol serves as the cornerstone protocol for World Wide Web, which allows the transfer of data between clients and servers.

IANA
See Internet Assigned Numbers Authority.

IANA Considerations
A component of RFCs that refer to any work required by IANA to maintain registries for a specific protocol.

IANA Contract
The contract between ICANN and the US Government that governs how various IANA functions are performed.

IANA Staff
See Internet Assigned Numbers Authority.

ICANN
Internet Corporation for Assigned Names and Numbers(ICANN) is responsible responsible for the coordination of maintenance and methodology of several databases of unique identifiers related to the namespaces of the Internet, and ensuring the network's stable and secure operation.

Internal transfer
Internal transfer refers to a transfer of a domain name within the same registrar. This procedure may be simpler, than starting a domain transfer, which involves 2 different registrars. The internal transfer is possible, after two parties involved in the internal transfer come to an agreement about the terms of the transfer.

Internationalized domain name (IDN)
Internet domain name, which allows the use of a language-specific script or alphabet, such as Arabic, Cyrillic, and Chinese. Adoption of IDN domain names is a significant step towards including non-English speakers into the world of Internet. Internationalized domain name is stored in Domain Name System as ASCII strings, which are transcribed by the use of Punycode.

Internet Architecture Board (IAB)
The oversight body of the IETF, responsible for overall strategic direction of Internet standardization efforts. The IAB works with ICANN on how the IANA protocol parameter registries should be managed. The IAB is an activity of the Internet Society, a non-profit organization.

Internet Assigned Numbers Authority (IANA)
A department of ICANN tasked with providing various Internet coordination functions, primarily those described in a contract between ICANN and the US Government. The functions relate to ensuring globally-unique protocol parameter assignment, including management of the root of the Domain Name System and IP Address Space. ICANN staff within this department is often referred to as "IANA Staff".

Internet Coordination Policy (ICP)
A series of documents created by ICANN between 1999 and 2000 describing management procedures.

Internet Engineering Steering Group (IESG)
The committee of area experts of the IETF’s areas of work, that acts as its board of management.

Internet Engineering Task Force (IETF)
The key Internet standardization forum. The standards developed within the IETF are published as RFCs.

Internet Protocol (IP)
The fundamental protocol that is used to transmit information over the Internet. Data transmitted over the Internet is transmitted using the Internet Protocol, usually in conjunction with a more specialized protocol. Computers are uniquely identified on the Internet using an IP Address.

IP address
A unique identifier for a device on the Internet. The identifier is used to accurately route Internet traffic to that device. IP addresses must be unique on the global Internet.

IPv4
Internet Protocol version 4. Refers to the version of Internet protocol that supports 32-bit IP addresses.

IPv6
Internet Protocol version 6. Refers to the version of Internet protocol that supports 128-bit IP addresses.

Landrush Phase
This phase allows you a greater chance to obtain a domain name prior to General Availability, typically for an increased fee. The fee generally varies depending on how early you want to register. Priority is either first-come, first-served or will go to an auction cpr144449003101 if there are multiple applicants, depending on registry rules. A common fee structure that will be in use is the Early Access Program (EAP). Further details on a specific extensions landrush phase can be found under the landrush section for that a particular domain.

Mail exchange (mx) record
MX record determines which server the mail client will be retrieving the mail from. The MX records for individual domains can be set up in the DNS records section of the client's control panel.

New Generic Top Level Domain (New gTLD)
Starting on July 15th, 2013 ICANN has started process of delegating new Generic Top Level Domains, opening up new opportunities for the internet community. New extensions include popular categories like professional domains, IDNs, general interest domains, and brand domain names.

NS record
a type of record in a DNS zone that signifies part of that zone is delegated to a different set of authoritative name servers.

Parent domain
The domain above a domain in the DNS hierarchy. For all top-level domains, the Root Zone is the parent domain. The Root Zone has no parent domain as it is as the top of the hierarchy. Opposite of sub-domain.

Parking
Many of the registrars offer a free service of domain parking. This allows the customer to quickly register a domain name, and choose the hosting solution at a later date. Very often the registrar's parking DNS servers allow DNS record modification.

Pre-Registration
Paid pre-registration allows you to purchase the domain in the General Availability phase, and the domain will be submitted as soon as the General Availability phase opens.

Primary name server
Practically every domain extension requires minimum 2 DNS servers in order for the domain to be successfully registered. Primary name server is responsible for storing information about the domain routing and making it available for requests.

PTR record
The representation of a IP address to domain name mapping in the DNS system.

Recursive Name Server
A domain name server configured to perform DNS lookups on behalf of other computers.

Redelegation
The transfer of a delegation from one entity to another. Most commonly used to refer to the redelegation process used for top-level domains.

Redelegation process
A special type of root zone change where there is a significant change involving the transfer of operations of a top-level domain to a new entity.

Redemption Grace Period
Redemption Grace Period(RGP) is a period after the expiration date, in which the domain still belongs to the same client, however the functionality is put on hold. The domain can usually be restored after paying for RGP fee. gTLDs often have a Renewal Period of 30 days before the Redemption Grace Period starts.

Regional Internet Registry (RIR)
A registry responsible for allocation of IP address resources within a particular region.

Registrant
See Registrant Contact

Registrant Contact
Majority of the registries require 4 contacts for a successful domain registration: Registrant, Administrative, Technical and Billing. The Registrant contact is the owner of the domain, and is the entity that holds right to use the particular domain name.

Registrar for .com.my
An entity that can act on requests from a registrant in making changes in a registry. Usually the registrar is the same entity that operates a registry, although for domain names this role is often split to allow for competition between multiple registrars who offer different levels of support.

Registry Malaysia .com.my
The authoritative record of registrations for a particular set of data. Most often used to refer to domain name registry, but all protocol parameters that IANA maintains are also registries.

Registry Operator for .com.my Malaysia
The entity that runs a registry.

Reverse IP
A method of translating an IP address into a domain name, so-called as it is the opposite of a typical lookup that converts a domain name to an IP address.

RFCs
A series of Internet engineering documents describing Internet standards, as well as discussion papers, informational memorandums and best practices. Internet standards that are published in an RFC originate from the IETF. The RFC series is published by the RFC Editor.

Root
The highest level of the domain system.

Root Servers
The authoritative name servers for the Root Zone.

Root Zone
The top of the domain name system hierarchy. The root zone contains all of the delegations for top-level domains, as well as the list of root servers, and is managed by IANA.

Root Zone Management (RZM)
The management of the DNS Root Zone by IANA.

RZM Automation
A project to automate many aspects of the Root Zone Management function within IANA. Based on a software tool originally called "eIANA".

Secondary name server
Practically every domain extension requires minimum 2 DNS servers in order for the domain to be successfully registered. Secondary server is responsible for copying information from the primary server. The original purpose of secondary server is to take over the requests, if the primary server is down. Some of the registries no longer put an emphasis on which server is primary or secondary, but many international registries still use the old standard.

Sponsoring organization
The entity acting as the trustee of a top-level domain on behalf of its designated community.

SSL
Secure Sockets Layer (SSL) is a cryptographivc protocol, which is designed to provide communication security over internet. The data entered on the websites, using SSL, is encrypted, thus making it less susceptible to data theft.

Subdomain
In the domain hierarchy, or structure, subdomain is a domain, which is a part of a larger domain. For example, "www.icann.org" is a sub-domain of "icann.org", and "icann.org" is a sub-domain of "org". Subdomains can generally be setup through a DNS server management utility as A records or CNAME records.

Sunrise Phase
A phase in which holders of eligible trademarks have the opportunity to apply and register domain names that correspond to their trademarks. To participate in Sunrise for new gTLDs, trademark holders must validate their trademarks with the Trademark Clearinghouse (TMCH) first and must provide a valid Signed Mark Data (SMD) file for submission.

Technical Contact
Majority of the registries require 4 contacts for a successful domain registration: Registrant, Administrative, Technical and Billing. The Technical contact is intended to assist the Registrant(owner) contact in any queries that pertain to the technical aspects of managing the domain name.

Trademark Clearinghouse (TMCH)
The central database of verified trademarks that was created by ICANN to provide brand protection to trademark holders during ICANN’s new gTLD program. Its' a centralized database of verified trademarks, that is connected to each and every new Top Level Domain (TLD) that will launch.

Top-level domain (TLD)
The highest level of subdivisions with the domain name system. These domains, such as ".com.my" and ".uk" are delegated from the DNS Root zone. They are generally divided into two distinct categories, generic top-level domains and country-code top-level domains.

Transfer
Most commonly, the term transfer refers to a inter-registrar transfer of registrations. The procedure of the tranfer will largely depend on the TLD, and is most commonly completed by requesting an authorization code from the current registrar and initiating the transfer at another registrar.

Trust anchor
A known good cryptographic certificate that can be used to validate a chain of trust. Trust anchor repository (TAR) Any repository of public keys that can be used as trust anchors for validating chains of trust. See Interim Trust Anchor Repository (ITAR) for one such repository for top-level domain operators using DNSSEC.

Trustee
An entity entrusted with the operations of an Internet resource for the benefit of the wider community. In IANA circles, usually in reference to the sponsoring organization of a top-level domain.

U-label
The Unicode representation of an internationalized domain name, i.e. how it is shown to the end-user. Contrast with A-label.

Unicode
A standard describing a repertoire of characters used to represent most of the worlds languages in written form. Unicode is the basis for internationalized domain names.

Uniform resource locator (URL)
Uniform Resource Locator(URL), commonly known as web address, is an address to a resource on the internet. The URL consists of two components: Protocol Identifier(i.e. http, https) and the Resource name(i.e. icann.org)

Unsponsored top-level domain
A sub-classification of generic top-level domain, where there is no formal community of interest. Unsponsored top-level domains(.COM, .NET, .ORG, etc.) are administered according to the policies and processes established by ICANN.

URL Forwarding
URL Forwarding or URL redirection refers to the most common type of forwarding offered by domain registrars. Forwarding occurs when all pages from one domain are redirected to another domain.

UTF-8
A standard used for transmitting Unicode characters.

Variant
In the context of internationalized domain names, an alternative domain name that can be registered, or mean the same thing, because some of its characters can be registered in multiple different ways due to the way the language works. Depending on registry policy, variants may be registered together in one block called a variant bundle. For example, "internationalise" and "internationalize" may be considered variants in English.

Variant bundle
A collection of multiple domain names that are grouped together because some of the characters are considered variants of the others.

Variant table
A type of IDN table that describes the variants for a particular language or script. For example, a variant table may map Simplified Chinese characters to Traditional Chinese characters for the purpose of constructing a variant bundle.

Web host (Hosting Provider)
Web host is a type of an Internet service, which allows users to host content and/or email services by providing hosting space. Most often the hosting providers include control panels and tools for building a website and maintaining mail records.

WHOIS
A simple plain text-based protocol for looking up registration data within a registry. Typically used for domain name registries and IP address registries to find out who has registered a particular resource. (Usage note: not "Whois" or "whois")

WHOIS database
Used to refer to parts of a registry’s database that are made public using the WHOIS protocol, or via similar mechanisms using other protocols (such as web pages, or IRIS). Most commonly used to refer to a domain name registry’s public database.

WHOIS gateway
An interface, usually a web-based form, that will perform a look-up to a WHOIS server. This allows one to find WHOIS information without needing a specialized computer program that speaks the WHOIS protocol.

WHOIS server
A system running on port number 43 that accepts queries using the WHOIS protocol.

Wire format
The format of data when it is transmitted over the Internet (i.e. "over the wire"). For example, an A-label is the wire format of an internationalized domain name; and UTF-8 is a possible wire format of Unicode.

XML
A machine-readable file format for storing structured data. Used to represent web pages (in a subset called HTML) etc. Used by IANA for storing protocol parameter registries.

Zone (DNS Records)
The zone file, also know as the DNS records is a vital component of DNS system, which contains various DNS records, which point to the location of content and email servers for each individual domain. Editing zone is made possible in the client's control panel.

Signed Mark Data (SMD)
A Signed Mark Data (SMD) is file that will allow you to register domain names during the sunrise period of new gTLD’s and request other services. It validates that you trademark has been verified within the Trademark Clearinghouse (TMCH).

Trademark Claims
The trademark claims period extends for 90 days after the close of the Sunrise period. During the Claims period, anyone attempting to register a domain name matching a trademark that is recorded in the Trademark Clearinghouse will receive a notification displaying the relevant mark information. If the notified party goes and ahead and registers the domain name the Trademark Clearinghouse will send a notice to those trademark holders with matching records in the Clearinghouse, informing them that someone has registered the domain name.