Changes

Jump to: navigation, search

.xxx

8,904 bytes added, 3 years ago
Grafted GAC advice from GAC article.
[[Image:UnderConstruction.png]]
{{TLD|
|logo = Xxx.JPG‎
|manager =
|country = International
|stringcontention =
|registryprovider = ICM Registry
}}
'''.xxx''' is one of the a [[sTLD|sponsored top-level domain name ]] ([[sTLD]]) delegated in the [[Root Zone|root zone]] of the internet 's [[DNS|Domain Name System ]] ([[DNS]]). The TLD is intended for the "online adult-entertainment community." The [[IFFOR|International Foundation for Online Responsibility ]] ([[IFFOR]]) is the sponsoring organization and it is responsible in for creating and overseeing policies for the .xxx. IFFOR is a non-profit organization created by [[ICM Registry]], which serves as the registry operator of the domain.xxx. <ref>[http://iffor.org/about IFFOR-About Us]</ref>  The domain space was launched for public registration on December 6, 2011. There were more than 100,000 domain names pre-registered.<ref>[http://www.sfgate.com/cgi-bin/article.cgi?f=/g/a/2011/12/05/businessinsiderofficial-porn-domain.DTL Over 100,000 XXX Domain Names Are Going Live Tomorrow At 11 EST]</ref>
==History==
===.xxx Application during the 2000 ICANN Proof of Concept===
[[ICM Registry]] proposed the .xxx as non-sponsored [[gTLD|generic top-level domain name ]] ([[gTLD]]) during the ICANN Proof of Concept round in 2000. ICANN's evaluation team did not recommend the string because of the "controversy surrounding it and the poor
 definition 
of 
the
 hope for 
benefits
 of .xxx." On December 15, 2000, ICM Registry filed a Reconsideration Request with ICANN but no action was rendered. The [[ICANN Board ]] cited that "no new TLD proposals proposal has been rejected , rather a small set of potentially successful applicants had been selected with the aim of testing a diversity of approaches to the creation of new TLDs."
<ref>[http://cyber.law.harvard.edu/pubrelease/icann/pdfs/AppendixD_xxx.pdf Accountability
 and
 Transparency 
at ICANN
: An
 Independent
 Review]</ref>
