.net.so Domain Registration

Somalia Domain - .net.so Domain Registration

Top Selling Somali Domains

.net.so Registry logo

Registration Pricing

  • 1 Year 74.50 USD
  • 2 Years 146.02 USD
  • 3 Years 216.79 USD
  • 4 Years 286.08 USD
  • 5 Years 353.87 USD
  • 6 Years 420.18 USD
  • 7 Years 484.99 USD
  • 8 Years 548.32 USD
  • 9 Years 610.15 USD
  • 10 Years 670.50 USD

Application Fee

Registration Time Frame

2 Days


Yes Details Are Individual .net.so domain registrations allowed?

Yes Details Company or legal entities registrations allowed for .net.so?

No Details Are there requirements, documents, or information needed for .net.so?

Yes Details Are some .net.so domain names restricted?

No Details Does .net.so domain have a special use?

No Details Other information I need to know about .net.so?

No Details Are there any additional fees for .net.so?

No Details Do I need a trademark/brand name to register .net.so?

Yes Details WHOIS Privacy service available?

Trustee / Proxy service offered? Fees? No Details

.net.so Domain FAQ

.net.so General FAQ
Somalia is a country located in the Horn of Africa. Previously under socialist rule, the country has had no defined central government control since civil war in 1991. It is one of the poorest and most violent states in the world and is considered a failed state. It has an estimated population of approximately 10 million people, and the official languages are Somali and Arabic.

Despite civil unrest, Somalia has maintained a relatively healthy informal economy that is largely based on livestock, money transfer companies and telecommunications. Agriculture is the cpr144449003101 most important sector to the economy, but there is a gradual shift towards modern production. Somalia is also noted to have a thriving private airline industry.

Why should I buy a .net.so domain name?
Domain extensions containing .NET are usually intended for entities involved in networking technologies or internet services such as internet service providers and other infrastructure companies. Although intended for cpr144449003101 network related companies, third level .NET domain extensions are being used by a multitude of different types of companies and can be an excellent alternative to the .COM.
What name can I register?

Any Applicant, any party submitting a Domain Name Registration Request and any Domain Name Holder represents and warrants that:

  • to its knowledge, the registration of the Domain Name mentioned in the Application or Domain Name Registration Request will not infringe upon or otherwise violate the rights of any third party;
  • it is not submitting the Application or Domain Name Registration Request and, upon registration, will not use the Domain Name for an unlawful purpose, contrary to public policy or morality, for offensive purposes, to mislead the public and/or contrary to good and fair business practices; and
  • it will not knowingly use the domain name in violation cpr144449003101 of any applicable laws or regulations, including third party interests; and
  • it will keep the WHOIS information related to the Domain Name accurate and up-to-date at all times, both with its Registrar and the Registry. the Application contains true, accurate and up-to-date information and is made in good faith, for a lawful purpose and does not infringe the rights of any third party;
  • it shall participate in good faith in any proceedings described in these Policies commenced by or against the Applicant
What is the registration term allowed for .net.so domain names?
The minimum term for .net.so cpr144449003101 domain names is 1 year(s).
Can anyone register a .net.so domain name?

YesAre Individual .net.so domain registrations allowed?

YesCompany or legal entities registrations allowed for .net.so?

NoAre there requirements, documents, or information needed for .net.so?

YesAre some .net.so domain names restricted?

Violating rights to third parties, names and activities that are offensive, common internet terms are prohibited. See FAQs for complete restrictions.

NoDoes .net.so domain have a special use?

NoOther information I need to know about .net.so?

NoAre there any cpr144449003101 additional fees for .net.so?

NoDo I need a trademark/brand name to register .net.so?

YesWHOIS Privacy service available?

Yes.net.so Trustee / Proxy service offered? Fees?

Don't Have All of These Requirements for Somalia .net.so? Our trustee service provides the required local contact information. Note: Registration for 2 years may be required on some extensions.

Available at Checkout

.net.so Trustee / Proxy Fee: per
.net.so Trustee / Proxy Setup Fee:

How long does it take to register my .net.so domain name?
The domain registration time frame for .net.so during general availability is 2 Days. .net.so is not cpr144449003101 expected to launch until 2 Days. Once launched, a registration time frame will be available.
What are the characters and valid character lengths for .net.so domain names?
Domain Names must:
  • have minimum of 3 and a maximum of 63 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.net.so); and
  • not include a space (e.g. www.ab cd.net.so).
