What Is the .to Domain? Tonga's Global ccTLD Explained

The .to domain is the country-code Top-Level Domain (ccTLD) of the Kingdom of Tonga — and one of the first country codes ever marketed to the whole world. Since 1997 its registry, Tonic (the Tonga Network Information Center), has sold .to names to anyone, anywhere, with no local-presence requirement. Because "to" is one of the most common words in English, the suffix became a natural canvas for domain hacks and short links: Amazon's amzn.to share links are the best-known .to names in circulation.

This page covers what .to is, its unusually early open-registration history, its distinctive WHOIS privacy stance, its complicated relationship with URL shorteners, and the honest trade-offs.

.to at a glance

What is .to?

.to is the ccTLD assigned to Tonga under the ISO 3166-1 two-letter country-code system. The IANA delegation record lists the Government of the Kingdom of Tonga as the manager, with registration services provided through Tonic, the Tonga Network Information Center. Like other ccTLDs, .to is governed by its national manager's policy rather than an ICANN registry agreement.

In practice, though, .to has behaved like a global extension for nearly its entire life. Registrations are made directly at the second level (yourname.to), there is no residency requirement, and Tonic's FAQ describes .to as "the first country code to be offered globally through an automated registry", running since June 1997.

One important SEO nuance: Google maintains a published list of ccTLDs it treats as generic (not geo-targeted), and .to is not on that list — the roster includes .ai, .co, .fm, .io, .me, and .tv, but not .to. Many .to sites still rank globally, but unlike .io or .co, you cannot point to Google's documentation for a generic-treatment guarantee.

History of .to

The .to domain was delegated in December 1995, in the first big wave of ccTLD delegations. According to the history recorded on Wikipedia, commercialization began in 1997, when San Francisco-based Tonic Corp. — founded by Eric Gullichsen and Eric Lyons — began selling .to names worldwide with the approval of Tonga's Crown Prince. That made Tonga one of the earliest small nations to treat its country code as a global digital export, years before .tv (Tuvalu) and .me (Montenegro) turned the model into an industry playbook.

Because registrations were open and readable as the English word "to," the namespace was quickly adopted by internet culture:

• Cryptographer Daniel J. Bernstein's cr.yp.to — a triple-stacked hack spelling "crypto" across two dots — became one of the most famous domain hacks anywhere, and is still online today.
• File-sharing and torrent-index sites gravitated to .to during the 2000s and 2010s (isohunt.to being a documented example), leaving an association that has faded as those sites disappeared.
• Czech and Slovak sites adopted .to because to means "it/that" in Slavic languages — the file-hosting service uloz.to ("save it") being the best-known example.
• Short-link services embraced the preposition reading, culminating in amzn.to, the short-link domain Amazon uses for shared product links.

How people use .to

• Domain hacks and phrase names — constructions where the URL reads as an English sentence, plus word-completing names like cr.yp.to.
• Branded short links — companies running their own redirect infrastructure on a compact .to name, with amzn.to the canonical example.
• Global startups and personal sites wanting a two-letter suffix where the equivalent .com is long gone.
• Toronto-flavored projects — "T.O." is a common nickname for Toronto.
• Czech/Slovak-language projects exploiting the "it/that" reading.

Who it's not ideal for: anyone planning a free public URL-shortening service (the registry prohibits them — see below), projects that require DNSSEC, and businesses that want Google's documented generic-ccTLD treatment.

Notable sites using .to

• amzn.to — Amazon's short-link domain, generated when users share product links; the best-known use of the suffix.
• cr.yp.to — the long-running home of cryptographer Daniel J. Bernstein (djb); the domain itself spells "crypto."
• uloz.to — the Czech file-hosting brand built on the Slavic-language reading of "to."

These span the suffix's three personalities: corporate short links, hacker-culture wordplay, and non-English-language branding.

.to vs other domains

Pick .io or .co when you want a startup-flavored name with Google's documented generic treatment. Pick .ly when your brand ends in "-ly." Pick .to when the preposition reading makes your name a phrase, when you run branded short links on your own infrastructure, or when the two-letter aesthetic matters more than checklist SEO guarantees.

Why choose .to?

• A genuinely readable suffix. Few TLDs double as one of the most common English words; a well-chosen .to name is a sentence, not an address.
• Open since 1997. No paperwork, no residency test — one of the longest track records of unrestricted global registration of any ccTLD.
• Registrant privacy by default. Tonic's WHOIS and RDAP return registration and DNS data "without revealing sensitive personal details" — no separate WHOIS privacy add-on needed.
• Unicode freedom. The registry allows names containing any unicode code point, which is why .to is one of the few places emoji domains are possible — while banning intentional homonym (look-alike) registrations.
• Active anti-abuse posture. Tonic takes down verified phishing domains and prohibits the free-shortener business model that generates most link abuse.

Things to consider

