1. Openprovider
  2. Domains
  3. Documentation per TLD

.in

This article describes the procedures and requirements of .in domain names.
Click on the subject below to open the dropdown for more information.

Registration

Successful domain registration via RCP or XML API or REST API requires:

  • two or more nameservers or a nameserver group

Important:

  • This TLD has strict contact verification requirements. You MUST provide verifiable contact information, or your domain may be suspended or deleted by the registry without warning or refund.
  • Adjusting contact details later will be a complex process due to slow/lack of responses from registry side.
  • Foreign / non-resident registrants are required to declare their connection or purpose related to India. Registrants will be prompted to select their connection to India during registration. This applies only to foreign / non-resident registrants. API documentation has also been updated for users integrating via REST API (in_nexus_connection_to_india / in_nexus_declaration_attestation) or XML API (inNexusConnectionToIndia / inNexusDeclarationAttestation).

NOTE:

To ensure registrant authenticity and communication reliability, the .IN registry now prohibits the use of disposable, temporary, or encrypted email services. This includes, but is not limited to:

  1. Guerrilla Mail – guerrillamail.com
  2. 10 Minute Mail – 10minutemail.com
  3. Temp Mail – temp-mail.org
  4. Mailinator – mailinator.com
  5. EmailOnDeck – emailondeck.com
  6. ProtonMail – proton.me
  7. Tutanota – tutanota.com
  8. Mailfence – mailfence.com
  9. Hushmail – hushmail.com
  10. StartMail – startmail.com

 

Hence effective Jan 14, 2026, we are introducing stricter validations to block the creation or update of contact handles using any of the above or similar email services. 

Transfer

Successful domain transfer via RCP or XML API or REST API requires:

  • authorisation code
  • two or more nameservers or a nameserver group
  • Transfer not allowed less than 60 days after domain registration

Important:

  • This TLD has strict contact verification requirements. You MUST provide verifiable contact information, or your domain may be suspended or deleted by the registry without warning or refund.
  • Adjusting contact details later will be a complex process due to slow/lack of responses from registry side.
  • Foreign / non-resident registrants are required to declare their connection or purpose related to India. Registrants will be prompted to select their connection to India during registration. This applies only to foreign / non-resident registrants. API documentation has also been updated for users integrating via REST API (in_nexus_connection_to_india / in_nexus_declaration_attestation) or XML API (inNexusConnectionToIndia / inNexusDeclarationAttestation).

 

NOTE:

To ensure registrant authenticity and communication reliability, the .IN registry now prohibits the use of disposable, temporary, or encrypted email services. This includes, but is not limited to:

  1. Guerrilla Mail – guerrillamail.com
  2. 10 Minute Mail – 10minutemail.com
  3. Temp Mail – temp-mail.org
  4. Mailinator – mailinator.com
  5. EmailOnDeck – emailondeck.com
  6. ProtonMail – proton.me
  7. Tutanota – tutanota.com
  8. Mailfence – mailfence.com
  9. Hushmail – hushmail.com
  10. StartMail – startmail.com

 

Hence effective Jan 14, 2026, we are introducing stricter validations to block the creation or update of contact handles using any of the above or similar email services. 

Authorization code required yes
Method of confirmation authcode
Registration period after transfer extends
Average transfer time Max 6 days
Advanced and simple transfers available Contact our Sales department to check if easy transfer of 100 or more .in domains is available.
Update

Owner change (trade)

  • Trade - via RCP or API, by updating the owner handle
  • Confirmation - via email to losing and gaining domain owners

Other update

NOTE:  Foreign / non-resident registrants are required to declare their connection or purpose related to India. Registrants will be prompted to select their connection to India during registration. This applies only to foreign / non-resident registrants. API documentation has also been updated for users integrating via REST API (in_nexus_connection_to_india / in_nexus_declaration_attestation) or XML API (inNexusConnectionToIndia / inNexusDeclarationAttestation).

Deletion / Restore

Delete

Restore / reactivate

Detailed extension information
Registry
Technical information
  • Available second level domains: .co.in, .firm.in, .gen.in, .ind.in, .net.in, .org.in
  • DNSSEC support: yes
  • Minimum length: 3 characters
  • Maximum length: 63 characters
  • Allowed characters: a-z 0-9 -
  • IDN characters: Yes
  • Registration period: 1-10 years
  • Renewal date offset: 0 days
    The number of days before the registry's expiration date, that Openprovider requires the domain to be renewed or expired. More info.
    Note that the dates as shown in your Openprovider account are always leading, even if they do not match the renewal date offset mentioned here.
  • Soft quarantine period: 44 days
    During this period, following after an expiration, the domain can be restored for free. This period does not apply if the domain is deleted explicitly. More info.
  • Quarantine period: 28 days
    During this period, an expired or deleted domain name can be reactivated at an additional fee.
Restrictions
  • Local presence required? no
  • Does Openprovider provide local presence services? n/a
  • Local activity required? no
  • Correct nameserver configuration required? no
  • The Domain(s) can be registered without further limitations.
Policies
  • Policies: https://www.registry.in/policies
Registration agreement The registry requires that a registration agreement is in place between the provider and the domain holder. The text of this registration agreement and any required supplements is the following:

Due to the regular changes in registry rules and configuration or missing information from registry side, and despite our effort to keep our knowledge base up-to-date, information in the knowledge base may be outdated or incorrect. If you encounter some issue, please report it through the "HotJar" feedback collector on the bottom right, or (if it is blocked by your browser) by clicking the "Submit a request" link below. No rights can be derived from the information in this knowledge base. If there is discrepancy between the knowledge base and the process in Openprovider, the process in Openprovider is leading.

Was this article helpful?
Additional questions? Submit a request