Trustee Service for .net.so

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


Trustee service is not available for this extension

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

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

To transfer your .net.so 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 .net.so requirements before transfer out can be started.
Can I hide my registration information (Private WHOIS)?
Yes. You can activate WHOIS Privacy service cpr144449003101 during the purchase of a new domain.
Can I register my .net.so domain name in different languages (Internationalized Domain Name)?

No, .net.so does not cpr144449003101 support Internationalized Domain Names

Grace period for .net.so 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 .net.so 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 .net.so domain names?
You may visit them here: SO Registry.cpr144449003101
.net.so Domains Dispute & Policy

Last Update 20 August 2012. The most recent source for .net.so domains dispute policy can be found at: www.registry.si/fileadmin/dokumenti/register/ENG/ADR/b_ARDS-ang-v3.pdf

Arnes has, in cooperation with legal experts, prepared a Procedure for Alternative (Domain Name) Dispute Resolution (ADR) . All domain name holders, registrars and Arnes as the registry are bound by it. This procedure is also quick and inexpensive way of resolving domain name disputes but it does not exclude the possibility of using other legal remedies.

Three conditions must be fulfilled to initiate the ADR procedure:

- that the domain name is identical to or interchangeable with the trade mark valid on the territory of the Republic of Slovenia, or company name, as taken from the court register in the Republic of Slovenia, or that it violates copyright under the law of the Republic of Slovenia, or a registered geographic designation to which complainant is entitled under the law of the Republic of Slovenia, or encroaches on rights to personal name under the law of the Republic of Slovenia, or encroaches upon other rights recognised in the legal system of the Republic of Slovenia;
- domain name holder does not have the right to his registered domain name;
- the domain name is registered or used in bad faith.

In case of a dispute independent arbiters are appointed to deliver a verdict with which Arnes must comply with.

When the ADR is started both the complainant and domain holder must follow the proper procedure, use proper forms and mind the terms. We have prepared a graphic illustration of the procedure to offer you some help.



(ARDS Rules)

Version 1.1


1. The ARDS Rules form part of the General terms and conditions for registration of domains under the .si top-level domain (hereinafter: General terms and conditions). These Rules are binding on all Registrars that have contracts with Arnes and on all domain-name holders.
2. The ARDS Rules regulate potential disputes regarding domains registered under the .si top-level domain.
3. The ARDS Rules, together with the ARDS Principles included in the General terms and conditions, have the legal character of a contractually agreed alternative dispute-resolution system. This system does not exclude or restrict, and is not intended to exclude or restrict, court protection that is the constitutional or statutory right of any party.
4. The ARDS Rules and the ARDS Principles may be amended on the basis of a decision ofArnes. All amendments shall enter into force on the date of publication on the Arnes website or subsequently, after the expiry of an interval defined by Arnes.

Terms used Unless otherwise indicated by the text, the terms used in the ARDS Rules shall have the following meanings:

ADMINISTRATOR means Arnes where it manages the ARDS procedure or provides administrative support to the tribunal in the procedure.

DOMAIN means a domain name registered directly under the .si top-level domain.

DOMAIN-NAME HOLDER is a subject allocated a domain name under the .si top-level domain in accordance with the General terms and conditions

DECISION means a decision in which the tribunal rules on a disputed domain name.

ARDS PROCEDURE is the alternative dispute resolution procedure for domains under the .si top-level domain, managed and coordinated by the tribunal president and undertaken by arbiters, and with the necessary administrative and organisational support from the administrator in line with the provisions of the ARDS Rules.

APPEAL is an application by an appellant that initiates an ARDS procedure.

APPELLANT is a third party in the ARDS procedure that asserts that the registered domain name of a domain-name holder violates its rights.

TRIBUNAL is a separate and independent institution that operates under the administrator comprising a tribunal president, a deputy and arbiters.

An ARBITER is a person with special professional knowledge and experience in law or other relevant fields appointed by the tribunal president to rule on the substance of a dispute in a specific domain-name dispute within the ARDS procedure.

The REGISTRAR is a subject with a contract with Arnes on the basis of which it is granted the right to register, and to extend the registration of, domains under the .si top-level domain on behalf of its customers.

