Registration and Launch Policies
Registration and Launch Policies
- Registration Policies
- Acceptable Use Policy and Takedown Policy
- Reserved and Premium Names Policy
- Launch Plan
- Qualified Launch Program
- Sunrise Policies
- Quiet Period
- Protected Names Policies
- General Availability
- IP Claims Notification
- Dispute Policies
- Sunrise Dispute Resolution Policy
- Whois Access Policy
Date 22 May 2015
Registration and Launch Policies
Revision date: 22 May 2015
1 Registration Policy for TLD .fans
TLD .fans is an open, unrestricted Top Level Domain. .fans is a niche TLD offering an intuitive address for fan engagement across sport, music, celebrity and entertainment. Any person or legal entity anywhere in the world may register a TLD .fans domain name, and will be subject to the policies herein.
Asiamix Digital Limited with its principal office at Unit 15, 1/F, Block 2, Office Building, 96 Siena Avenue, Discovery Bay North, Hong Kong (“Registry”), is the Registry operator for the .fans TLD.
Please note that the Registry may modify this Policy from time to time in its sole discretion. Any modifications or amendments to this Policy shall be effective upon posting on the .fans Registry website and giving 90 days prior written notice to all .fans Accredited Registrars.
Term. Names may be registered for a period of no less than one (1) year and no more than ten (10) years, commencing on the date on which the Registry accepts the request for registration submitted by the Accredited Registrar.
Names registered in .fans must have at least 1 character and not more than 63.
Second level domain names registered in .fans may contain the 26 letters of the Latin alphabet, “a-z”, the ten digits, “0-9”, a hyphen, “-“, and a dot,”.”. The dot is used exclusively to separate labels. The hyphen may not appear at the beginning or end of a label. A label may not contain more than 63 characters and the total number of characters in a domain name may not exceed 255 (including a final dot that is not normally displayed as a part of the name).
Two hyphens may appear in the third and fourth positions in a label in a .fans name only in accordance with the policies and procedures for Internationalized Domain Names (IDN) referenced below.
Dotless domains are not permitted in the TLD. Dotless domain names are those that consist of a single label (e.g., http://fans, or mail@fans). Dotless names would require the inclusion of, for example, an A, AAAA, or MX, record in the apex of a TLD zone in the DNS (i.e., the record relates to the TLD-string itself).
Registry reserves the right to implement IDNs in .fans.
All names registered in .fans TLD are subject to the .fans Reserved and Premium Names Policy outlined in section 3 below.
Proxy Registrations are permitted in accordance with ICANN policies.
2 Acceptable Use Policy and Takedown Policy
All .fans names are subject to this Acceptable Use Policy. Please note that the Registry may modify this Policy from time to time in its sole discretion. Any modifications or amendments to this Policy shall be effective upon 90 days prior notice posting on the .fans Registry website and giving notice to all .fans Accredited Registrars.
The Registry reserves the right to deny, cancel or transfer any registration or service, or place any domain name(s) on registry lock, hold, or other status, as it deems necessary, at its sole discretion and without notice:
- 2.2.1 to protect the integrity, security, and stability of the domain name system;
- 2.2.2 to comply with any applicable court orders, laws, requests or rulings from law enforcement agencies,
government agencies, or other organizations, or dispute resolution proceedings;
- 2.2.3 to avoid any liability, civil or criminal, on the part of the Registry, as well as its affiliates, subsidiaries, officers,
directors, and employees or its service providers;
- 2.2.4 per the terms of the Registration Agreement;
- 2.2.5 to respond to or protect against any form of malware (which includes, without limitation, malicious code or
software that may affect the operation of the Internet);
- 2.2.6 to comply with specifications of any industry group or recognized authority on Internet stability (i.e., RFCs);
- 2.2.7 to correct mistakes made by the Registry or any Registrar in connection with the domain name registration;
- 2.2.8 for the non-payment of any fees owed; or
- 2.2.9 for non-compliance with the terms of the Founders Program as set forth in part 5 below
The following activities are prohibited, and constitute registration abuse which may result in cancelling, suspending, transferring and/or deleting of the domain name. The Registrant and/or user of domain names in the TLD agrees to the following:
- 2.3.1 Not upload, post, email, publish, transmit or otherwise make available (collectively, “Transmit”) any Content that in the Registry’s sole discretion is unlawful, harmful, threatening, abusive, harassing, tortious, defamatory, vulgar, obscene, libellous, invasive of another’s privacy, hateful, or racially, ethnically or otherwise objectionable;
- 2.3.2 Not impersonate any person or entity, including, but not limited to, a celebrity, a personality, musician, band, club, team, brand, TV show, an official, forum leader, guide or host, or falsely state or otherwise misrepresent the Registrant and/or user’s affiliation with a person or entity;
- 2.3.3 Not harm minors in any way; not abuse children or Transmit child abuse material;
- 2.3.4 Not distribute malware; or operate botnets;
- 2.3.5 Not engage in phishing, piracy, trademark or copyright infringement, fraudulent or deceptive practices,
counterfeiting or other activity contrary to applicable law;
- 2.3.6 Not forge headers or otherwise manipulate identifiers in order to disguise the origin of any Content
- 2.3.7 Not Transmit any Content that the Registrant or user does not have a right to make available under any law or
under contractual or fiduciary relationships (such as inside information, proprietary and confidential
information learned or disclosed as part of employment relationships or under nondisclosure agreements);
- 2.3.8 Not Transmit any Content that infringes any patent, trademark, trade secret, copyright or other proprietary
rights (“Rights”) of any party;
- 2.3.9 Not Transmit any unsolicited or unauthorized advertising, “junk mail,” “spam,” “chain letters,” “pyramid
schemes,” “phishing” or “pharming”;
- 2.3.10 Not Transmit any content that contains software viruses or any other computer code, files or programs
designed to interrupt, destroy or limit the functionality of any computer software or hardware or
- 2.3.11 Not interfere with or disrupt servers or networks, or disobey any requirements, procedures, policies or
regulations of networks;
- 2.3.12 Not relay email from a third party’s mail servers without the permission of that third party;
- 2.3.13 Not use “robots” or otherwise harvest others’ email addresses for purposes of sending unsolicited or
- 2.3.14 Not upload, post, email, or transmit the same message, URL, or post multiple times;
- 2.3.15 Not intentionally or unintentionally violate any applicable local, state, national or international law, including, any rules of any national or other securities exchange, and any regulations having the force of law; and,
- 2.3.16 Not “stalk” or otherwise harass another, or engage in cyber bullying.
All Registrants must comply with all applicable laws including those that relate to privacy, data collection, consumer protection (including in relation to misleading and deceptive conduct) and applicable consumer laws in respect of fair lending, debt collection, disclosure of data and financial regulations.
If a Registrant is collecting and maintaining sensitive health and financial data, then they must comply with applicable laws on the provision of such services and include security measures appropriate to that sector.
All .fans domain names are subject to ICANN’s policies, including the dispute resolution procedures of UDRP, URS and the rights of trademark holders as enforced by courts of law.
This Acceptable Use Policy is to assist Registrants in the lawful use of .fans domain names and does not exhaustively cover all potential abuses of domain names which may result in the suspension, transfer, cancellation or locking of a domain name under this policy.
Registrant may not operate third level registries with more than 100 sub-domains, unless it has received express written permission of the Registry.
3 Reserved and Premium Names Policy
Reserved and Premium Names Policy (“Policy”) of .fans.
Please note that the Registry may modify this Policy from time to time in its sole discretion. Any modifications or amendments to this Policy shall be effective upon posting on the .fans Registry website and giving ninety (90) days prior written notice to all .fans Accredited Registrars.
The Registry may reserve (i.e. withhold from registration or allocate to itself), restrict, or block certain domain names from registration (“Reserved List”). The Registry may add or remove domain names from its Reserved List at any time.
This Reserved List of domain names shall generally consist of:
- 3.3.1 Names reserved for Registry operations and other purposes, including without limitation, certain names retained for use by Registry’s strategic partners; names for later release;
- 3.3.2 Names reserved to comply with ICANN requirements such as, but not limited to, Specification 5 of the .fans gTLD Registry Agreement;
- 3.3.3 Names reserved as part of the Protected Names program , including, but not limited to brands, celebrities, sport teams, musicians, bands, entertainers, tv shows, films, clubs reserved for the purposes of allocation to the appropriate parties or communities of their supporters;
- 3.3.4 Premium Names including generic names and key words for later release by the Registry;
- 3.3.5 Names that are temporarily unavailable due to processing delays from Sunrise Registrations, or for other
Premium Generic Names. The Registry may reserve generic key words under this policy for individual release or later bulk release. Interested parties are encouraged to apply to the Registry for any such name by application to the Registry http://activate.your.fans stating the intended purpose for the use and attaching any business plans. Applications will be reviewed and any offers made shall be in the Registry’s sole discretion.
4 Launch Plan – Overview
The launch of the .fans TLD will include the following consecutive phases:
- 4.1.1 Allocation of Qualified Launch Program Names;
- 4.1.2 Sunrise – end date sunrise with at least 60 day duration;
- 4.1.3 Quiet Period of not more than 2 weeks;
- 4.1.4 General Availability (including Protected Names program).
Timing of each phase will be announced via the Registry website.
5 .fans Founders Program
Free .fans domains under Founders Program application.
- 5.1.1 To participate in the .fans Founders Program the Registry will consider applications from qualifying brands, entities and individuals to allocate domains free of Registry fees for a period of at least one year (“Initial Founders Period”).
- 5.1.2 In order to qualify, Applicants must represent a team, artist, celebrity, club or other entertainment brand, demonstrate a significant and active fan-base, and the selected domain name must have a strong nexus to the relevant brand or registered trade mark.
A core aim of the Founders Program is to show .fans as a primary destination for supporting fan- facing activities. To help facilitate this, the Registry mandates that all .fans Founders Program participants must:
- 5.2.1 activate the domain in the DNS immediately upon registration;
- 5.2.2 point it at a fan-focused web property such as web page, Facebook page or website;
- 5.2.3 maintain active use of the domain throughout the Initial Founders Period;
- 5.2.4 agree to the Registry’s promotion of the domain(s) and associated websites;
- 5.2.5 not transfer the domain to another Registrant (except for the purposes of corporate reorganisation,
reconstruction to a verified successor in title or change of management company) during the Initial Founders Period.
In return, Founders Program participants benefit from marketing exposure through the Registry and secure a valuable digital asset for their brand. See Registry Website for more details.
Within 6 months after registration the registrant will:
- begin active use of the domain as a primary domain for a fan-focused web property. Examples include, but are not limited to:
– using the domain as the primary address for a section of an existing fan-focused website (microsite);
– using the domain as the primary address for a new fan-focused website; the Registry may suggest or facilitate a particular use of the domain;
– rebranding an existing fan-focused website under the .fans address;
- submit the domain to Google search index;
- if multiple domains are used for content served by the .fans domain, nominate the .fans domain as a primary (preferred) domain for Google search index;
- for the avoidance of doubt, using the domain purely for redirection to a website that uses a different primary domain is only allowed during the first 6 months from registration date.
To submit a no-obligation expression of interest for the .fans Founders Program please complete the form at http://activate.your.fans. The Registry shall in its absolute discretion select (or reject) Applicants for the .fans Founders Program.
The Registry reserves the right to modify the terms of the .fans Founders Program or to discontinue the program at any time.
6 Sunrise Policies
Trademark Sunrise Overview
- 6.1.1 Sunrise allows the holder of a trademark that has previously been verified by the officially mandated ICANN Trademark Clearinghouse (“Trademark Holder”) to notify the Registry of its registered trademark, and apply to register the corresponding .fans domain name.
- 6.1.2 During Sunrise only Trademark Holders may apply for a domain name that constitutes an “exact match” of their mark, in accordance with the ICANN Trademark Clearinghouse (“TMCH”) policy. The Registry will charge a Sunrise domain name registration fee for registrations of domain names during Sunrise. (“Sunrise Price”).
- 6.1.3 The Trademark Holder is responsible for protecting any domain names which match its trademarks. If a Trademark Holder fails to reserve any domain name during Sunrise, any other party is free to register that domain name during General Availability, subject to Registry Policies, the TMCH Claims Service, and applicable laws and regulations.
- 6.1.4 Because some generic terms may be the subject of trademark registration, certain generic names may be withheld from Sunrise availability, in accordance with Registry policy.
- 6.1.5 The Sunrise Dispute Resolution Policy (“SDRP”) describes the process and standards that will be applied to resolve challenges alleging that a domain name has been registered, or has been declined to be registered, in violation of the Registry’s Sunrise Policy. This SDRP will not be applied to Registry-reserved names (including any Founders’ Program and Premium Names reserved) in the TLD.
- 6.1.6 Please note that the Registry may modify this Policy from time to time in its sole discretion. Any modifications or amendments to this Policy shall be effective upon posting on the .fans Registry website and giving 90 days prior written notice to all .fans Accredited Registrars.
6.2.1 The Registry will operate an “End-Date Sunrise” process. This means allocation of names occurs at the end of Sunrise. Sole Applicants meeting all Sunrise criteria for an available domain will be awarded their applied-for domain. In the event there are multiple eligible applications for the same domain name, all such Applicants will be notified of the competing Applications, and the process to resolve contentions as stipulated in 6.4 below. The .fans Sunrise shall have duration of at least sixty (60) days.
The Registry requires the payment of a minimum of one year (1) of non-refundable registration fee with a Sunrise Application. The renewal price for domain names registered during Sunrise and names registered as part of the Protected Names program will be the normal renewal fee (also used for the General Availability phase) then in effect.
- 6.4.1 In the event there are duplicate Applications for the same exact match trademark, the Registry reserves the right to give preference to certain trade and service mark classes in preference to others. In particular if relevant the Registry may give priority to SMD holders with goods and services in the following relevant NICE classes: no: 9 , 35, and 41. If the Registry cannot resolve the competing Sunrise Applications by relevance of class to the purpose of the TLD, those Applicants may participate in a Sunrise Auction.
- 6.4.2 If there are multiple Trademark Holders with rights to the same term which all apply for a given, available domain, those Applicants may participate in a post-Sunrise auction at the end of Sunrise. The auction will be conducted by the Registry’s third party auction provider. However parties are not obligated to participate in an auction; they may choose to withdraw their Sunrise Application or privately resolve their conflicting Applications. The starting bid for an auction is the Sunrise Registration Fee plus $1 USD with bid increments escalating during the auction. The auction winner will be awarded the domain provided that the auction winner pays the winning auction bid.
- 6.4.3 Auction Rules: full Auction rules will be distributed to eligible participants in reasonable time prior to any auction.
- 6.4.4 The results of any auction shall be deemed final and binding upon parties.
The TMCH & Trademark Validation
The Trademark Clearinghouse (“TMCH”) is responsible for maintaining Sunrise eligibility requirements, validating and authenticating marks (as applicable), and hearing challenges regarding validity of a mark or SMD File. When processing Sunrise Applications, the Registry relies on the validity of mark holder information contained in SMD Files provided by the TMCH.
Disputes regarding the validity of an SMD File are subject to a separate TMCH dispute process and should be submitted to the TMCH using its dispute resolution procedures outlined at http://trademark-clearinghouse.com/dispute prior to initiation of a complaint under the SDRP. In the event the TMCH reports fraud in a SMD File or a Sunrise Application, the Registry may disqualify the Sunrise Application or, in the event that fraud is detected after the Sunrise period, suspend, transfer, reserve and/or delete the applicable domain(s). The Registry reserves the right to put on hold any domain name pending final dispute resolution.
7 Quiet Period
There will be a quiet period of up to two weeks at the end of Sunrise and the commencement of General Availability.
8 Protected Names Policies
As a further protection for well-known entities, the Registry may reserve domains under this policy as “Protected Names”. These may include names for high profile brands or names in music, sport, tv, film, celebrities, clubs, publishing and other sectors or pursuits which may have fan bases of supporters, enthusiasts or collective admirers.
Eligibility criteria and release mechanisms for Protected Names will apply only after completion of Sunrise and on commencement of General Availability.
Protected Names program will commence after the end of the Quiet Period and will run in parallel with General Availability. Protected Names program will run for a limited time period (end date to be determined by the Registry to take place no later than 24 months after the start of General Availability). Upon completion of the program Protected Names will become available under normal General Availability terms or reserved by the Registry pursuant to section 3 above.
- 8.3.1 Protected Names program Phase 1
Parties eligible for Protected Names program Phase 1 are artists, celebrities, clubs, sports teams, institutions and entities with registered trademarks related to sports, music or entertainment, or substantial goodwill (determined on the evidence provided by the Applicant in the sole discretion of the Registry) in the relevant brands (an “Eligible Party”).
- 8.3.2 Protected Names program Phase 2
Protected Names program Phase 2 will be available to Eligible Parties with the addition of communities of their supporters (a “Community”).
- 8.3.3 Application, validation and registration process
Any Eligible Party or Community may apply for domain names reserved on Protected Names list at http://activate.your.fans by completing a simple Application to assist the Registry in verifying the Applicant’s identity and links to the requested Protected Name. Awards of any such Protected Name will be made in the sole discretion of the Registry, and will be subject to Registration Agreement with a Registrar. Registry may request additional information or reasonable actions from the Applicant to prove its association with the relevant brand or fan club.
Applications will be considered by the Registry on a first come first served basis. Registry is responsible for validating and authenticating marks (as applicable), and hearing challenges regarding validity of a Protected Name Application. When processing Protected Names Applications, Registry relies on the validity of information provided by the Eligible Party (or Community as the case may be).
Upon a successful validation the Registry will issue a code to the Eligible Party or Community that will enable registration of the domain with any Registrar participating in the .fans Protected Names program.
- 8.3.4 The Registry will charge a Protected Names domain name registration fee for registrations of Protected Names.
- 8.3.5 An Eligible Party or Community is responsible for protecting any domain names which match its brand. If an Eligible Party or Community fails to reserve any domain name as part of the Protected Names program, any other party is free to register that domain name after the completion of the Protected Names program, subject to Registry Policies, and applicable laws and regulations.
9 General Availability
Upon the commencement of General Availability, available names will be allocated via .fans Accredited Registrars on a first-come first-served basis subject to Registry Policy and ICANN requirements. Protected Names will be available only to Eligible Parties or Communities pursuant to the terms of the Protected Names program as established in section 8 above. Please note that the Registry may modify this Policy from time to time in its sole discretion. Any modifications or amendments to this Policy shall be effective upon posting on the .fans Registry website and giving ninety (90) days prior written notice to all .fans Accredited Registrars.
At least the first ninety (90) days of the General Availability period will subject to the Claims Notifications. As such, an Applicant for a domain name must acknowledge and accept the information contained within any Claims Notice that may be presented before processing of the Application for registering a domain name. See the Claims Notices section of these policies for more information on the Claims Period.
10 Claims Notices
The Registry will send Claims Notices in accordance with the ICANN and TMCH policies during the Sunrise period and for a further period of at least ninety (90) days commencing from the General Availability launch date of .fans. In the event an Applicant proceeds with a Registration Application, a notification is sent to the record holder of the TMCH entry. Such Applicant may further be deemed on notice of the intellectual property claims corresponding to the TMCH entry.
11 Dispute Policies
All Registrants agree to participate in and abide by any determinations made as part of the Registry’s dispute resolution procedures, including:
- 11.1.1 Uniform Domain Name Dispute Policy (http://www.icann.org/en/help/dndr/udrp),
- 11.1.2 Uniform Rapid Suspension Policy (http://newgtlds.icann.org/en/applicants/urs)
- 11.1.3 Transfer Dispute Resolution Policy (http://www.icann.org/en/help/dndr/tdrp)
- 11.1.4 Trademark Sunrise Dispute Resolution Policy (see below)
12 Sunrise Dispute Resolution Policy
This Sunrise Dispute Resolution Policy (the “SDRP”) is incorporated by reference into the Registration Agreement. This SDRP is applicable to the Trademark Sunrise. This SDRP is effective as of 1 May 2015. An SDRP Complaint may be filed against a domain name registered during the .fans TLD during its Sunrise period, and until 10 days after the close of the Sunrise period. This SDRP describes the process and the standards that will be applied to resolve disputes in relation to an allegation that a domain name has been registered by a third party in violation of the Registry’s SDRP criteria. Please note that the Registry may modify this Policy from time to time in its sole discretion. Any modifications or amendments to this Policy shall be effective upon posting on the .fans Registry Website and giving 90 days prior written notice to all .fans Accredited Registrars.
Initiating a Dispute and Internal Review
- 12.1.1 Prior to initiating a dispute under this Policy, potential complainants must submit complaints first to the Registry at: firstname.lastname@example.org
- 12.1.2 As a first step the Registry shall attempt to resolve the issue internally without charge. In particular, in the case that the matter is more appropriately dealt with by the Sunrise Registrar, or the TMCH, it will advise the potential complainant accordingly. If the complaint relates to a Registry process error affecting the applicable domain(s), the Registry will investigate and if upheld seek to resolve such errors internally without charge. In the event the Registry is unable to resolve the dispute, it will notify the potential complainant to submit its complaint for resolution directly to arbitration at an appropriately located arbitration provider to accommodate the complainant as outlined in this Policy. The Dispute Resolution Provider to be appointed within suitable timeframe for each complainant may include the National Arbitration Forum (USA), WIPO (Switzerland or Singapore) or other Arbitration services provider.
- 12.1.3 Any claim or dispute not made to the Registry within ten (10) days of the end of Sunrise will be time barred from consideration by the Registry.
12.2.1 A complainant, complainant’s counsel, or complainant’s counsel’s firm, that is found to be responsible for filing three or more SDRP complaints (in any TLD, .fans or otherwise) deemed to be frivolous may be barred from further use of this policy at the Registry’s discretion. A frivolous complaint comes from a complainant that has habitually lodged vexatious complaints, persistently and without reasonable grounds. In denying use of this policy, the Registry or the Dispute Resolution Providers, may consider the number of complaints lodged under this Policy or any similar third-party registry policies and paths of dispute resolution, which were resolved in favor of a respondent, or otherwise consider a pattern of abusing such policies.
- 12.3.1 A registered domain name in the TLD will be subject to an administrative proceeding upon submission of a complaint that a third-party Sunrise Registration was improper under one or more of the following criteria.
- 12.3.2 Improper Sunrise Registration-Trademarks. A complaint under this section shall be required to show by reasonable evidence that a registered domain name in the .fans TLD does not comply with the provisions of the Registry’s Sunrise Program. The complaint must prove one or more of the following elements:
184.108.40.206 at time the challenged domain name was registered, the Registrant did not hold a trademark registration of national effect (or regional effect) or the trademark had not been court-validated or protected by statute or treaty;
220.127.116.11 the domain name is not identical to the mark on which the Registrant based its Sunrise registration;
18.104.22.168 the trademark registration on which the Registrant based its Sunrise Registration is not of national effect (or regional effect) or the trademark had not been court-validated or protected by statute or treaty; or
22.214.171.124 the trademark registration on which the domain name Registrant based its Sunrise registration did not issue on or before the date specified by the Registry in its Sunrise Criteria, if one was specified.
Evidence and Defences
Arbitrators will review the Registry’s Sunrise Policy in making its decision
Harmless error. A Respondent may produce evidence to show that, although the Sunrise Registration was granted based on submission of the wrong documents, or documents containing an error, the true and correct evidence existed at the time the Sunrise Registration was applied for and, thus, the registration would have been granted.
If the Arbitrator finds that the domain name was improperly registered during the Sunrise period, the sole remedy for a Complaint filed under this SDRP shall be cancellation of the registration, and return of the cancelled domain name to the pool of available names available for registration. In the event an SDRP dispute is brought by an auction bidder for the same domain name, the auction will be suspended until the dispute is resolved.
- 12.6.1 Dispute Resolution Provider – Selection of Procedure.
Following the internal review process set forth in Section 1, the Registry will appoint a dispute resolution provider such as the National Arbitration Forum (“Forum”) , WIPO Arbitration and Mediation Centre (“WIPO”) or other appropriate provider (collectively referred to as the “Dispute Resolution Provider”) by submitting the complaint directly to such provider as directed by the Registry. Before submission to such provider the Registry will inform complainant and provide adequate time for the preparation of the complaint. The Dispute Resolution Provider will administer the proceeding and select a qualified and eligible Arbitrator(s) (“Arbitrator”). The Dispute will be handled according to the established rules for such providers, Sunrise Dispute Resolution Policy (“Rules”), setting forth a fee schedule and other technical and process requirements for handling a dispute under this SDRP. For example, if the Forum were to be selected as the most appropriate Dispute Resolution Provider the proceedings will be conducted according to this SDRP and the applicable Rules of the Forum. Any fees will be those set by the Dispute Resolution Provider.
- 12.6.2 Registry’s or Registrar’s Involvement
Neither the Registry nor Registrar will participate in the administration or conduct of any proceeding before a Dispute Resolution Provider. In any event, neither the Registry nor the Registrar is or will be liable as a result of any decisions rendered by the Dispute Resolution Provider. Any Sunrise Registration in the TLD involved in a SDRP proceeding will be locked against transfer to another domain name holder or another Registrar in the event of a dispute and during the course of a proceeding. The contact details of the holder of a registered domain name in the TLD, against which a complaint has been filed, will be as shown in the Registrar’s publicly available Whois database record for the relevant Registrant. The Registry and the applicable Registrar will
 For the purposes of analysis of this element, neither the gTLD itself, nor the “dot,” shall be considered.
 A Registry may, though its agreement with Registrars, instead require the Registrar to perform the lock and/or implementation steps.
comply with any Arbitration decision and make all appropriate changes to the status of the domain name registration(s) in their Whois databases.
The Registrant of a registered domain name in the TLD shall be promptly notified by the Dispute Resolution Provider of the commencement of a dispute under this SDRP, and may contest the allegations of the complaint or show other cause why the remedy requested in the complaint should not be granted in accordance with this SDRP. In all cases, the burden of proof shall be on the complainant, and default or other failure of the holder of the registered domain name shall not constitute an admission to any allegation of the complaint. The Dispute Resolution Provider shall promptly notify all named parties in the dispute, as well as the Registrar and the Registry of any decision made by the Arbitration.
12.6.4 Decisions 126.96.36.199
The Arbitrator may state the basis on which the decision is issued in summary format and may include such commentary or guidance as the Arbitrator deems appropriate;
the decision shall state whether a registered domain name in the TLD is to be cancelled or if the status quo maintained; and
decisions made under this SDRP may be published by the Dispute Resolution Provider on its website.
- 12.6.5 Implementation of a Lock and the Decision
If an Arbitrator’s decision requires a change to the status of a registered domain name, the Registry3 will wait ten (10) business days after communication of the decision before implementing that decision, unless the Registrant submits to the Registry (with a copy to the Dispute Resolution Provider) during that ten (10) day period official documentation (such as a copy of a complaint, file-stamped by the clerk of the court) that the Registrant has commenced a lawsuit to preserve its claimed rights in a court of competent jurisdiction over the parties and the registered domain name. If such documentation is received no further action shall be taken until the Registry receives (i) evidence satisfactory to the Registry of an agreed resolution between the parties; (ii) evidence satisfactory to Registry that Registrant’s lawsuit has been dismissed or withdrawn; or (iii) a copy of an order from such court dismissing such lawsuit or otherwise directing disposition of the registered domain name.
- 12.6.6 Representations and Warranties
Parties to a dispute under this SDRP shall warrant that all factual allegations made in the course thereof are true and correct to the best of their knowledge, shall remain subject to all representations and warranties made in the course of registration of a disputed domain name.
Maintaining the Status Quo
During a proceeding under the SDRP, the registered domain name shall be locked against transfers between Registrants and/or Registrars and against deletion by Registrants.
Indemnification / Hold Harmless
The parties shall hold the Registrar, the Registry, the Dispute Resolution Provider, and the Arbitrator harmless from any claim arising from operation of the SDRP. Neither party may name the Registrar, the Registry, the Dispute Resolution Provider, or the Arbitrator as a party or otherwise include the Registrar, the Registry, the Dispute Resolution Provider, or the Arbitrator in any judicial proceeding relating to the dispute or the administration of the SDRP policy. The parties shall indemnify, defend and hold harmless the Registrar, the Registry, the Dispute Resolution Provider, the Arbitrator and their respective employees, contractors, agents and service providers from any claim arising from the conduct or result of a proceeding under this
3 A Registry may, though its agreement with Registrars, instead require the Registrar to perform the lock and implementation steps.
SDRP. Neither the Registrar, the Registry, Dispute Resolution Provider, the Arbitrator nor their respective employees, contractors, agents and service providers shall be liable to a party for any act or omission in connection with any administrative proceeding under this SDRP or the corresponding rules. The complainant shall be directly and solely liable to the Registrant in the event the complaint is granted in circumstances where the Registrant is lawfully entitled to registration and use of the registered domain name(s) in the TLD.
Relation to Other Dispute Resolution Policies
This SDRP is in addition to and complementary with the Uniform Domain Name Dispute Resolution Policy (“UDRP”), the Uniform Rapid Suspension System (“URS”) and any charter, nexus, or eligibility dispute policies adopted by ICANN or the Registry.
Effect of Other Proceedings
The administrative proceeding under the SDRP shall not prevent either party from submitting a dispute concerning the registered domain name in the TLD to concurrent administrative proceedings or to a court of competent jurisdiction for independent resolution during a pending SDRP administrative proceeding or after such proceeding is concluded. Upon notice of such other proceeding, the SDRP proceeding may be terminated or put on hold (in the sole discretion of the Arbitrator) in deference to the outcome of such other proceeding.
The Registry reserves the right to modify this SDRP at any time. Such revised SDRP shall be posted on the Registry Website at least thirty (30) calendar days before it becomes effective; unless this SDRP has already been invoked by the submission of a complaint, in which event the version of the SDRP in effect at the time it was invoked will apply until the dispute is concluded. In the event that Registrant objects to a change in this SDRP, the sole remedy is to cancel the registration, provided that Registrant will not be entitled to a refund of any fees paid in connection with such registration.
The Registry having considered the applicable laws on data protection principles, which have guided the development of this policy:
- 13.1.1 Personal data shall be processed fairly and lawfully.
- 13.1.2 Personal data shall be obtained only for one or more specified and lawful purposes, and shall not be further
processed in any manner incompatible with that purpose or those purposes.
- 13.1.3 Personal data shall be adequate, relevant and not excessive in relation to the purpose or purposes for which
they are processed.
- 13.1.4 Personal data shall be accurate and, where necessary, kept up to date.
- 13.1.5 Personal data processed for any purpose or purposes shall not be kept for longer than is necessary for that
purpose or those purposes.
- 13.1.6 Appropriate technical and organisational measures shall be taken against unauthorised or unlawful processing
of personal data and against accidental loss or destruction of, or damage to, personal data.
Relationship with Registrars
- 13.2.1 Domain names are distributed through Registrars, accredited by ICANN, and who have entered into a Registry Registrar Agreement (“RRA”) with the Registry. Registrars register domain names on behalf of their customers, and typically provide additional services (such as web hosting, email, and SSL certificates). Registrars have broad powers to register, delete, and modify the domain names that are registered for their customers, and use a variety of automated and manual tools to do so.
- 13.2.2 The RRA with Registrars requires that they ensure that their connection to the Registry system is secure, and that all data exchanged between the Registrar’s system and the Registry system is protected. However, the Registry cannot ensure or guarantee the security of Registrars’ systems. Registrants should contact their Registrar if they have any questions or concerns about how the Registrar processes, stores and transmits their personal information.
What information the Registry collects
All domain names registered in the .fans database have to be associated with the following information:
188.8.131.52 Registered Name Holder (or Registrant): the legal owner of the domain name.
184.108.40.206 Administrative Contact: the entity authorized by the Registrant to interact with the Registrar on behalf of the Registrant.
220.127.116.11 Technical Contact: the entity authorized by the Registrant to maintain the technical operations of the domain name.
18.104.22.168 Sponsoring Registrar: The entity authorized by the Registrant to register and manage the domain.
22.214.171.124 Name servers: the domain name servers to which the domain must be delegated in order to function.
- 13.3.2 The following information may also be provided:
126.96.36.199 Billing Contact: the entity authorized by the Registrant that is responsible for payment of registration and renewal fees to the registrar.
188.8.131.52 DNSSEC DS records: digests of the DNSSEC Secure Entry Point (SEP) for the domain name.
- 13.3.3 The Registrant and the Administrative, Technical and Billing Contacts described above include the following information:
- Contact Name/Role
- Street Address
- Post Code
- 13.3.4 The Registrar provides this information to the Registry when the domain is registered. Registrars can also amend the above information at any time during the lifetime of the domain registration. The Registrar does not share with the Registry the Registrant’s methods of payment or such other information about services a Registrant may have with a given Registrar. At the point of registration, the Registry also stores the following information:
- The creation date of the domain,
- The expiry date of the domain,
- Status codes used to lock the domain, prohibit updates, etc.,
- A random authorisation code used for transfers.
Information the Registry does not collect
Because the Registry does not directly interact with Registrants, the Registry does not receive or store any of the following information:
How information is stored
- The IP address of the registrar’s customer,
- Any credit card information,
- Any passwords used by the Registrant to access the registrar’s
Domain name registration information is stored in a central database. This database is hosted in a secure colocation facility and is protected by enterprise-grade firewalls. The Registry takes regular backups of the database to ensure continuity of service. All backups are stored in an encrypted format and are transmitted to off-site locations using encrypted communications channels to prevent unauthorized access.
How information is used
As a domain name Registry, we use this information in the following ways:
- 13.6.1 We use the domain name, name servers, and DNSSEC DS records (if any) to publish DNS zone files to facilitate the functioning of the domains. This information can be queried through our public DNS servers. Third parties can also access copies of the zone files after signing an agreement.
- 13.6.2 The Registrant, Administrative, Technical and Billing Contact information is published via our Whois service. The Whois system is a standard service operated by all domain name registries and Regional Internet Registries (RIRs) and is used by third parties to obtain information about registered domain names, and has a variety of uses, including:
Supporting the security and stability of the Internet by providing contact points for network operators and administrators, including ISPs, and certified computer incident response teams; Determining the registration status of domain names;
Assisting law enforcement authorities in investigations for enforcing national and international laws;
Assisting in combating abusive uses of information communication technology;
Facilitating inquiries and subsequent steps to conduct trademark research and to help counter intellectual property infringement;
Contributing to user confidence in the Internet by helping users identify persons or entities responsible for content and services online; and
Assisting businesses, other organizations and users in combating fraud, complying with relevant laws and safeguarding the interests of the public.
13.6.3 The Registry uses the Registrant, Administrative, Technical and Billing Contact information to contact the appropriate entities when dealing with the following issues, without limitation:
184.108.40.206 220.127.116.11 18.104.22.168
Non-payment of registration or renewal fees by the Registrar4
Misdirected SSL certificate requests
Complaints of trademark or copyright infringement, malware, fraud or spam
An example of a typical Whois record appears below.
Domain Name: NIC.FANS
Domain ID: D1465606-CNIC
WHOIS Server: whois.centralnic.com
Referral URL: http://www.centralnic.com/
Updated Date: 2014-09-12T00:15:47.0Z
Creation Date: 2013-09-11T00:00:00.0Z
Registry Expiry Date: 2015-09-11T23:59:59.0Z
Sponsoring Registrar: CentralNic Ltd
Sponsoring Registrar IANA ID: 9999
Domain Status: ok
Registrant ID: C114321
Registrant Name: Domain Administrator
Registrant Organization: Asiamix Digital Ltd.
Registrant Street: Unit 15, 1/F, Block 2, Office Building, 96 Siena Avenue Registrant City: Discovery Bay North
Registrant Postal Code: N/A
Registrant Country: HK
Registrant Phone: +852.22536700
4 In most cases, this is not required, however the Registry reserves the right to send notifications in some circumstances.
Registrant Phone Ext:
Registrant Fax: +852.22536700
Registrant Fax Ext:
Registrant Email: email@example.com
Admin ID: C114321
Admin Name: Domain Administrator
Admin Organization: Asiamix Digital Ltd.
Admin Street: Unit 15, 1/F, Block 2, Office Building, 96 Siena Avenue Admin City: Discovery Bay North
Admin Postal Code: N/A
Admin Country: HK
Admin Phone: +852.22536700
Admin Phone Ext:
Admin Fax: +852.22536700
Admin Fax Ext:
Admin Email: firstname.lastname@example.org
Tech ID: C114321
Tech Name: Domain Administrator
Tech Organization: Asiamix Digital Ltd.
Tech Street: Unit 15, 1/F, Block 2, Office Building, 96 Siena Avenue Tech City: Discovery Bay North
Tech Postal Code: N/A
Tech Country: HK
Tech Phone: +852.22536700
Tech Phone Ext:
Tech Fax: +852.22536700
Tech Fax Ext:
Tech Email: email@example.com
Name Server: NS0.CENTRALNIC-DNS.COM
Name Server: NS1.CENTRALNIC-DNS.COM
Name Server: NS2.CENTRALNIC-DNS.COM
Name Server: NS3.CENTRALNIC-DNS.COM
Name Server: NS4.CENTRALNIC-DNS.COM
Name Server: NS5.CENTRALNIC-DNS.COM
Billing ID: C114321
Billing Name: Domain Administrator
Billing Organization: Asiamix Digital Ltd.
Billing Street: Unit 15, 1/F, Block 2, Office Building, 96 Siena Avenue Billing City: Discovery Bay North
Billing Postal Code: N/A
Billing Country: HK
Billing Phone: +852.22536700
Billing Phone Ext:
Billing Fax: +44.2033880601
Billing Fax Ext:
Billing Email: firstname.lastname@example.org
>>> Last update of WHOIS database: 2015-03-25T17:18:52.0Z <<<
How information is protected
All interfaces used to collect information (specifically, EPP and Toolkit systems, the web-based Registrar Console and the Registry website) use the Secure Sockets Layer (SSL) to encrypt information as it is transmitted to the Registry’s system. This is the same technology used to secure e-commerce systems and online banking. As described above, the database storing domain name registration data is hosted on a server in a secure colocation facility, protected by a firewall. When copied from this server, the database is always transmitted and stored using encryption technology.
How to get further information or ask a question
If a Registrant has any questions or comments about this policy, please contact: By email: email@example.com
14 Whois Access Policy
Dissemination of Domain Registration Information:
Asiamix Digital Ltd, the Registry for TLD .fans is required to collect and provide domain name registration information (“Whois Data”) for a variety of purposes. The Registry provides access to Whois Data through a standard text-based network protocol at whois.nic.fans, port 43. Whois Data can also be accessed on the Registry’s website using a standard web interface at whois.nic.fans (port 80).
Both interfaces are publicly available at no cost to the user and are reachable worldwide. This service is available to any Internet user and its use does not require prior authorization or permission.
Access to Whois Data in the Registry’s database is provided to assist in determining the contents of a domain name’s registration record. Whois Data consists not only of the domain name but also the relevant contact information associated with the domain name as provided by the Registrant. It also identifies nameserver delegation and the domain name’s registrar of record.
The data in this record is provided for informational purposes only; the Registry does not guarantee Whois Data accuracy. This service is intended only for query-based access. By submitting a Whois query to the Registry, you agree to abide by this Whois Access Policy (this “Policy”).
Please note that the Registry may modify this Policy from time to time in its sole discretion. Any modifications or amendments to this Policy shall be effective upon posting on the .fans Registry website and giving ninety (90) days prior written notice to all .fans Accredited Registrars.
Security and Stability Considerations:
Abuse of the Registry’s Whois interface through data mining may be mitigated by detecting and limiting bulk query access from single sources. Such queries by non-authorised parties will be
limited and unauthorised queries may result in responses that do not include data sets representing significant portions of the registration database. In addition, the Registry’s Whois web interface adds a simple challenge-response CAPTCHA that requires a user to type in the characters displayed in a certain image. The .fans Registry will employ a blacklist to block access to Whois Data by those found to violate this Policy or any .fans Registry policy. At .fans Registry’s sole and complete discretion, individual Internet protocol (“IP”) addresses or IP ranges may be prevented from accessing Whois Data.
By accessing Whois Data from the Registry, you agree that you will use the Whois Data only for lawful purposes and that under no circumstances will you use the Whois Data to:
- 14.3.1 allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to any entities (other than your existing customers from whom you collected such information with their knowledge and permission);
- 14.3.2 enable high volume, automated, electronic processes that send queries or data to the systems of the Registry, its registry service provider or any ICANN-accredited Registrar, except as reasonably necessary to register domain names or modify existing registrations; or
- 14.3.3 collect or attempt to collect the majority or entirety of the Whois database contents.
- 14.3.4 Users who collect Whois Data by any of the above purposes are prohibited from publishing such Whois Data.
When using the Registry’s Whois service, consider the following:
- The Whois Service is not a replacement for standard EPP commands;
- Whois Data is not considered authoritative for registered domain objects;
- The Whois service may be scheduled for downtime during production or operation, testing and evaluation maintenance periods; and,
- Queries to the Whois service may be “throttled” (i.e. if too many queries are received from a single IP address within a specified time, the service will begin to reject further queries for a period of time to prevent disruption of Whois service access).
- Information regarding the .fans Registry’s searchable Whois service is available on its website at www.nic.fans.
In this document:
“Accredited Registrar” or “Registrar” means a domain name registrar that is (i) accredited by ICANN and (ii) has entered into a Registry-Registrar Agreement with the Registry.
“Allocation” means the method by which a domain name is created and assigned to an Applicant; “Allocated” shall have a corresponding meaning.
“Applicant” means a natural person, company or organisation in whose name an Application is submitted.
“Application” means the complete and technically correct request for a domain name, which complies with this policy and any other policy issued by us, or ICANN.
“Available Names” means .fans names that have not been reserved, restricted, protected, registered, awarded, or otherwise allocated.
“CentralNic Registrar Console” means the console provided by CentralNic available at https://registrar-console.centralnic.com.
“Claims Notice “means a notice provided to an Applicant indicating that the applied for label is a Trademark Match to a Trademark Record in the Trademark Clearinghouse.
“Claims Period” means any period during which the Claims Services are provided.
“Claims Services” means the services that collectively provide:
- Applicants with a Claims Notice, and
- Trademark Holders, with a corresponding Trademark Record, with notice that a label
that is a Trademark Match to the Trademark Record is Allocated.
“Content” means any web, e-mail or other content associated with a domain name in the .fans TLD
“Dispute Resolution Provider” means the forum or provider of domain name disputes as appointed by the Registry which may include: WIPO, the National Arbitration Forum or other Arbitrator as designated by the Registry.
“General Availability” means the point in time following which requests to register a domain name may be received from any party on a first come, first served basis.
“ICANN” means the Internet Corporation for Assigned Names and Numbers, its successors and assigns.
“ICANN Requirements” means the Registry’s obligations under the Registry Agreement between Registry and ICANN and all ICANN Consensus Policies applicable to the .fans TLD.
“Protected Names” means the mechanism by which the Registry may reserve certain names in order to extend additional rights protection for certain categories of Applicants.
“Registrant” is an Applicant that has submitted a Registration Request that has been paid for in full and accepted by the Registry. A Registrant is the holder of a registered name in the .fans TLD.
“Registration” means a .fans name that has been accepted by the Registry in accordance with the terms of the Registry-Registrar Agreement and the Registration Agreement for registration during a specified term.
“Registration Agreement” means the agreement between Registrant and Accredited Registrar for registration of the domain name.
“Registration Request” is an application submitted by an Accredited Registrar on behalf of an Applicant to register a name in the .fans TLD.
“Registrar” means an entity that is authorised to offer domain name registration services in relation to the TLD.
“Registry” is Asiamix Digital Limited of Unit 15, 1/F, Block 2, Office Building, 96 Siena Avenue, Discovery Bay North, Hong Kong.
“Registry Policies” means the policies adopted from time to time by the Registry as posted under Policies on the Registry Website.
“Registry-Registrar Agreement” or “RRA” is the agreement between Registry and Accredited Registrars, as amended from time to time.
“Registry System” means the system operated by Registry or Registered Names in the .fans TLD.
“Registry Website” is www.nic.fans and www.dotfans.net
“SMD File” means the Signed Mark Data file provided by the TMCH Sunrise and Claims Operator to a holder of a Validated Mark which is encoded with information such as the labels that may be Allocated during a Sunrise Period.
“Sunrise Registration” means a domain name Allocated to a Sunrise-Eligible Rights Holder and applied for during the Sunrise Period.
“TLD” means Top Level Domain and for the purpose of this policy the TLD shall be .fans.
“TMCH Sunrise and Claims Operator” means the providers appointed by ICANN to serve as the Trademark Clearinghouse by accepting, authenticating, validating and facilitating the transmission of information related to certain trademarks.
“Trademark Clearinghouse” means the central repository for information to be authenticated, stored, and disseminated, pertaining to the rights of Trademark Holders. Trademark Holder means holders of marks that have been verified by the TMCH Sunrise and Claims Operator as meeting the requirements specified in the Trademark Clearinghouse Guidelines.
“Trademark Clearinghouse Guidelines” means the guidelines which can be found at the following link http://www.trademark-clearinghouse.com (as may be updated from time to time) which provide an overview of the requirements for the inclusion of trademarks in the Trademark Clearinghouse and the issuance of a SMD File.
“Trademark Holders” are those eligible trademark owners who have been issued with a SMD File from the TMCH Sunrise and Claims Operator and meet the eligibility requirements specified in the Trademark Sunrise Policy.
“Trademark Match” means that a label is a match to a trademark, as described in the Trademark Clearinghouse Guidelines.
“Trademark Record” means a complete and correct set of information concerning a trademark or other mark submitted to the Trademark Clearinghouse.
“Trademark Sunrise” means the period during which Sunrise- eligible Trademark Holders have the opportunity to submit an Application for a domain name in the TLD prior to the General Availability phase.
“Validated Mark” means a mark that has been verified by the TMCH Sunrise and Claims Operation as meeting the requirements specified in the Trademark Clearinghouse Guidelines including those relating to proof of use.