On the ICANN Website. Please also refer to RFC 3915 for more
information.

Protecting Your .IN Domain

The .IN Registry has prepared the below advisory for .IN domain owners to assist them with protecting their domain name. Please feel free to distribute the following to your clients. 

After you register your .IN domain name and build your online presence, it's important for you to understand how to protect your .IN domain name. 

Your .IN domain name also has value-both in monetary terms and in terms of the message you send by having a .IN identity. Chances are you wouldn't give away your domain name to a group or an individual who promotes products and services that are counter to your mission, nor are you likely to sell your .IN domain name to businesses that sell products or services you deem inappropriate. That's why .IN Registry, wants to help make sure your .IN domain name doesn't inadvertently fall into the wrong hands. 

Registering recently expired domains has resulted in a number of cases where expired domain names are registered and utilized in a fashion that is counter to the mission and intention of the original owner. 

Every day, many .IN domain names become available because domain holders, also known as registrants, allowed them to expire or were unaware that the domain names were up for renewal. And every day, those same .IN domain names become vulnerable to companies and individuals who can exploit them for economic gain, without regard for their actual use or meaning. The process of obtaining expired domain names has become sophisticated, automated, and increasingly popular. And the consequences to the original .IN domain holders can be serious. 

We believe the best way to protect your .IN domain name is to take proactive and preventive measures. 

See these Simple Steps to protect your .IN domain name today: 

1. Verify Registration of Your .IN Domain Name 

Whether you registered your .IN yourself or whether someone else in your organization was responsible for registering it, it's essential that you verify that you or an authorized representative of your organization has been named as the registrant. A simple visit to the WHOIS tool
is a good first step. There you can view the name of the registrant, administrative contact, and technical contact for your .IN domain(s). You can
also find the name of the registrar through which your .IN domain was registered. 

2. Verify and Update and Administrative Contact Information Regularly 

Consider making it organizational policy to regularly verify and update .IN domain name information. If it's your responsibility to keep the information updated, put it on your calendar for verification twice a year. If instead it's
the responsibility of a staff member, instruct the staff member to schedule the task for twice a year. In fact, having two staff members responsible for
checking domain information is even better. Any information pertaining to your .IN domain that needs changing can be updated by contacting and working with your registrar. 

3. Check that Email Contact Information is Valid 

Registrars are the organizations that provide registration services for the public, and the most common way they notify .IN registrants of domain name renewal is by e-mail. If you can't be reached by email, it's possible your domain name will expire without your knowledge. Therefore, it's essential that the email addresses on file with your registrar be current. You can see whose
e-mail address is on file when reviewing your .IN domain name WHOIS information at www.getyourown.in. And you can update your e-mail contact information by contacting and working with your registrar. 

4. Register Your .IN for Maximum Period of Time 

The maximum registration period for a .IN domain name is 10 years. Consider registering your .IN domain name for the maximum period of time at initial registration or even at the time of renewal. 

5. Ask your registrar to place Client Update, Client Transfer prohibited statuses on Your Domain Name so it can only be updated and transferred when you intend to do so 

Client Update and Client Transfer Prohibited domain statuses means that your domain name is "locked" and it can't be transferred or updated until the said statuses are removed. 

6. Also refer to .IN Domain Transfer and RGP FAQ

If the domain name has expired before it is deleted and enters RGP and then it is restored, the registrar's account is debited for the RGP fee and the one-year renewal fee. If the domain name has NOT expired prior to deletion and entering RGP and then it is restored, the registrar's account is debited the RGP fee, but the renewal fee is charged only if a renew is requested explicitly or the domain was deleted within the 45-day Auto-Renew Grace Period. When at all commercially reasonable, the domain name will be reinstated. It is up to each registrar whether to charge the registrant for the renewal fee in addition to an RGP fee.

Once the 30-day RGP for a domain name has passed, it cannot be restored. RHP serves as a notice period for registrars regarding the pending availability of the domain name.

.IN Registry does not determine the fees that registrars charge their customers. However, the registrar incurs extra costs each time it invokes the RGP process. Registrars may charge a fee to restore a domain name through RGP at their discretion. You should contact your registrar to inquire about the fee being charged.

No. Once a domain name is placed in RGP, no Internet services for that domain name, including e-mail, will work.

No. Once a domain name is placed in RGP, no Internet services for that domain name will work.

For a domain name to be released for registration, it must complete the 30-day RGP and the five-day RHP. In total, a domain name can be released for re-registration 35 days after it has been deleted by a registrar, provided that there has been no restore request received by the registry during the RGP. To calculate the date a deleted domain name will be available for registration, add 35 days to the "last updated on" date reflected in the WHOIS.

If your domain name has been placed in RGP, it is because your registrar requested to delete it. If you wish to redeem the domain name, YOU MUST CONTACT YOUR REGISTRAR IMMEDIATELY.

