Back in the early days of the web, we were stuck with a modest handful of top‑level domains – the familiar .com, .net, .org and a few country codes like .co.uk or .us. Then the Internet Corporation for Assigned Names and Numbers (ICANN) opened the floodgates, letting anyone apply for custom TLDs, and suddenly hundreds of new extensions such as .hotel, .sucks, and the like appeared. This is the story of the top 10 top domains that have sparked the biggest controversies.
Why the Top 10 Top Domains Spark Controversy
1. .bible
In 2016, ICANN handed the .bible top‑level domain over to the American Bible Society (ABS). Since then, the organization has faced criticism for imposing strict controls that some say curb religious freedom online.
ABS decides who may register a .bible address and even supplies a rulebook outlining permissible content. While prohibiting material that disparages God or the Bible seems reasonable, some of the society’s mandates have raised eyebrows.
At one point, ABS barred any site that promoted beliefs outside Christianity or that diverged from the New Testament. After pushback from Jewish scholars, the policy was softened to forbid content that conflicted with the doctrines of Jews and Orthodox Christians.
The controversy deepened when ABS demanded that anyone arbitrating disputes over .bible names swear allegiance to the society’s mission and affirm that the Bible is the Word of God.
2. .su
.su was originally assigned to the Soviet Union in 1990, a year before the USSR dissolved into multiple independent states. The expectation was that the domain would disappear along with the union, much like .yu vanished after Yugoslavia split.
Instead, .su lingered and gradually turned into a haven for cyber‑criminals. Its lax oversight has attracted bot‑net operators, spammers, bank robbers, and groups launching DDoS and ransomware attacks, making it a digital Wild West.
Since Russia tightened .ru policies in 2011, roughly half of Russian malicious sites migrated to .su. Shutting down the entire TLD is impractical, and today it still hosts over 120,000 websites, many of which are perfectly legitimate.
3. .corp, .home, and .mail
In 2012, twenty companies each shelled out $185,000 to vie for the coveted .corp, .home, and .mail extensions. ICANN soon realized these three TLDs are typically reserved for internal networks and DNS testing, not public use.
If ever approved, browsers might inadvertently resolve private network addresses, opening the door to serious security threats and pranksters alike. After six years of deliberation, ICANN placed the three extensions on indefinite hold and refunded all bidders in full.
4. .africa
.africa was proposed in 2011 as a continent‑wide domain, but it quickly became embroiled in a dispute between Kenya’s DotConnectAfrica and South Africa’s ZA Central Registry (ZACR). Both entities applied for control in 2012.
ICANN required any applicant to secure backing from at least 60 % of African governments and the African Union (AU). Both registries claimed AU endorsement, but the AU initially backed DotConnectAfrica before switching its support to ZACR.
In 2014 ICANN awarded the .africa TLD to ZACR, prompting DotConnectAfrica to seek an injunction in a California court. The judge denied the request, allowing ICANN to move forward with ZACR’s delegation.
5. .sucks
The .sucks extension quickly earned a reputation for being a nightmare for brand owners, as attaching ‘.sucks’ to a name can invite angry customers or trolls to tarnish a company’s image.
When businesses tried to secure their own .sucks domains, the Canadian registry Vox Populi charged a steep $2,499 fee, with some resellers inflating the cost to $4,000—far above the typical $250‑$300 registration price for new TLDs.
Vox Populi’s aggressive stance escalated when it threatened to sell the domains to the public for $10 each, redirecting them to forums for complaints. After a wave of backlash, ICANN asked the U.S. FTC and Canada’s Office of Consumer Affairs to investigate, while giants like Apple, Google, Taylor Swift, and Oprah quietly snapped up their .sucks names.
6. .amazon
E‑commerce titan Amazon threw its hat into the ring for the .amazon TLD, sparking fierce opposition from a coalition of South American nations—Argentina, Brazil, Chile, Peru, and Uruguay—who argued the name should be reserved for the Amazon River itself.
These countries warned that granting the domain to a corporation could jeopardize river‑related conservation efforts, indigenous rights, and environmental agencies tasked with protecting the watershed.
The dispute even dragged the United States into the fray, with rumors that some South American governments, angry over granting asylum to Edward Snowden, were less inclined to support U.S. interests in the domain debate.
Ultimately, the U.S. stance was clear: ICANN would only approve geographic TLDs that aren’t listed in ISO 3166 and face no opposition. Since several nations objected, ICANN rejected Amazon’s application for .amazon.
7. .patagonia
Outdoor apparel brand Patagonia, Inc. sparked controversy when it pursued the .patagonia extension, prompting protests from Argentina and Chile, whose region shares the same name.
ICANN rules forbid bidding on geographic names that appear on the ISO 3166 list, which catalogs official country and subdivision codes to avoid linguistic confusion.
Since ‘Patagonia’ isn’t on the ISO 3166 roster, Patagonia, Inc. could technically claim the TLD, but after sensing little chance of approval, the company withdrew its application.
8. .gay and .lgbt
Saudi Arabia has publicly opposed the creation of a .gay TLD, claiming it could offend cultures and religions that disapprove of homosexuality. The stance attracted attention from gay advocacy groups, such as the Lesbian and Gay Foundation, which clarified that the domain would serve as a supportive space rather than a promotional platform.
The .lgbt extension, already live under registrar Afilias, allows businesses to signal LGBT‑friendliness by registering a .lgbt address.
However, the International Gay and Lesbian Travel Association warns that anti‑LGBT actors could masquerade as allies to snatch names, suggesting the community focus on the .gay TLD instead of .lgbt.
9. .catholic
ICANN is still debating the creation of a .catholic TLD, with the Vatican leading the charge and having already paid the $185,000 application fee.
Saudi Arabia opposes any TLD containing religious terminology, even those aligned with Islam, such as .islam, .halal, and .ummah.
Critics from the Islamic nation argue the Vatican’s ownership would be unfair to Eastern and Oriental Orthodox churches, whose members also identify as Catholics.
Beyond religious labels, Saudi Arabia also objects to .gay, .tattoo, .pub, .bar, .pornography, and .baby. The latter sees competition among three bidders, including Johnson & Johnson, which needs the TLD for its baby line, though Saudi suspects the other two aim to use it for adult content.
10. .xxx, .porn, and .adult
ICANN launched the .xxx extension in 2011, aiming to give pornographic sites a distinct namespace. The rollout triggered panic among non‑adult businesses and U.S. colleges, which rushed to secure .xxx names that could be linked to them before mischievous producers got creative.
Major brands such as Pepsi, Nike, and Target quickly claimed Pepsi.xxx, Nike.xxx, and Target.xxx. Google also snapped up Google.xxx, YouTube.xxx, Blogspot.xxx, and Picasa.xxx, while the Vatican ignored the extension, allowing a third party to register Vatican.xxx as soon as it opened.
Universities faced even steeper costs; the University of Kansas shelled out nearly $3,000 for dozens of .xxx domains like KUgirls.xxx and KUnurses.xxx. Some schools opted to monitor the space and sue porn producers who attempted to appropriate their names.
Beyond .xxx, the .porn and .adult extensions sparked similar battles. Institutions and brands—including Harvard, Microsoft, and Taylor Swift—grabbed .porn and .adult variants early on. Microsoft, for instance, secured Microsoft.porn, Microsoft.adult, Office.porn, and Office.adult.