The SENATE comprises three arbiters appointed by the tribunal president to rule on a particular domain-name dispute under the ARDS procedure.

DISPUTED DOMAIN NAME is a domain name for which an ARDS procedure has been initiated or is underway.

PARTY is the domain-name holder or appellant.

APPLICATION is any written communication from a party to the ARDS procedure sent to the administrator or tribunal.


1. General provisions
1.1 The ARDS procedure shall be managed in accordance with these Rules. Where these Rules do not provide sufficiently precise instructions for the management of the ARDS procedure, the administrator or arbiter or senate may by agreement apply mutatis mutandis the Rules of Permanent Arbitration at GZS or UNCITRAL.
1.2 The ARDS procedure shall take place in Ljubljana. Where possible through means of communication, arbiters and parties may perform individual tasks in the procedure from other locations.
1.3 The Slovenian language shall be used in ARDS procedures.
2. Tribunal
2.1 The tribunal is specifically established and organised as a separate and independent institution within the administrator to ensure the implementation of impartial and rapid resolution and decision-making in disputes regarding domains under the .si top-level domain.
2.2 The tribunal shall not have legal personality.
2.3 Disputes shall be decided by an arbiter, who must be and remain independent and impartial towards parties to the dispute. If an appellant in the appeal or the domain-name holder in a response to the appeal requests a decision by a senate of three arbiters, a senate of three arbiters shall rule on such dispute.
2.4 The administrator shall undertake administrative and organisational work for the tribunal.
The administrator shall also undertake all necessary organisational activity within the framework of ARDS until the appointment of an arbiter or senate.
2.5 The administrator shall appoint the tribunal president. The administrator shall appoint arbiters to the list of arbiters at the suggestion of and following consultation with the tribunal president. The tribunal president shall select and appoint a deputy from among the arbiters. The tribunal president may not perform the role of arbiter. The names of the tribunal president, his or her deputy and a list of at least 7 arbiters shall be published on the Arnes website.
2.6 The deputy may temporarily replace the tribunal president with regard to his or her duties. The deputy tribunal president may not appoint himself or herself as arbiter to rule on an individual dispute, and may not decide in the event of doubt as to his or her independence, impartiality or ability to decide on an individual case.
2.7 The tribunal president shall form a list of professional associates of the tribunal, which shall be published on the administrator's website.
3. Applications
3.1 An application is any written communication between a party and the administrator or tribunal. The term written shall be taken to include documents, notes, data and applications in electronic form that genuinely represent a designed and sent or received message:
• If it is accessible and suitable for subsequent use;
• If the stored electronic message allows identification of the sender, recipient and time and place of sending or receipt;
• And if the technology and procedures used prevent to a reasonable and sufficient extent changes to or deletions of data that could not readily be identified, or where there exists a reliable guarantee regarding the invariability of the particular message in electronic form.
3.2 All applications submitted by parties pursuant to these Rules must be sent within the intervals stipulated by these Rules:
• By electronic mail to ARDS@arnes.si in MS Word format, and
• By registered mail to Academic and Research Network of Slovenia, ARDS, PO Box 7, 1001, Ljubljana.
Where an application sent by electronic mail differs from an application sent by registered mail, the latter shall be deemed to be the authentic version.
3.3 Applications shall be deemed timely if sent by registered mail before the end of the last day of the interval, and if they arrive in the electronic mailbox of the administrator before the end of the last day of the interval. In the event of technical barriers to the acceptance of applications by electronic mail, the administrator shall suitably extend the interval by a reasonable length of time if the application was sent by mail in a timely manner.
3.4 Where for an individual type of application there exist electronic or paper forms that are appended to these Rules and available on the Arnes website, such forms must be used for such applications, otherwise the administrator and tribunal shall not be obliged to accept them.
3.5 All applications sent by mail must be sent together with enclosed documentation in three copies, otherwise the administrator and tribunal shall not be obliged to accept them.
3.6 All applications by parties, with the exception of appeals, must contain a task number,otherwise the administrator and tribunal shall not be obliged to accept them.
3.7 All applications sent by mail must be signed in holograph by the party. Where the party is a legal person, applications must also contain the stamp of the legal person.
3.8 All applications by parties must be in the Slovenian language. If parties submit documents in other languages, they shall be obliged on request by the administrator, arbiters or senate (if the procedure is operating before an arbiter or a senate of three arbiters) to submit a certified translation of the documents concerned.
3.9 Parties shall submit all applications to the administrator, which shall forward them to the tribunal without delay.
4. Submission
4.1 The administrator shall endeavour to send all communications to parties:
• by electronic mail to the email address; and
• by registered mail with receipt.
4.2 The administrator shall in principle send relevant material or necessary communication to parties' postal and email addresses. If an appellant supplies another postal address for the domain-name holder, and if delivery to the postal address originating from the domain-name holder was unsuccessful, the administrator shall attempt to deliver to the postal address provided by the appellant. If such delivery also fails, the administrator shall act under clause 4.4.
4.3 All communications intended for parties shall be deemed by the administrator to have been received on the date shown on the receipt. Failed email communication shall not affect the success of delivery, although the administrator may attempt to deliver to an alternative email address according to its own judgement. If temporary technical barriers prevent communication by email, the administrator shall attempt the communication as soon as possible or within a reasonable interval.
4.4. Where any communication cannot be delivered to a party due to deficient or inaccurate information that was or should have been provided by the party, or if the party fails to collect a delivery from poste restante within the defined interval, or refuses the delivery, delivery shall be deemed to have occurred on the date it was attempted.
4.5 Parties with an authorised representative may opt in their initial application for communications to be delivered to their representative in accordance with the provisions of this section.
4.6 All communication from arbiters or the senate shall be delivered to parties by the administrator in accordance with the rules of this section.
5. Deadlines
5.1 The deadlines binding on arbiters and the tribunal shall have the legal character of instructions for their behaviour in the particular procedure. Any reasonable breach of deadlines shall not affect the outcome or validity of the procedure.
5.2 Parties shall be obliged to comply with binding deadlines on parties; failure to do so could harm their case.
6. Appeals
6.1 An appeal is an application by an appellant that initiates a procedure.
6.2 Appeals must contain:
• Full name, postal and email address and telephone number of the appellant and lawful agent or representative in the procedure, including the authorisation of the representative if the appellant has a lawful agent or representative;
• A request to decide on the case enclosed in accordance with ARDS rules;
• The contact person and email and postal address to whom and to which all communications under the ARDS Rules should be sent; _postopekARDS-ang-v3.doc
• Data on the domain-name holder, and specifically full name, title or other name, contact person, postal and email address and telephone number, including such data as follows from the whois database and other data available to the appellant;
• An indication of the disputed domain name or names;
• A statement that the appellant meets all the conditions for initiating a procedure in accordance with the dispute resolution principles, together with an explanation thereof, which may not be more than 3000 words in length;
• A statement or request from the appellant for deletion or transfer of the disputed domain or domains;
• If the appellant requests that the dispute be decided by a senate of three arbiters, a statement to that effect;
• A statement as to whether the disputed domain or domains is or cpr144449003101 are subject to court, arbitration or other procedures, and evidence of such procedures;
• Appeals in paper form must include evidence of payment of fees;
• If the appellant is a legal person, an extract from the relevant register of legal persons;
• Any evidence supporting the appeal, in paper, electronic or other form;
• A declaration of the veracity of statements, consent to the use of the ARDS Rules and the General terms and conditions, responsibility, good faith and eligibility for the procedure under the law of the Republic of Slovenia as substantively stipulated on the form.
6.3 Appeals may only relate to multiple domains if such domains are possessed by single domain-name holder.
6.4 Appellants may not submit appeals regarding domains where a decision on the dispute between the appellant and the domain-name holder has already been adopted in an ARDS procedure, or where such procedure has been suspended.
6.5 The administrator shall within seven (7) days of receipt of an appeal and receipt of payment of the fees verify whether the appeal complies with formal requirements. If the appeal has formal deficiencies, the administrator shall call upon the appellant to correct or supplement the appeal as appropriate within five (5) days of receipt of such call.
6.6 If an appellant fails within the interval referred to in clause 6.5 of these Rules to correct or supplement the appeal, the appellant shall be deemed to have withdrawn the appeal.
6.7 Complete appeals shall be registered in the administrator's records. A task number shall be allocated in accordance with the internal rules of the administrator. The administrator shall quote the task number in all communications sent to parties.
6.8 The administrator shall send complete appeals to the domain-name holder together with an explanation from the administrator that the domain-name holder has the right in accordance with ARDS rules to respond to the appeal within an interval of twenty-one (21) days from the date of receipt of the appeal.
6.9 The administrator shall at the same time also inform the registrar or registrars that registered the disputed domain or domains of the appeal.
6.10 From the date when a complete appeal is made, the domain may not be transferred to a third party until the procedure either ends with a decision of the arbiter or panel, and the implementation thereof, or is suspended. (Such domains are assigned blocked status.).
7. Responses to appeals
7.1 Domain-name holders may within twenty-one (21) days from the date of delivery of the appeal submit their responses to the appeal to the administrator.
7.2 Responses to appeals must contain:
• Full name, postal and email address and telephone number of the domain-name holder and lawful agent or representative in the procedure, including the authorisationof the representative if the domain-name holder has a lawful agent or representative;
• The contact person and email and postal address to whom and to which all communications under the procedure should be sent;
• Response to the appellant's proposals to delete or transfer the disputed domain or domains, which together with the explanation may not be more than 3,000 words long;
• Where the domain-name holder requests that the procedure be decided by three arbiters, a declaration to that effect;
• An indication if the disputed domain or domains is or are subject to court, arbitration or other procedures, and evidence of such procedures;
• Where the domain-name holder requests that the procedure be decided by three arbiters, and the appellant has not so requested, the response to the appeal must include written evidence of the payment of fees;
• Any evidence supporting the response to the appeal, in paper, electronic or other form that is both verifiable and suitable for identification.
7.3 The administrator shall send responses to appeals within three (3) days to the appellant, together with an explanation that the appellant has the right within five (5) days of receipt thereof to submit an additional application in accordance with ARDS rules.
7.4 Where evidence of the payment of fees under the conditions referred to in the sixth indent of clause 7.2 has not been submitted, or where it is determined that the domain-name holder has failed to pay such fees, the request referred to in the fourth indent of clause 7.2 shall not be granted.
8. Additional applications by the appellant
8.1 Appellants may within five (5) days of delivery of a response to an appeal submit an additional application, in which they may only respond to the statements made by the domain-name holder in the response to the appeal, and may not cite other facts or submit new evidence unrelated to the response to the appeal.
8.2 Additional applications must contain a statement from the appellant. The statements and their explanations together may not be more than 2,000 words long.
8.3 Arbiters shall not be obliged to respect statements in additional applications that do not fall within the framework of clause 8.1.
8.4 The administrator shall send additional applications by appellants to the domain-name holder within three (3) days.
9. Suspension of ARDS procedure
9.1 The administrator, or if the procedure is taking place before an arbiter or a senate, the arbiter or senate, may at any time suspend the ARDS procedure in part or in full:
• If the appellant withdraws the appeal in part or in full;
• If the parties at any time during the ARDS procedure agree a settlement and submit an application with a declaration regarding the settlement to the administrator in the manner set out in clause 12.1;
• If the appellant fails to pay fees as required by the ARDS Rules;
• If a dispute regarding the same domain between the same parties has been decided in a court or arbitration procedure, where such court or arbitration decision is enforceable in the Republic of Slovenia; _postopekARDS-ang-v3.doc 7
• If the arbiter or senate concludes that the appeal was clearly submitted in bad faith; or
• In other instances determined by these Rules, or where necessary in the assessment of the arbiter or senate.
9.2 The administrator shall inform parties of the suspension of the procedure; parties may object to the suspension of the ARDS procedure by application within five (5) days of receipt of notification of suspension of the procedure.
9.3 The administrator, or if the procedure is taking place before an arbiter or a senate, the arbiter or senate, shall study statements in objections, and shall continue the ARDS procedure as necessary if they consider the appellant's objection to be justified.
10. Fees
10.1 Appellants shall be obliged to pay fees at the same time as submitting appeals to the Arnes subaccount at the Public Payments Administration of the Republic of Slovenia no. 01100-6030345406.
10.2 Fees vary depending on the number of disputed domains covered by the appeal, and shall be calculated as follows:
10.3 Appellants shall pay the supplement for decisions by a senate if they requested a decision by a senate of three arbiters in their appeal. If the appellant did not so request, but the domain-name holder requested a decision by a senate of three arbiters in its response to the appeal, the domain-name holder shall pay into the Arnes transaction account cited in clause 10.1 the supplement for a decision by a senate at the same time as responding to the appeal.
10.4 Fees paid shall generally not be refunded. Fees paid and appropriately reduced may exceptionally be refunded to the payer:
• If the parties agree a settlement prior to the appointment of the arbiter or senate, 75% of the fees paid by each party shall be refunded;
• If the appellant withdraws the appeal, all fees paid by the domain-name holder shall be refunded unless a senate has already been appointed;
• If the appellant fails within the required interval to correct or supplement an incomplete appeal, 70% of the fees paid shall be refunded.
10.5 Fees shall be used to cover the cost of the administrator's services and payments to arbiters at the standard tariff as follows:
• An individual arbiter shall receive 80% of the fees,
• Members of the senate combined shall jointly receive 90% of the fees for decisions by a senate; they may reach a written agreement on the internal division of the aforementioned sum and submit such agreement to the administrator;
• The administrator's administrative costs shall amount to 20% of the fees for decisions by individual arbiters and 10% of the fees for decisions by a senate.
The administrator shall ensure payment to the tribunal president of EUR 350 per month from June 2008 on. If necessary, a new key for the division of fees, which will also be used to cover the costs of the tribunal president or to adjust them to take account of changing circumstances.
10.6 The administrator shall adjust the level of fees set out in clauses 10.2 and 10.5 in accordance with economic trends and its assessment, taking reasonable account of the extent of work, inflation, growth in personal incomes in the sector etc. Changes to the level of fees shall not apply to ARDS procedures in which appeals were submitted prior to publication on the Arnes website of the change in the level of fees.
11. Possibility of settlement
11.1 After receiving all applications from parties, or after the expiry of the deadlines for submission of applications, the administrator shall call upon the parties to agree a settlement if possible.
11.2 In its call to the parties, the administrator may according to its assessment propose any advice regarding the content of the settlement. Such advice shall not affect any possible subsequent judgement by arbiters.
12. Appointment of arbiters
12.1 If both parties fail within ten (10) days of delivery of the proposal in accordance with clause 11.1 of the ARDS Rules to send to the administrator an application with a statement that they have agreed a settlement, the administrator shall immediately inform the tribunal president, who shall as soon as possible and without delay appoint an arbiter, or, where so requested by the appellant in the appeal or by the domain-name holder in the response to the appeal, a senate of three arbiters.
12.2 The tribunal president shall appoint within seven (7) days an arbiter or a senate of three arbiters from the list of arbiters. If there are no other barriers, appointments shall be made under the rotation principle as designed by the tribunal president, and must continually ensure conditions in which all appointed arbiters in each specific case are always independent and impartial. The tribunal president shall appoint a senate president from a senate of three arbiters.
12.3 Arbiters with concerns regarding their independence and impartiality shall inform the tribunal president thereof without delay so that the president can appoint another arbiter. Arbiters may do so at any time during the ARDS procedure prior to the issuing of a decision. The ARDS procedure shall begin anew before a new arbiter or before an altered senate.
12.4 If the tribunal president at any point during the ARDS procedure determines that a particular arbiter for any reason whatsoever will be unable to perform his or her duties, or will be unable to do so in a timely manner, or if doubt arises as to the arbiter's independence and impartiality, the president shall appoint another arbiter without delay. The ARDS procedures shall begin anew before a new arbiter or before an altered senate.
12.5 Arbiters who are appointed shall immediately complete the form with a declaration of independence and impartiality, and shall send it to the administrator. Parties shall have the right to examine such declarations.
12.6 The administrator shall inform parties of each appointment of arbiters.
13. ARDS procedure before arbiters
13.1 When the administrator receives an arbiter's declaration of independence and impartiality, it shall send the arbiter a copy of all applications by parties in electronic and paper form. It shall make copies of documents where necessary. Where a particular domain dispute is decided by a senate, copies of the documents shall be sent to all senate members.
13.2 All arbiters shall be obliged to treat all parties to disputes equally.
13.3 Where particular documents or other evidence are stored at the administrator, arbiters may inspect them at any time during the administrator's office hours by prior arrangement.
13.4 An arbiter or senate may at any time request via the administrator additional information and clarification from the parties. Where such information or clarification is not received within the interval determined, arbiters or senates shall act according to their judgment. Parties may not communicate with arbiters at their own initiative.
13.5 Any arbiter may at any time during the ARDS procedure request that the tribunal president assign him or her a professional associate. The costs of such associates shall be covered from the remuneration due to the arbiter. The tribunal president shall appoint a professional associate from the list of professional associates.
13.6 When a senate is appointed, the senate president shall be exclusively responsible for communication with the administrator, and shall undertake all other activities required to implement the procedure. When any member of the senate disagrees with a decision of the senate president regarding the management of the procedure, he or she may request that the senate make the final decision on the matter.
13.7 The senate shall adopt decisions after discussion by all three arbiters by a majority vote of all members. The senate may discuss cases using electronic means. All three members of the senate shall have 1 vote each.
14. Influence of court or arbitration procedures
14.1 The enforcement of court or arbitration decisions enforceable in the Republic of Slovenia shall have priority over enforcement of decisions of the tribunal and the ARDS procedure. The tribunal and administrator shall act in accordance with binding court and arbitration decisions irrespective of the ARDS Rules.
14.2 Both parties shall be obliged to inform the tribunal of any court or arbitration procedure regarding the disputed domain or domains that is running in parallel. The arbiter or senate shall assess what such a procedure means, and if necessary may suspend the procedure in part or in full.
15. Decisions and implementation of decisions
15.1 Decisions may reject appeals in full as unfounded, or may uphold appeals in part or in full.
15.2 If an appeal is upheld in part or in full, the decision shall in accordance with the contents of the appeal order that the particular domain be deleted or transferred to the appellant. If an appellant requests in an appeal the transfer of a particular domain, but the arbiter or senate concludes that there are no grounds for so doing, but that there are grounds for deleting the domain, the decision shall order that the domain be deleted.
15.3 Arbiters or senates shall adopt and compose an explained decision in written form within twenty-one (21) days of receipt of the documentation, and shall send it in written and electronic form to the administrator. This deadline shall be extended where justified by circumstances, particularly where further clarification or additional evidence must be obtained from the parties. _postopekARDS-ang-v3.doc
15.4 There shall be no appeals against decisions in the ARDS procedure.
15.5 The administrator shall within seven (7) days send the decision to parties, and shall inform the registrar or registrars that registered the disputed domain or domains. If the decision orders that the domain be deleted or transferred, the administrator should announce in its notification to parties that the decision will be enforced after twenty-one (days) from delivery of the decision to the domain-name holder. Decisions shall be published on the Arnes website. Natural persons shall only be identified by their initials, while other personal data pertaining to them shall not be published.
15.6 If the decision is to delete the domain, the administrator shall implement the decision after twenty-one (21) days from delivery of the decision to the domain-name holder. If the decision is to transfer the domain to the appellant, the administrator shall implement the decision after twenty-one (21) days from delivery of the decision to the domain-name holder if it has received from the appellant's registrar an application and payment for registration of the domain name on behalf of the appellant in accordance with the General terms and conditions. If within the aforementioned interval Arnes does not receive an application for registration on behalf of the appellant, the domain shall be allocated quarantine status, and shall then be deleted from the database of registered domain names after thirty (30) days.
15.7 On the date that a decision was sent to parties, the general prohibition on the transfer of the domain name to third parties shall be lifted for those domains not subject to deletion or transfer under the relevant decision.
15.8 After deletion or transfer of the domain, the domain-name holder may not acquire the same domain without the consent of the appellant.
15.9 Insofar as a domain is transferred on the basis of a decision to the appellant, the appellant shall be obliged within one (1) month to conclude a domain registration contract with a registrar, otherwise the transfer shall have the effect of a deletion.
.net.so Glossary of Technical Terms

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.

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.

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 Somali .net.so 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.

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 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.

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 "", 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 “.net.so”.

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.

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.

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.

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

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

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.

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.

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

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.

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.

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.

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.

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 .net.so
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 Somalia .net.so
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 .net.so Somalia
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.

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.

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.

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.

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 ".net.so" 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.

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.

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.

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

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.

A standard used for transmitting Unicode characters.

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.

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.

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.