===GAC Advice on the .xxx sTLD===
On March 17, 2011, the GAC, via its Chairman [[Heather Dryden]], reiterated to ICANN Chairman [[Peter Dengate Thrush]] that the Committee has no active support for the implementation of the [[.xxx]] [[sTLD]]. The GAC also informed ICANN that some governments might prevent access to the TLD, which could harm the global interoperability and stability of the internet. Furthermore, the Committee also pointed out the possibility that ICANN may have to assume a management and oversight role regarding .xxx content.<ref>[http://news.dot-nxt.com/2011/03/17/gac-statement-dot-xxx GAC Statement on .xxx]</ref> Despite GAC's position, the [[ICANN Board]] approved the .xxx sTLD during the [[ICANN 41]] Meeting in San Francisco, on March 18, 2011.<ref>[http://news.dot-nxt.com/2011/04/03/summary-icann-san-francisco#xxx Conference summary: ICANN San Francisco]</ref> The disregard for the GAC's advice in this instance provided for a number of other international entities to question ICANN's ability to successfully manage the [[DNS]].
===.xxx during the 2003 sTLD Application Process===
On December 15, 2003, the ICANN Board published a Request For Proposal (RFP) for new [[sTLD]]s after extensive discussions within the different stakeholders within the ICANN community. [[ICM Registry]] submitted a proposal for.xxx on March 16 2004. IFFOR was named as the sponsoring organization, responsible for developing policies for the proposed TLD. In August, 2004, the [[IRP|Independent Review Panel]] evaluated ICM's application and reported to the [[ICANN Board]] that the the company failed to meet the baseline sponsorship criteria for a [[sTLD]].<ref>[http://www.iana.org/reports/2011/xxx-report-20110407.pdf Delegation of the .XXX top-level domain]</ref> Following the report, the ICANN Board approved a resolution allowing sTLD applicants to add additional information to resolve the concerns raised by IRP in the report. In October, 2004, ICM Registry started submitting additional documents to strengthen its application. ICM Registry was invited to make a presentation on April 3, 2005.<ref>[http://archive.icann.org/en/tlds/stld-apps-19mar04/stld-status-report.pdf Status Report on the sTLD Evaluation Process]</ref>
 
Following the presentation, a special meeting was conducted by the [[ICANN Board]] on May 3, 2005, where it discussed whether the sponsored community baseline criteria was met or not by ICM Registry. The Board decided to further discuss the issue at another meeting.<ref>[http://www.icann.org/en/groups/board/documents/minutes-03may05-en.htm Minutes-Special Meeting of the Board May 3, 2005]</ref>
 
On June 1, 2005, the ICANN Board charged [[ICANN CEO]] [[Paul Twomey]] and General Counsel [[Jon Jeffrey]] to negotiate the proposed commercial and technical terms for a contractual agreement in connection with the delegation of the [[.xxx]] sTLD.<ref>[http://www.icann.org/en/groups/board/documents/minutes-01jun05-en.htm Minutes Special Meeting of the Board, June 1, 2005]</ref>
 
On September 5, 2005, the proposed contractual agreement for .xxx sTLD was submitted to the ICANN Board for approval. It was also posted on ICANN's website. A significant number of comments and inquiries from the Internet community were received by the Board relating to the contract. The Board directed the ICANN CEO and the General Counsel to discuss the possible additional contractual provisions or modifications for the .xxx Registry Agreemet to ensure the development and implementation of policies consistent with the principles of ICM Registry application.<ref>[https://community.icann.org/display/tap/2005-09-15+-+Review+of+Proposed+.XXX+Sponsored+Top-Level+Domain+Registry+Agreement 2005-09-15 - Review of Proposed .XXX Sponsored Top-Level Domain Registry Agreement]</ref>
 
Several revisions were submitted and negotiations were made on the .xxx Registry Agreement between September 15, 2005 until January 5, 2007. Extensive comments and advice were also received from the global internet community and from the [[GAC|Governmental Advisory Committee]], which were evaluated by the ICANN Board. On March 30, 2007, the ICANN Board denied the ICM Registry application citing that the company failed to meet the Sponsored Community criteria set forth in the RFP, issues raised by GAC such as offensive content and protection of vulnerable members of the community were not properly adressed, the application raised significant law enforcement issues in different countries, and the application posed a possibility that ICANN might be forced to assume an ongoing management and oversight role regarding Internet content, which is inconsistent with its technical mandate.<ref>[http://www.icann.org/en/groups/board/documents/resolutions-30mar07-en.htm#_Toc36876524 Adopted Resolutions from ICANN Board Meeting, 30 March 2007]</ref>
===.xxx during the 2003 sTLD Application ProcessIndependent Review Proceedings=== On December 15, 2003, ICM Registry contested the ICANN Board published a Request For Proposal (RFP) for new sTLDs after conducting public comments resoultion and extensive discussions within the different stakeholders within the ICANN community. ICM Registry submitted a proposal request for.xxx on March 16 2004. IFFOR was named as the sponsoring organization, which will be responsible in developing policies for the proposed TLD. On August 2004, the [[IRP|Independent Review Panel]] evaluated ICMproceeding on June 6, 2008. Entities may request for an IRP to resolve their claims that the ICANN Board acted in a manner inconsistent with the organization's application Articles of Incorporation. The IRP is a final appeal to ensure transparency; and reported due to this, ICM Registry was the first entity to utilize this provision in the [[history of ICANN Board]] . ICM complained that ICANN exceeded its mandate during the evaluation process and violated the company failed to meet its Articles of Incorporation and Bylaws. ICM claimed that the Internet governing body improperly administered the baseline sponsorship criteria 2003 RFP process for sTLDsTLDs and its decision lacks transparency and is discriminatory.<ref>[http://www.ianaicann.org/reportsen/news/2011irp/xxxicm-reportv-20110407.pdf Delegation of the .XXX top-level domainicann ICM's Request for Independent Review Process]</ref> Following  ICANN responded on Septemebr 8, 2008 and argued that ICM's allegations were false. The organization pointed out that its evaluation of ICM's application were more open and transparent, and that the reportnegotiations conducted on June 1, 2005 were not binding and di not assure approval of the Registry agreement. ICANN Board approved a resolution allowing sTLD applicants tried to additional information work closely with ICM to resolve the concerns raised by IRP problems in the report. On October 2004application, however, ICM Registry started submitting additional documents to strengthen its applicationthe ICANN Board believed that the underlying problems would not be resolved by awarding a contract. ICM Registry ICANN strongly emphasized that the decision was invited to make a presentation on April 3, 2005made in good faith.<ref>[http://archivewww.icann.org/en/tldsnews/stld-apps-19mar04irp/stldicm-statusv-report.pdf Status Report on the sTLD Evaluation Processicann ICANN's Response to ICM's IRP Request]</ref>
Following Both parties submitted their briefing papers and testimonies to the presentation, a special meeting three-member IRP which was conducted handled by the ICANN Board on May 3[[ICDR|International Centre for Dispute Resolution]] of the [[American Arbitration Association]]. On February 19, 2010, 2005 and discussed whether the sponsored community baseline IRP ruled in favor of ICM. Two of the panelist agreed that ICM met the criteria for sponsorship citing that, "the Board’s reconsideration of that finding was met or not by ICM Registryconsistent with the application of neutral, objective and fair documented policy. " The Board decided to further discuss opinion of the other panelist was contrary. He said that ICM did not meet the issue on another meetingsTLD sponsorship requirements and ICANN carried out its decision with transparency. <ref>[http://www.icann.org/en/groups/boardnews/documentsirp/minutesicm-03may05v-en.htm Minutes-Special Meeting icann Independent Review Panel Declaration]</ref> Moreover, the declaration of the IRP is not a binding order rather an advisory or recommendation for the ICANN Board May to consider as stated on Article IV Section 3(15) of the ICANN Bylaws stating that, "Where feasible, 2005the Board shall consider the IRP declaration at the Board's next meeting."<ref>[http://www.icann.org/en/about/governance/bylaws#IV ICANN Bylaws]</ref>
On June 1March 12, 20052010, the ICANN Board considered the IRP declaration and tasked ICANN President [[Paul Twomey]] CEO and General Counsel to develop a final report for possible process options to be posted on the website.<ref>[[Jon Jeffrey]http://www.icann.org/en/groups/board/documents/resolutions-12mar10-en.htm#15 Adopted Board Resolutions, Nairobi, March 12, 2010] </ref> The ICANN Board received and evaluated 13,700 comments regarding the process options. On June 25, 2010, the ICANN Board to accept the majority recommendation of the IRP and directed the ICANN Staff to negotiate ensure that the proposed commercial ICM application is still current and technical terms for no changes have been made to the company's qualifications. In addition, the ICANN Staff were also authorized to develop a contractual agreement in connection contract with ICM to be reviewed by the delegation Board to ensure that it is consistent with [[GAC]]'s advice, if not, consultation with GAC will be done prior to approval of the contract.<ref>[http://www.icann.xxx sTLDorg/en/groups/board/documents/resolutions-25jun10-en.htm#5 Adopted Board Resolutions | Brussels]</ref> On August 5, 2010, the proposed [[Registry Agreement]] was posted for public comments.<ref>[http://www.icann.org/en/groups/board/documents/minutesresolutions-01jun0505aug10-en.htm Minutes Special Meeting #9 Adopted Board Resolutions]</ref>ICANN's chairman initiated a consultation process with GAC Chair regarding the proposed ICM Registry Agreement. Prior to the schedule personal consultation, the GAC sent a letter to ICANN stating that it has no active support for the introduction of the Board.xxx string and governments might take actions to prohibit internet access to the TLD, June 1, 2005which is a threat to the universal stability of the DNS.<ref>[http://www.icann.org/en/groups/.../draft-icm-rationale-18mar11-en.pdf Draft Rationale for Approving ICM Registry Agreement]</ref>
On September 5During the [[ICANN 40]] meeting in San Francisco in March, 20052011, the proposed contractual agreement for .xxx sTLD was submitted to the ICANN Board for approvalapproved the ICM application.<ref>[http://www.above. It was also posted on ICANN's websitecom/blog/2011/03/xxx-approved-at-icann-40. Significant number of comments, correspondences and inquiries from the internet and community were received by the Board relating to the contracthtml . XXX Approved at ICANN 40]</ref> The Board directed the ICANN President and the General Counsel to discuss the possible additional contractual provisions or modifications for the .xxx Registry Agreemet string was delegated to ensure the development and implementation [[Root Zone|root zone]] of policies consistent with the principles of ICM Registry application[[DNS]] in June, 2011.<ref>[httpshttp://communitywww.icanncomputerworld.orgcom/s/displayarticle/tap9178518/2005-09-15+ICANN_board_approves_dot_XXX_top_level_domain_for_porn?taxonomyId=18&pageNumber=2 ICANN board approves dot-+Review+of+Proposed+.XXX+Sponsored+Toptop-Level+Domain+Registry+Agreement 2005-09-15 - Review of Proposed .XXX Sponsored Top-Level Domain Registry Agreementlevel domain for porn]</ref>
Several revisions were submitted and negotiations were made on ==.xxx Policies==The sponsoring community of the .xxx Registry Agreement between September 15includes individuals, companies, 2005 until January 5organizations, 2007providers of adult entertainment. Extensive comments and advice were also received from global internet community and from the [[Government Advisory Council|GAC]]Some of these entities include adult website administrators, club owners, performers, which were evaluated by the ICANN Board. On March 30agents, 2007lawyers, the ICANN Board denied the ICM Registry application citing that the company failed to meet the Sponsored Community criteria set forth distributors and manufacturers or adult products. All entities interested in the RFP, the registering a .xxx sTLD raised public policy, approval domain need to become a member of the Registry Agreement will not resolve the issue raised by GAC such as offensive content and protection of vulnerable members community. Individuals must provide correct date of birth, address, phone number, confirm membership to the community, the application raises significant law enforcement issues in different countries and accept the application poses a possibility that ICANN might be forced to assume an ongoing management and oversight role regarding Internet content, which is inconsistent with its technical mandateRegistry-Registrant Agreement.<ref>[http://www.icannicmregistry.orgcom/enabout/groupssponsored-community/board/documents/resolutions-30mar07-en.htm#_Toc36876524 Adopted Resolutions from ICANN Board Meeting, 30 March 2007Who Qualifies for the Sponsored Community]</ref>
==Independent Review Proceedings==ICM Registry contested the resolution of the Board and submitted a request for The [[IRP|Independent Review PanelIFFOR]] proceeding on June 6, 2008.Entities may request for an IRP implements policies to resolve allegations that the ICANN Board acted or decided inconsistent comply with the organizations Articles of Incorporation. The IRP is a final appeal its agreements; to ensure transparency and since protect the establishment of ICANNprivacy, ICM Registry was the first entity to utilize this provision. ICM complained that ICANN exceeded its mission during the evaluation process security and violated the its Articles consumer rights of Incorporation consenting adults; to help user choice and Bylaws. The internet governing body improperly administered the 2003 RFP process for sTLD parental control with regards to access to online adult content; and its decision lacks transparency and discriminatory. In addition, the company alleged that ICANN to fight child abuse images. Its' baseline policies include:<ref>[http://www.icannicmregistry.org/encom/newspolicies/irpiffor/icm-v-icann ICM's Request for Independent Review ProcessIFFOR Baseline Policies]</ref>* Registration is restricted to the sponsoring community* The organization implements eligibility verification processes with all registrants interested in becoming a member of the sponsoring community* Reasonable Technological Mechanisms will be used to authenticate the identity of registrants* Registrants must agree to the labeling requirements as all .xxx sites use an IFFOR aproved label* Child abuse images and conduct are prohibited, including content designed to suggest the availability of child abuse images* Registrants must agree to automated scanning of their sites to ensure compliance of IFFOR policies; using technology to prevent scanning is prohibited* Abusive registration ([[Intellectual Property]] rights and Trademarks infringements) is not allowed* Malicious Conduct is prohibited such as email spoofing, [[phishing]], spamming, and other illegal cyber activities.* Registrants must comply with the IFFOR Best Practices Guidelines.* All registrants violating the IFFOR policies will be disqualified. Violators of the prohibitions on child abuse images and the implementation of automated scanning will be referred to third parties such as law enforcement agencies, hotlines, etc.
ICANN Responded on Septemebr 8, 2008 and argued that ICM===Dispute Resolution Programs===The '''Rapid Evaluation Service (RES)'s allegations are false. The internet governing body pointed out that ICANN's evaluation on ICM's application was more open and transparent, introduced by the negotiations conducted on June 1[[National Arbitration Forum]] (FORUM), 2005 was not binding to assure approval serve as dispute resolution program to protect the stage names of the Registry agreementadult entertainers and performers from infringements. ICANN tried to work closely with ICM to resolve the problems Complaints filed under RES in proper circumstances will be handled within two business days and the application however, the ICANN Board believed that the underlying problems infringing domain names will not be resolved taken down. The '''Charter Eligibility Dispute Resolution Policy (CEDRP)''' of ICM is also handled by awarding a contractFORUM. ICANN strongly emphasized that Entities may file complaints and challenge the decision was made in good faith to deny ICM's applicationownership eligibility of entities for .xxx domain names.<ref>[http://www.icannicmregistry.orgcom/enpress/news/irp/icmnational-arbitration-forum-launches-dispute-program-for-xxx-vdomain-icann ICANN's Response to ICM's IRP Requestnames/ National Arbitration Forum Launches Dispute Program for .XXX Domain Names]</ref>
Both parties submitted their briefing papers and testimonies to the three-member IRP which was handled by the [[ICDR|International Centre for Dispute Resolution]] ==Domain Statistics==As of the [[American Arbitration Association|AAA]]June 2, 2013, . On February 19xxx had 122,000 active registrations, 2010after a peak at 142, the IRP ruled 000 in favor of ICMDecember 2012. Two of the panelist agreed that During May 2013, [[ICM met Registry]] cut the criteria prices for sponsorship citing that.xxx names down to .com-level prices, "the Board’s reconsideration of that finding was not consistent with the application of neutral, objective and fair documented policy." The opinion resulting in a large number of the other panelist was contrary. He said registrations during that ICM did not meet the sTLD sponsorship requirements and ICANN carried out its decision with transparencymonth.<ref>[http://www.icanndomainincite.org/en/news/irpcom/13245-icm-vprice-icann Independent Review Panel Declaration]</ref> Moreovercut-sees-10-times-more-xxx-sales ICM Price Cut sees 10 times more xxx sales, the declaration of the IRP is not a binding order rather an advisory or recommendation for the ICANN Board to consider as stated on Article IV Section 3(15) of the ICANN Bylaws stating that, "Where feasible, the Board shall consider the IRP declaration at the Board's next meeting."<ref>[http://www.icann.org/en/about/governance/bylaws#IV ICANN BylawsDomain Incite]Retrieved 19 Sept 2013</ref>
On March 12, 2010, ICANN Board considered the IRP declaration and delegated the ICANN CEO and General Counsel to develop a final report for possible process options to be posted on The following are the websitetop 10 .xxx registrars as of February 2012:<ref>[http://wwwdomainnamewire.icann.orgcom/en2012/groups06/board07/documents/resolutionsxxx-12mar10up-en.htm#15 Adopted Board Resolutions, Nairobi, March 12, 2010]</ref> The ICANN Board received and evaluated 13,700 comments regarding the process options. On June 25, 2010, the ICANN Board to accept the majority recommendation of the IRP and directed the ICANN Staff to ensure that the ICM application is still current -137k-active-registrations-220k-total-and no changes have been made to the company's qualifications.In addition, the ICANN Staff was also authorized to develop a contract with ICM to be reviewed by the Board to ensure that it is consistent with GAC's advice, if not, consultation with GAC will be done prior to approval of the contract.<ref>[http://www.icann.org/en/groups/board/documents/resolutions-25jun10new-en.htm#5 Adopted Board Resolutions | Brussels]</ref> On August 5, 2010, the proposed Registry Agreement was posted for public comments.<ref>[http://www.icann.org/en/groups/board/documents/resolutions630k-05aug10premium-en.htm#9 Adopted Board Resolutions]<sale/ref>ICANN's chairman initiated a consultation process with GAC Chair regarding the proposed ICM Registry Agreement.Prior XXX up to the schedule personal consultation137k active registrations, 220k total, GAC sent a letter to ICANN stating that it has no active support for the introduction of the .xxx string and governments might take actions to prohibit internet access to the TLDnew $630k premium sale, which is a threat to the universal stability of the DNS.<ref>[http://www.icann.org/en/groups/.../draft-icm-rationale-18mar11-en.pdf Draft Rationale for Approving ICM Registry Agreementdomainnamewire]</ref>
During the # [[ICANN 40Go Daddy]] meeting in San Francisco on March 2011- 36,111 ([[Wild West Domains]], [[Blue Razor]])# [[Network Solutions]] - 16, the ICANN Board approved the ICM application 633# [http://www.above[Instra]] - 4,636# [[Name.com/blog/2011/03/xxx]] -approved4,272# [[eNom]] -at4,210# [[United Domains]] -icann3,820# [[Tucows]] -40.html .XXX Approved at ICANN 403,750# [[Ascio Technologies]]</ref> and .xxx was delegated to the - 3,645# [[root zonePublicDomainRegistry]] of the DNS on June.<ref>- 3,450# [[http://www.computerworld.com/s/article/9178518/ICANN_board_approves_dot_XXX_top_level_domain_for_porn?taxonomyId=18&pageNumber=2 ICANN board approves dotCSC]] -XXX top-level domain for porn]</ref>3,198
===Premium .xxx Sponsored CommunityDomain Names===The sponsored community ICM Registry sold several of the its premium .xxx include individuals, companies and organizations providers adult entertainmentdomain names for large sums, representatives of providers and products or service providersincluding gay. Some of these entities include adult web mastersxxx, club ownerswhich was purchased by Liberty Media Holdings (Corbin Fisher), performersa porn production company based in Las Vegas, agentsfor $500, lawyers000.<ref>[http://www.theregister.co.uk/2011/10/07/4500k_for_gay_dot_xxx_address/ Gay.xxx sells for $500, distributors and manufacturers or adult products000]</ref> Shemales. All entities interested xxx was sold for $200,000 to register a Grooby Productions.<ref>[http://www.thedomains.com/2011/10/17/shemales-xxx domain need to become a member of -sells-for-200000-3-12-times-more-than-the community-net-sold-for/ SheMales. Individuals must provide correct date XXX Sells For $200,000; 3 1/2 Times More Than The .Net Sold For]</ref> Meanwhile, [[Mike Berkens]], president of birth[[Worldwide Media]] invested six figures on three domain names: FreePorn.xxx, address, phone numberBlowJobs.xxx, confirm membership to the community and accept the Registry-Registrant AgreementAnalSex.xxx. <ref>[http://www.icmregistryelliotsblog.com/about/sponsoredmike-berkens-invests-in-xxx-domains-community0737 Mike Berkens Invests in .XXX Domains]</ Who Qualifies ref> [[Frank Schilling]], a domain name investor paid seven figures for the Sponsored Communityamateur.xxx, anal.xxx, asian.xxx, bollywood.xxx, book.xxx, celeb.xxx, chat.xxx, dating.xxx, hardcore.xxx, sexy.xxx, video.xxx, webcam.xxx and several other domain names.<ref>[http://www.elliotsblog.com/frank-schilling-took-risk-on-xxx-8017 Frank Schilling Spends Seven Figures on .XXX Domain Names]</ref>
==References=Free .xxx Domain Names==={{reflist}}As part of ICM's Adult Performer Program, the company partnered with domain name registrar [[Name.com]] in offering a one-year free domain name registration for 3,500 selected porn stars. The domain names were reserved by ICM and the $210,000 registry fee was paid in advance by Name.com.<ref>[http://domainincite.com/icm-offers-free-xxx-domains-to-porn-stars/ ICM offers free .xxx domains to porn stars]</ref>
===Suspended .xxx Domain Names===
Stuart Lawley, CEO of ICM confirmed that the company suspended the registration for several .xxx domain names due to unmistakable, blatant [[cybersquatting]]. The suspended domain names include businessweek.xxx, cnbc.xxx, geocities.xxx, nextag.xxx, snapfish.xxx, verizonwireless.xxx, washingtonpost.xxx and gayroom.xxx. Lawley emphasized and reiterated that his company is serious about implementing its policies and it is committed to maintaining high standards for its registry operations. He said, ''"We will not tolerate nefarious conduct and will exercise our right to take appropriate action when we detect widespread repeat patterns of cyber-squatting activity. Would-be cyber-squatters are on notice – neither ICM Registry nor the .xxx community will be complicit in the theft or abuse of intellectual property. ICM takes a stand to facilitate user choice and parental control, protect the privacy, security, and consumer rights of consenting adults, fight child abuse images, and protect intellectual property.”''<ref>[http://www.icmregistry.com/press/icm-registry-acts-in-response-to-reports-of-cyber-squatting/ ICM Registry Acts in Response to Reports of Cyber-squatting]</ref>
==ICM-Operated Sites==
===Search.xxx===
In September, 2012, the .xxx centric search engine at search.xxx was launched by ICM Registry. The search engine does not have a direct revenue model, but is instead a means of directing greater traffic to .xxx sites. Touted benefits of the search engine include: a pornographic focused search rather than a search that could result in non-pornographic sexual material, a safe and focused search for adults, the ability to search via sexual orientation, and not saving or recording searches to one's Google search history. The long-term goal is to increase the market-share of .xxx.<ref>[http://www.cnbc.com/id/49212131/ CNBC.com]</ref>
==Other==
===Russian iTunes Glitch===
On December 5th 2012, sections of the Russian iTunes store featured out of place banner ads and explicit content from ICM's registry internal search engine, xxx.xxx. Bloggers speculated than an Apple Web Developer may have entered the "xxx.xxx" as a placeholder not realizing that the URL would resolve as a live domain.<ref>[http://domainincite.com/11253-russian-itunes-store-infiltrated-by-xxx-banners-after-snafu-nsfw Russian iTunes Store Infiltrated by XXX Banners after Snafu, DomainIncite.com] Retrieved & Published 5 Dec 2012</ref>
==References==
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2">
{{reflist}}</div>
[[Category:TLD]]
[[Category:TLDs with Registry Agreements|xxx]]

Navigation menu