The sponsoring registrar for the domain name (as indicated in the WHOIS) is the ONLY registrar that can restore it. .IN Registry cannot directly restore your domain name -- it can act only on explicit instructions from the sponsoring registrar. Please note that your registrar may charge a fee for restoring the domain name.

If a domain name is in RHP, the "Status" field in the WHOIS will show the domain name as "PENDING DELETE SCHEDULED FOR RELEASE HOLD."

If a domain name is in RGP, the "Status" field in the WHOIS will show the domain name as "PENDING DELETE RESTORABLE and HOLD." All Internet services
associated with the domain name will remain disabled.

If a registrar deletes a domain name and does not request that the domain name be restored during the 30-day RGP, it enters RHP. RHP lasts for five days, and during this time domain name is locked and unable to be restored. After five days, it becomes available for re-registration. Once the domain name enters RHP, the prior registrant cannot request a restore. When a domain name is in RHP, its status is listed as PENDING DELETE SCHEDULED FOR RELEASE and HOLD.

To make a change, you must send a request to your registrar, who will then put the request through to the .IN registry. NIXI is not allowed to change records directly for registrants.

The authorization code is a 6- to 16-character code assigned by the registrar. The auth code is basically a password for the domain name. Auth codes are a security measure, ensuring that only the owner of the domain can make transfers. 

If you do not know your auth code, you can obtain it from your registrar. Registrars are contractually required to provide the auth code upon the request by the registrant.

• Sponsoring registrars can obtain the auth code for their sponsored domains by sending an EPP command to the registry. Registrars are only able to obtain auth codes for the domain names they sponsor.
• NIXI does not give out authorization codes to registrants. NIXI advises that you change your auth code after a transfer. You can do this through your new (gaining) registrar.

For Registrant-to-Registrant Transfers:

The registrant should update the contact information through the sponsoring registrar. NIXI cannot do this for you; you must do it through the registrar.

For Registrar-to-Registrar Transfers:

• Obtain the authorization code from the current sponsoring registrar of the domain. Please consult the WHOIS to find out who the sponsoring registrar is.
• After you receive your authorization code, supply it to the new (gaining) registrar.
• The new (gaining) registrar should then initiate the transfer. Once initiated, the transfer will be completed in five 24-hour periods.
• NIXI advises that you change your auth code after a transfer. You can do this through your new registrar. 

Domain Status in WHOIS FAQ 

What does the STATUS mean in the WHOIS query results for a .IN
domain??

The registrant should contact the registrar directly if there is any question
regarding the domain status.

What does "CLIENT" mean in a WHOIS STATUS?

If "CLIENT" precedes the STATUS that is PROHIBITED, that status is set by the registrar and can only be removed by the registrar. The registrant must contact the registrar directly to have this changed. These are the examples of a
registrar CLIENT status: 

What do the following Statuses mean in a WHOIS STATUS?

If the STATUS is PROHIBITED, that status is set by the registry and can only be removed by the registry. The registrant must contact the registrar directly to inquire about the registry-set Prohibited Statuses and to have this changed.
These are the examples of a Registry status:

If additional information is required about the domain status, who should I contact?

The registrant should contact the registrar directly if there is any question regarding the domain status.

Redemption Grace Period FAQ

• What is the Redemption Grace Period (RGP)?
• What is the Redemption Hold Period (RHP)?
• How do I know if a domain name is in RGP?
• How do I know if a domain name is in RHP?
• My domain name has been placed in RGP. How do I redeem it?
• How do I know when a domain name will be released for re-registration?
• Will my domain name still work if it is in RGP?
• Will I still be able to get e-mail if my domain name is in RGP?
• Why is my registrar charging me to redeem my domain name through RGP?
• My domain name is in RHP. Why can't I restore it?
• Will I be charged a renewal fee in addition to the RGP fee itself? Do I lose any time that remained on my registration?
• Where can I find more information about the ICANN requirements for RGP?

RGP is a service that allows the registrar to restore a .IN domain name that has been unintentionally deleted. RGP is a 30-day period that begins after a registrar requests that the registry delete a domain name. When a domain name is in RGP, its status is listed as PENDING DELETE RESTORABLE and HOLD. When a domain name enters RGP, it is removed from the .IN zone file. As a result, any Internet services served by the domain name will be disabled (e.g., e-mail or a Web site). The registrant must act IMMEDIATELY if he or she wants to restore the domain name via the sponsoring Domain Registrar. After the 30-day RGP, the domain name enters the Redemption Hold Period (RHP).

Punjabi, Tamil, Urdu, Gujarati, Telegu, Bengali & Manipuri( in Bengali script) , Malayalam, Sindhi, Kashmiri, Santali, Sanskrit, Assamese, Oriya, Kannada, Devnagari(Hindi, Bodo(Boro), Dogri, Konkani, Maithili, Marathi, Nepali, and Sindhi-Devanagari

The "Domain Name" field will display the registered name in Punycode (e.g.: xn-- p1b6ci4b4b3a.xn--h2brj9c). Three additional fields will be added to the display output.:

• Language-Tag: The intended Launguage-Tag of the IDN as determined by the registrant (e.g. "HIN-DEVA" for Hindi)
• Unicode Hex: The IDN in Unicode Hex format (e.g. Unicode Hex:U+0924 U+094D U+0924 U+094D U+0924 U+094D)
• Unicode HTML: The IDN in HTML त्त्त्).

