A gTLD, generic Top-Level Domain, is a TLD that is not associated with a specific country or territory. Where ccTLDs are two-letter codes assigned to specific nations, .de for Germany, .fr for France, gTLDs are generic identifiers available for registration by anyone worldwide without geographic restriction. .com, .net, .org, .io, .app, .store, .supply: all gTLDs. They define the highest-level category of a domain name without implying any national affiliation.

The original gTLDs, established in the 1980s at the dawn of the commercial internet, were designed with specific intended audiences. .com for commercial entities. .net for network infrastructure. .org for non-profit organisations. .edu for educational institutions. .gov for government entities. .mil for military. .int for international organisations. These seven original gTLDs defined the early domain namespace and .com in particular became the dominant TLD for virtually all commercial websites regardless of whether they were strictly commercial entities.

Decades later ICANN’s new gTLD program, launched in 2012 and continuing to expand, introduced hundreds of additional generic TLDs. .app, .dev, .blog, .shop, .online, .tech, .agency, .design, .studio, .supply, and many others. This expansion dramatically increased the available TLD namespace, provided alternatives to the saturated .com space, and enabled more descriptive and brand-relevant domain names.

The original gTLDs

The seven original gTLDs established in 1984 and 1985 shaped the early internet and continue to define the TLD landscape today.

.com: commercial. The most registered, most recognised, and most trusted TLD worldwide. Originally intended for commercial businesses but the restriction was never enforced, .com became universally dominant for all types of websites. Over 160 million .com domains are registered, by far the largest TLD by registration volume. Operated by Verisign.

The dominance of .com means that for most organisations a .com domain is the gold standard, the default expectation when someone thinks of a website. The scarcity of available short and memorable .com names has driven interest in alternatives but .com maintains a trust and recognition advantage that no other gTLD has yet matched globally.

.net: network. Originally intended for network infrastructure organisations, internet service providers, network operators. Like .com the restriction was never enforced and .net became a general-purpose alternative when preferred .com names were unavailable. Less common than .com but widely recognised. Operated by Verisign alongside .com.

.org: organisation. Originally intended for non-profit and non-commercial organisations. The restriction was never enforced but .org has maintained stronger informal association with non-profits, open-source projects, advocacy organisations, and community initiatives. Wikipedia at wikipedia.org and Mozilla at mozilla.org exemplify this association. Operated by the Public Interest Registry.

.edu: education. Restricted to accredited US higher education institutions, colleges, universities, and associated organisations. The restriction is actively enforced, .edu registration requires verification of US accreditation status. The restriction gives .edu high trust as an identifier of legitimate educational institutions. Operated by EDUCAUSE.

.gov: government. Restricted to US government entities, federal, state, local, tribal. Managed by the Cybersecurity and Infrastructure Security Agency. The .gov restriction is strictly enforced, only verified government entities can register. The restriction makes .gov a highly trusted identifier of official US government information.

.mil: military. Exclusively for the US military. Managed by the US Department of Defense. Strictly restricted to official military use.

.int: international organisations. Reserved for organisations established by international treaties between governments. Strictly restricted. Few registrations, the United Nations at un.int and NATO at nato.int are examples.

New gTLDs

ICANN’s new gTLD program transformed the TLD landscape. Beginning with delegations in 2013 and continuing through subsequent rounds the program has introduced over 1,200 new generic TLDs. These new gTLDs range from generic descriptive terms to brand-specific TLDs to internationalised domain extensions.

Generic descriptive gTLDs: TLDs that describe a category of website or business activity. .shop, .store, .online, .website for e-commerce and general web presence. .app, .dev, .software, .cloud for technology products. .blog, .news, .media for content and publishing. .agency, .studio, .design, .consulting for service businesses. .health, .care, .clinic for healthcare. .finance, .bank, .insurance for financial services.

These descriptive gTLDs enable domain names where the TLD contributes meaningfully to the overall meaning, our.agency, cool.design, my.app. The TLD becomes part of the brand rather than a generic suffix.

Industry-specific gTLDs: TLDs targeted at specific industries with associated trust signals. .bank requires financial institution verification. .insurance requires insurance industry verification. .pharmacy requires pharmacy accreditation. These restricted new gTLDs provide trust signals within their industries similar to how .edu provides trust for education.

Geographic gTLDs: TLDs associated with specific cities, regions, or localities. .london, .nyc, .berlin, .tokyo, .paris. These combine geographic association with gTLD flexibility, unlike ccTLDs they are not nationally assigned but they carry strong geographic associations.

Brand gTLDs: large organisations have registered their own TLDs for exclusive brand use. .google, .apple, .amazon, .microsoft. Brand TLDs allow organisations to create domain names entirely within their own namespace, search.google, store.apple. Most brand gTLD registrations are used internally or for specific branded applications rather than for general public registration.

Internationalised gTLDs, IDN gTLDs: new gTLDs in non-Latin scripts alongside the internationalised ccTLDs. Generic terms in Chinese, Arabic, Devanagari, and other writing systems. Enabling fully native-script domain names for global markets.

Popular new gTLDs in practice

Certain new gTLDs have achieved significant adoption, particularly in specific industries and communities, demonstrating that gTLD alternatives to .com can build genuine recognition and trust.

.io: while technically a ccTLD assigned to the British Indian Ocean Territory .io functions as a gTLD in practice, it is used generically by technology companies worldwide with no geographic association. Hundreds of well-known technology platforms, developer tools, and web applications use .io as their primary domain. Within technology circles .io has achieved recognition and trust approaching .com for tech-specific products.

