What changed, and why it matters before you order
For most of its life .in behaved like an unusually relaxed country code: open to the world, instant, no paperwork. That is no longer an accurate description, and buying on the old description is how people end up with a domain that does not resolve. NIXI now requires identity verification for new registrations, backed by a registrar agreement in force since 15 May 2025, and the registry will hold a name on serverHold until the check clears.
None of this closes .in to foreign registrants. NIXI has been explicit that foreign nationals and entities remain eligible; what it asks of them is evidence of who they are and a short statement of their business connection to or purpose in India. The practical effect is a lead time rather than a barrier. If an .in name is part of a launch, order it far enough ahead that a document request does not land on your launch day.
How the verification actually runs, and what we do
The registry's own e-KYC path is built for Indian identity documents, which is why the process forks. An Indian individual verifies with an Aadhaar, PAN, passport or voter ID; an Indian company adds its certificate of incorporation and an authorised signatory's ID. A registrant outside India supplies a passport or a company registration extract together with the statement of India connection, because the domestic e-KYC tooling will not accept foreign documents.
We are a reseller, not the registry, so we cannot pre-approve anything or shorten NIXI's queue. What we do is collect the right documents with the order rather than after it, keep the registrant record accurate so a compliance query never arrives in the first place, and tell you plainly when a proposed .in name looks like it will attract questions. Registration, renewal, transfer and restore prices are all shown live above before you commit.