• No DNSSEC. The .to zone publishes no DS record in the root, so DNSSEC validation cannot be chained to your domain. For most sites this is invisible; for security-sensitive infrastructure it can be disqualifying.
• Two-year minimum initial term. New registrations commit you to at least two years up front (renewals can then be annual) — a longer minimum than most TLDs.
• Undocumented Google treatment. Absence from Google's generic-ccTLD list means geo-targeting behavior is not guaranteed in writing, unlike .io, .co, or .tv.
• Historical baggage. The 2000s-era torrent-site association has faded, but security-conscious reviewers occasionally remember it.
• Single-registry dependence. Policy, pricing, and support all flow through one small registry (Tonic) under the Tongan government's delegation, and ccTLD policy can evolve outside ICANN processes.

Who can register a .to domain?

Registration restrictions: open to all. There is no residency, citizenship, or local-presence requirement — any individual or organization worldwide can register a .to name, either directly with the Tonic registry or through an accredited registrar that carries the extension. Names are registered directly at the second level (yourname.to), with no mandatory com.to-style hierarchy.

The real rules are usage rules, set out in Tonic's FAQ and policies:

• Two-year minimum initial term for new registrations; renewals are available in one-year increments, up to ten years ahead.
• Prohibited uses: spam and phishing lead to suspension, and Tonic bans free public URL-shortening services outright, on the reasoning that free URL-shortening is inherently attractive for phishing attacks. Branded, self-operated short links (the amzn.to model) are a different matter.
• Reserved names: Tonic has reserved a set of names, and intentional homonym (look-alike) registrations are not allowed despite the open unicode policy.
• WHOIS: lookups work via WHOIS and RDAP but return registration and DNS data without personal registrant details.
• No DNSSEC is currently available at the registry level.

As a ccTLD, .to has no ICANN registry agreement; Tonic's published policies, under the Government of Tonga's IANA delegation, are the authoritative source.

.to pricing and value

.to sits in the premium-priced tier of ccTLDs. The two-year minimum initial term makes the up-front commitment larger than a typical one-year registration; renewals then run annually, with multi-year terms available. Because much of the namespace is registered directly with the registry, markups and promotions play a smaller role than in heavily discounted gTLD markets, while short, dictionary-word, and phrase-completing names command real aftermarket premiums driven by the domain-hack use case. Budget on the renewal rate and check live pricing at purchase time — this page intentionally quotes no numbers.

Reputation and email deliverability

.to carries a mixed but serviceable reputation. On the positive side, its most visible user is Amazon, the premium price point deters bulk spam registration, and the registry's bans on phishing and free shorteners attack the main abuse vectors at the policy level. On the cautious side, the file-sharing history and the popularity of redirect-style links mean some security tools look twice at unfamiliar .to URLs.

For email, the suffix itself is rarely decisive: modern filters weigh SPF, DKIM, and DMARC authentication and sender reputation far more than the TLD. A properly authenticated .to sender should reach inboxes normally, though a brand-new .to domain sending cold email faces the same warm-up scrutiny as any newly registered name.

Branding and naming tips

• Make it read as a phrase. The suffix's superpower is the preposition: names shaped like verb + .to or words ending in "-to" (cr.yp.to) are instantly memorable.
• Say it out loud. If you have to explain the dot placement, the hack is too clever; the best .to names survive being spoken on a podcast.
• Emoji domains are a novelty, not a strategy. They are technically possible on .to, but browser and email support is inconsistent.
• Don't build a free shortener on it. That business model is banned by the registry; branded redirects for your own product are fine.

How to register a .to domain at Namefi

1. Search for your desired name with the .to extension.
2. Choose an available name, remembering the two-year minimum initial term.
3. Register and configure DNS for your site and email.

Namefi is an ICANN-accredited registrar bridging Web2 and Web3, with transparent pricing and fast DNS management. You can also optionally tokenize your domain for provable on-chain ownership and easier transfers. New to extensions? Start with what is a TLD and the domain terminology guide.

Frequently asked questions

Can anyone register a .to domain?

Yes. .to is open to individuals and organizations worldwide with no residency or local-presence requirement. New registrations carry a two-year minimum initial term, and the Tonic registry prohibits certain uses, including spam, phishing, and free public URL-shortening services.

Does a .to domain affect SEO?

Google publishes a list of ccTLDs it treats as generic, and .to is not on it, so you should not assume automatic generic treatment the way you can with .io or .co. Many global sites still rank fine on .to, but a business chasing worldwide search visibility should weigh this nuance.

Does .to have public WHOIS?

Tonic operates both WHOIS and RDAP services, but they return domain registration and DNS information without revealing sensitive personal details about the registrant. This built-in privacy has long been a distinctive feature of the .to namespace.

Why do URL shorteners and domain hacks use .to?

Because "to" is a common English preposition, names like amzn.to read as natural phrases, which made .to a favorite for short links and word-completing domain hacks. Note that Tonic now prohibits free public URL-shortening services on .to because they attract phishing abuse; branded shorteners like Amazon's are a different, controlled use.

Related resources

• Domain hacks explained
• What is a TLD?
• ccTLD market share by registration volume
• What are tokenized domains?
• Glossary: ccTLD, domain hack, WHOIS, registry, DNSSEC
• Compare TLDs: .io, .co, .tv, .me, .ly, .us

Sources and further reading

• IANA — IANA delegation record
• tonic.to — Tonic
• tonic.to — tonic.to
• Google Search Central — .to is not on that list
• en.wikipedia.org — history recorded on Wikipedia