.co: operated as an open international TLD by Colombia. Widely adopted as a .com alternative, particularly by startups that could not obtain their preferred .com name. Twit.tv founder Leo Laporte famously said .co would become the new .com. While that prediction has not fully materialised .co has achieved solid recognition as a legitimate domain choice.

.app: a Google-operated new gTLD for applications and software. Requires HTTPS, all .app domains must serve content over SSL, making it one of the few TLDs with a built-in security requirement. Widely used by web and mobile applications.

.dev: another Google-operated gTLD for developers and development tools. Also requires HTTPS. Popular among developer-focused products and personal developer portfolios.

.supply: the TLD used by Redirect Supply itself. Descriptive new gTLD that contributes to the overall meaning of the domain, redirect.supply communicates the product purpose through both the second-level domain and the TLD together.

gTLDs and SEO

Google has stated clearly and repeatedly that new gTLDs are treated equivalently to .com and other established gTLDs in its ranking algorithms. A site on .supply ranks on the same basis as a site on .com: content quality, backlinks, technical factors, and user signals determine rankings, not TLD choice.

The practical SEO implications of gTLD choice are more nuanced than the algorithm statement suggests.

User trust and click-through rates: search rankings are influenced by engagement signals, how often users click on search results and how long they stay. Users are more familiar with .com and may have higher click-through rates for .com results at equivalent ranking positions. A less familiar gTLD may receive lower clicks, not because Google’s algorithm penalises it but because users trust it less instinctively. This is a human psychology factor that can indirectly affect SEO performance.

Backlink acquisition: building backlinks is central to SEO. Some website owners and content creators are less likely to link to unfamiliar TLDs, not from any deliberate policy but from habit and familiarity. A .com domain may find link acquisition marginally easier than an equivalent site on a newer gTLD in some contexts.

Brand recognition and direct traffic: strong brands generate direct traffic, users typing the domain directly rather than clicking from search. .com domains benefit from the browser behaviour of auto-completing or defaulting to .com: a user who types example in a browser address bar may have .com appended automatically. Sites on other gTLDs miss this automatic brand association.

No algorithmic penalty for new gTLDs: Google’s position is clear, a well-built, well-linked site on .supply will rank appropriately. The absence of algorithmic bias against new gTLDs means the choice is primarily a business and branding decision rather than an SEO decision. A highly relevant, high-quality site on a descriptive new gTLD can and does outrank mediocre sites on .com.

gTLDs and redirect management

gTLD management intersects with redirect management in several ways, from brand protection across multiple gTLDs to migration between gTLDs to the role of new gTLDs in domain portfolio strategy.

Multi-gTLD brand protection: organisations register their brand name across multiple gTLDs, brand.com, brand.net, brand.org, brand.io, brand.co: to prevent competitors and bad actors from using them. Each non-primary gTLD registration is configured with a permanent redirect to the primary domain. Managing multiple gTLD redirects centrally through a redirect management platform simplifies the administration of potentially large domain portfolios.

gTLD migration: moving from one gTLD to another, example.net to example.com when the .com becomes available, or example.com to example.io for a technology brand repositioning, requires comprehensive redirect management. Every URL on the old gTLD must redirect to its equivalent on the new gTLD with 301 permanent redirects. The old gTLD registration must be maintained for the duration that redirects are needed, typically years for established domains with significant backlink profiles.

New gTLD adoption and redirect strategy: organisations adopting new gTLDs for their primary domain must ensure the .com equivalent is either registered and redirected to the new gTLD primary, or is not available and cannot be registered by competitors. Redirect Supply operates at redirect.supply: a descriptive new gTLD choice where the TLD contributes to the brand meaning. Any relevant .com alternatives should be registered and redirected to avoid brand confusion.

ccTLD vs gTLD redirect patterns: multinational organisations using both ccTLDs and gTLDs in their domain portfolio create complex redirect patterns. The primary gTLD domain serves the global audience. ccTLD domains serve specific national markets, either redirecting to localised sections of the primary gTLD domain or hosting independent localised content. Redirect management coordinates the routing across all these domains.

Choosing between gTLDs

With hundreds of gTLDs available the choice extends beyond the historical .com versus alternatives debate. Selecting the right gTLD involves weighing availability, brand fit, audience expectations, and long-term strategic considerations.

.com when available and affordable: for most commercial websites .com remains the preferred choice when the desired name is available at standard registration cost. The universal recognition, trust, and direct traffic benefits of .com are difficult to replicate. If the preferred .com name is available it should generally be the first choice.

New gTLD when semantically appropriate: when a new gTLD contributes meaningfully to the domain name’s meaning and the .com equivalent is unavailable or prohibitively expensive a new gTLD can be an excellent choice. redirect.supply communicates more about the product than redirectsupply.com would. my.app or cool.design or digital.agency uses the TLD as part of the brand expression in a way .com cannot.

.io for technology products: the widespread adoption of .io in the technology industry has made it a legitimate and well-recognised choice for developer tools, web applications, and technology platforms. Within technology audiences .io carries recognition and implicit trust that other new gTLDs have not yet achieved.

.org for non-profits and open-source: the longstanding informal association between .org and non-commercial, mission-driven organisations makes it the natural choice for non-profits, open-source projects, and advocacy organisations, even though registration is open to all.

Register .com alongside any gTLD: regardless of which gTLD is chosen as primary the corresponding .com should be registered if available, to prevent brand confusion, competitor registration, and direct traffic loss from users who default to typing .com. The .com registration is then permanently redirected to the primary gTLD domain.