Namefi

What Is the .in Domain? India's Country-Code TLD Explained

The .in domain is India's ccTLD, run by NIXI on an open, liberalized basis since 2005. Learn its structure, IDN and .bharat support, and who should register.

Aileen WrightAileen WrightAuthorVictor ZhouVictor ZhouEditorAugust 5, 2026
  • tld

The .in domain is the official country-code top-level domain (ccTLD) for India, administered by the National Internet Exchange of India (NIXI). Unlike the local-presence rules that gate .jp and .kr, .in has been run as an open, liberalized namespace since 2005 — anyone, anywhere, can register one. It also anchors one of the largest internationalized-domain programs of any ccTLD, spanning more than a dozen Indian scripts under the .bharat family. This page covers what .in is, its second-level structure, the IDN program, and who should register one.

.in at a glance

FactDetail
TLD typeCountry-code TLD (ccTLD) for India
Registry operatorNational Internet Exchange of India (NIXI)
Year delegated1989
IDN supportYes — 16 Indian-script registration options, including the multi-script .bharat family, all in General Availability
DNSSECSupported
Registration restrictionsOpen to all — liberalized since January 2005, first-come, first-served, no residency requirement
Best forIndia-market businesses and brands, government and institutional entities via their categories, Indian-language-first projects via IDN/.bharat

What is .in?

.in is the ccTLD assigned to India under ISO 3166-1 (country code IN), delegated through the IANA root-zone database, which lists NIXI as both registry operator and sponsoring organization. As with any ccTLD, .in operates under Indian domain-name policy rather than a standard ICANN registry agreement.