Example of an IDN Display in WHOIS with reserved variants:
Domain ID:D3776-LRMS
Domain Name: XN--P1B6CI4B4B3A.XN--H2BRJ9C
Created On:31-Aug-2011 10:08:22 UTC
Expiration Date:31-Aug-2013 10:08:22 UTC
IDN Script:hin-deva
Unicode Hex:U+0909 U+0926 U+093E U+0939 U+0930 U+0923 Unicode HTML:उदाहरण DNSSEC:Unsigned
Variant reserved by .IN Registry: XN--P1B6CI4B4B3A.XN--H2BRJ9C

NIXI had launched the .भारत Devanagari IDN registrations on 15th August 2014 in a phased manner and has now announced sunrise launch of additional languages namely Kannada, Oriya ,Assamese, Sanskrit, Santali, Kashmiri, Sindhi and Malayalam on the 16th of March 2020. General availability of these additional IDNs on first come first served basis will be from 15th June 2020 at 10:00am IST/ 04:30 UTC.

More information on timelines, previously launched IDNs in general availability and IDNs in sunrise available at /internationalized-domain-names-idns

Punjabi, Tamil, Urdu, Gujarati, Telegu, Bengali & Manipuri( in Bengali script) , Malayalam, Sindhi, Kashmiri, Santali, Sanskrit, Assamese, Oriya, Kannada, Devnagari(Hindi, Bodo(Boro), Dogri, Konkani, Maithili, Marathi, Nepali, and Sindhi-Devanagari

To register a .भारत IDN, go to a .IN Accredited registrar. You can check the list of .IN Accredited registrars from the registry website link:
Accredited Registrars

The retail pricing for all domains is set by the registrar.

The new Microsoft Internet Explorer (IE7), Netscape 7.1, Mozilla 1.4, Firefox 1.0 and Opera 7 are anticipated to be IDNA compliant browsers. Subsequent versions of these browsers are also expected to contain this same functionality.
Further questions about IDN compatibility should be directed to your registrar.

Internationalized Domain Names (IDNs) are domain/host names that are represented with native language, non-ASCII characters. The native language domain name is followed by the top- level domain (TLD), such as .भारत. An example of an IDN is: उदाहरण.भारत.

How does the Registry control access to the Shared Registry System?

Access to the Shared Registry System is restricted by three mechanisms:

• Access control to the production SRS is restricted by IP address filters.
• SSL encryption is required for the communication channels between the Registrar's client system and the OT&E and Production systems.
• Authentication by means of a username and password is required for session establishment.

OT&E FAQ OT & E instructions and documentation are available in Become a Registrar. How do I begin the accreditation process? What do I do after I receive the OT&E welcome package? How do I test my client application? How do I arrange a time for OT&E testing? What happens after OT&E testing is completed? What key or cert sizes are accepted ?

How do I begin the accreditation process?

The OT&E certification process begins when the registry accepts a registrar's application. Tech Support will send you a welcome package.

If you think you would like to begin the process, please go to the Become a Registrar page.

What do I do after I receive the OT&E welcome package?

The registrar is responsible for developing the client application that will interface with the registry using the EPP protocol. The Registrar Toolkit is available to any interested party that would like to develop Registrar client applications.

A registrar may opt to develop their application to conform to the EPP specification without the use of the Registrar Toolkit. This is acceptable as long as the client is able to pass the OT&E connection test process.

The registry-registrar communication channel will be encrypted. An SSL certificate from an approved certificate authority is required to establish this encrypted channel. The registrar is responsible for acquiring the SSL certificate and developing support for SSL in their client application.

How do I test my client application?

During client development, the registrar will have access to the OT&E environment. In the OT&E environment, the registrar may test the operation of their software to verify the correct handling of EPP commands and their responses.

Operations performed in the OT&E environment will not be charged and will not have any impacts on the live IN Registry. Registrars will continue to have access to the OT&E environment after accreditation, so that they may continue to test their software systems

How do I arrange a time for OT&E testing?

There is no time to schedule any testing as such. When you receive a valid signed SSL Certificate, username and password and confirmation that your IP Range was accepted and whitelisted, you will be able to connect and begin your testing.

What happens after OT&E testing is completed?

Upon successful OT&E connection and you are satisfied that you are able to perform all of the actions required, you should contact the Tech Support team and inform them. Once they have confirmed that they can see you connected in OT&E they will be able to start the process to connect to the live IN Production Registry System.

What key or cert sizes are accepted?

The .IN registry currently utilizes private keys with 2048 bits in length minimum and support up to 4096 bit length.