Google does not classify .in among the small set of ccTLDs it treats as generic (that list — .ad, .ai, .as, .bz, .cc, .cd, .co, .dj, .fm, .io, .la, .me, .ms, .nu, .sc, .sr, .su, .tv, .tk, .ws — is published in Google Search Central's guidance on managing multi-regional sites). .in is absent from that list, so Google treats it as a genuine India-targeting signal.

History of .in

.in was delegated in 1989. For its first fifteen years it stayed a small, tightly managed namespace. The turning point came on January 1, 2005, when the Government of India liberalized .in registration policy and authorized NIXI — a not-for-profit body under what is now the Ministry of Electronics and Information Technology — to run the registry. A short sunrise period (January 1–21, 2005) protected trademark holders first; after that, .in moved to unrestricted, first-come, first-served registration open to anyone in the world, the structure that still governs it today, per NIXI's own about-the-registry page.

The registry's biggest expansion since then has been internationalization. India's first IDN ccTLD, .भारत (.bharat, Devanagari script), was delegated to the DNS root in February 2011, with public registration opening on August 27, 2014. NIXI subsequently added .bharat variants in seven more scripts — Bengali, Gujarati, Punjabi (Gurmukhi), Tamil, Telugu, Kannada, and others — extending script-native registration to a wide swath of India's 22 scheduled languages.

How people use .in

  • India-market businesses and brands using plain .in for a direct, recognizable India signal.
  • Companies and registered organizations, via .co.in, .com.in, and similar categories, alongside the open general .in.
  • Government agencies, via .gov.in, with NIC.in (India's National Informatics Centre) hosting much of the backbone for official portals.
  • Indian-language-first projects, via the 16-script IDN program and the .bharat family, reaching audiences more comfortable in a native script than Latin characters.
  • Global companies establishing an India-specific storefront or presence alongside their primary .com domain.

Who it's not ideal for: brands that specifically want to avoid any country association, since Google reads .in as India-targeted; and projects that need the strict category verification some other ccTLDs enforce — .in's open general tier does not itself gate registration by entity type.

Notable sites using .in

  • india.gov.in — the National Portal of India, launched November 10, 2005 and operated by the National Informatics Centre (NIC) as the Indian government's single-window information and services portal.
  • irctc.co.in — the Indian Railway Catering and Tourism Corporation's official train-ticketing portal, one of the most heavily trafficked .co.in sites in daily use.

.in vs other domains

Factor.in.com.co.in (IN company category)
TypeccTLD, open general tierLegacy gTLDccTLD, category-specific second level
EligibilityOpen, no restrictionOpen, no restrictionOpen, positioned for companies/organizations
Geo signal to GoogleIndia-targetedGenericIndia-targeted
IDN/script options16 Indian scripts, including .bharatLatin-script IDN variants onlyFollows .in policy

Choose .com for a globally neutral default with no country association. Choose .in when a direct India-market signal and open registration matter more than a sector label. Choose .co.in when you want the "registered company" flavor within the .in family, or a native-script .bharat name when your audience is primarily Indian-language-first.

Why choose .in?

  • Fully open registration. No residency, citizenship, or local-presence requirement — liberalized since 2005 and first-come, first-served ever since.
  • Direct India-market signal. For businesses genuinely serving Indian users, .in states that plainly.
  • Unmatched Indian-script IDN support. 16 scripts, including the multi-script .bharat family, make .in one of the most linguistically inclusive ccTLD programs anywhere.
  • Long-established, growing namespace. Delegated in 1989 and used by major government and commercial sites, .in carries real institutional weight in the Indian market.

Things to consider

  • Geo-targeted, not global. Search engines read .in as India-specific, a constraint for sites chasing a global, non-India audience.
  • Second-level categories add some naming complexity. Businesses must decide between plain .in, .co.in, and .com.in, each with slightly different positioning.
  • IDN/.bharat requires a script decision upfront. Picking the right script and Latin transliteration matters for how discoverable a native-script name is.
  • Open registration means no built-in trust signal. Because eligibility is unrestricted, .in itself does not verify who is behind a name the way a local-presence or credential-gated TLD does.

Who can register a .in domain?

Registration restrictions: open to all. Since the January 1, 2005 liberalization, NIXI has run .in on a first-come, first-served basis with no residency or citizenship requirement, per its own about-the-registry page. Individuals and organizations worldwide can register directly under .in or under second-level categories such as .co.in (companies and organizations) and .com.in (banks, registered companies, trademarks) through an accredited registrar.

For Indian-script registration, NIXI's Internationalized Domain Names program covers 16 scripts in General Availability, including the .bharat family, each following essentially the same open policy as .in. DNSSEC is supported at the registry level. Because .in is a nationally governed ccTLD, NIXI's own policy pages — not an ICANN registry agreement — are the authoritative source for current rules.

.in pricing and value

.in pricing follows general-ccTLD dynamics rather than a fixed number: first-year and renewal pricing commonly differ, so budget for the standing renewal rate rather than an introductory offer. Short, dictionary, or high-demand .in names may carry premium registration pricing, and IDN/.bharat names in some scripts may be priced differently from ASCII .in given the newer, thinner registrant base. This page intentionally quotes no specific figures — check current rates at the point of registration.

Reputation and email deliverability

.in carries a solid, mainstream reputation as an established national ccTLD used by government, major commercial, and institutional sites — it does not carry the documented spam-abuse profile associated with some unrestricted, ultra-cheap new gTLDs. For email deliverability, the extension itself is rarely the deciding factor; proper SPF, DKIM, and DMARC configuration matters far more than the TLD. The main practical consideration is audience fit: a .in address reads as India-facing, reassuring for Indian recipients but narrower for a purely international correspondent.

Branding and naming tips

  • Decide between .in, .co.in, and .com.in early. Each carries slightly different positioning — plain .in reads broadest, .co.in leans corporate.
  • Consider an Indian-script name if your audience is language-first. The 16-script IDN program, including .bharat, can reach readers more comfortable outside Latin characters.
  • Pair with a .com if you operate globally. Many companies run .com as the primary brand and .in as the India-specific storefront.
  • Register your script variants together. If a native-script name matters to your brand, secure the matching .bharat script alongside the Latin .in early, before someone else does.

How to register a .in domain at Namefi

  1. Search for your desired .in name, or the matching IDN/.bharat script variant.
  2. Choose between plain .in, .co.in, or .com.in based on how you want to position the brand.
  3. Register — no residency or local-presence documentation is required.
  4. Configure DNS to point your site or email.

Namefi is an ICANN-accredited registrar that bridges Web2 and Web3, with transparent pricing and the option to hold eligible domains as tokenized assets for provable ownership and easier transfers.

Frequently asked questions

Can anyone register a .in domain?

Yes. Since India liberalized .in registration in 2005, the National Internet Exchange of India (NIXI) has run it as an open, first-come, first-served namespace with no residency or citizenship requirement — individuals and organizations anywhere in the world can register a .in name through an accredited registrar.

Does a .in domain affect SEO?

Google treats .in as a country-targeted ccTLD for India, not a generic extension, so it signals to search engines that a site is meant for an Indian audience. That helps India-focused sites rank locally but works against sites built for a global audience.

What is .bharat?

The .bharat family is a set of internationalized ccTLDs run by NIXI that represent India in Indian scripts rather than Latin characters, including Devanagari .भारत and seven other scripts launched from 2014 onward. They follow largely the same policies as .in, giving script-native branding to Indian-language audiences.

Who runs the .in domain?

The National Internet Exchange of India (NIXI) is the registry operator for .in, listed as both registry operator and sponsoring organization in the IANA root-zone database, and it has managed the namespace on behalf of the Government of India since January 2005.

Sources and further reading

Related keywords

  • NIXI registry
  • .in vs .co.in
  • .bharat IDN domain
  • India domain liberalization
  • IDN ccTLD India
  • what is .in
  • .in domain
  • .in TLD

Contributors

Aileen WrightAuthor
Art & History Writer • Namefi

Aileen Wright is a student in her twenties living in New York City, where the distance between a museum wall and a library reading room is a short walk and a long afternoon. She came to name writing through art and history — the way a single portrait, coin, or manuscript margin can carry a name across centuries and change its meaning on the way.

Most weeks you can find her in Central Park with a paperback, or in the quiet of a public reading room chasing down where a name actually comes from rather than what a name-list says it means. She is also teaching herself to code, which has made her oddly precise about spelling, sorting, and the small details that decide whether a name ages well.

For Namefi she writes about the history and culture behind domain names, the stories brands carry as they rename, and the difference between a good story and a verified source.

Victor ZhouEditor
Founder & Standards Editor • Namefi

Victor Zhou is a technology founder and standards editor focused on digital identity and trust. He founded Namefi, edits Ethereum Improvement Proposals, and previously led smart-contract architecture work at Google Labs.

His work sits at the intersection of naming, ownership, and the systems people use to establish identity online. That perspective makes him especially interested in the way names move between personal meaning, public recognition, and digital infrastructure.

For Namefi, Victor edits and writes about domains as durable digital identity: how names become ownable onchain assets, how tokenization changes custody and trust, and what naming can learn from the systems people use to establish identity online.

Explore other extensions