Personal tools

From HEXONET Wiki

Jump to: navigation, search
(Domain Registration)
Line 93: Line 93:
 
subuser = <TEXT> | <NULL>
 
subuser = <TEXT> | <NULL>
 
</pre>
 
</pre>
 +
 +
 +
 +
 +
Limitations to .IN registrations
 +
 +
 +
NIXI, the .IN Registry has implemented new limits to the amount of .IN domain names a single registrant can register.
 +
The policy is effective immediately under .IN, which includes all .IN subdomains and third levels, and prohibits individual registrants (private persons and organisations) from registering more than two domain names.
 +
 +
This applies across all registrars, e.g. any one registrant having registered more than two domains may have their domain(s) deleted by us or by the registry regardless of which registrar is used for prior registrations. This policy is not applied retroactively, so all registrations prior to February 1, 2022 are unaffected.
 +
 +
NIXI has stated that registrants can apply for written approval of additional registrations to their CEO.
  
 
=== Domain Transfer ===
 
=== Domain Transfer ===

Revision as of 13:33, 8 March 2022

.IN

.IN is the official country code Top-Level-Domain (ccTLD) of India. .IN is very popular for companies and individuals located in India or for corporations looking to do business with India.


In.jpg
Introduced 1989
Country India
Registry NIXI
IDN Capable No
Webpage Register .IN

Contents


Registry

TLD

.in

Allowed TLDs

.in, .co.in, .net.in, .org.in, .firm.in, .gen.in, .ind.in

Registry

NIXI

Dispute Policy

Rules

Registrar

1api GmbH

WHOIS-Server

whois.registry.in

WHOIS-Update

Real-Time

Min. Characters

3

Max. Characters

63

Character Set
  • Letters and numbers
  • Hyphens ("-"), however not at the beginning or directly in front of the TLD
  • IDN: not allowed
Limitations
  • Registrant Contacts: Required: 1 / Maximum: 1
  • Admin Contacts: Required: 1 / Maximum: 1
  • Tech Contacts: Required: 1 / Maximum: 1
  • Billing Contacts: Required: 1 / Maximum: 1

{{{Possible Extensions}}}

IDN capable

No

Restore capable

Real-Time

Handle Updates

Supported

Registration System

Real-Time

Allowed number of NS

0 to 13

Registry Nameservercheck

No

Host IP-Addresses Type

IPv4 / IPv6

Hosts managed as

Object

Root Nameserver Update

Real-Time

SEC DNS Interface

DS data interface

Transferclass

Pull

Transfer Periods

1Y

Transfer Authcode required

Yes

Transfer Real-Time

No

Transfer Pending Period

5 days

Transfer Expire Action

ACK

Transfer ACK by

Registrar

Transfer NACK by

Registrar

Transfer Lock

Yes

Owner Change by

Update


Periods

{{{Possible Extensions}}}

Registration Periods

1-10 years

Add Grace Period

0 days

Accounting Period

0 days

Finalization Period

44 days

Failure Period

44 days

Payment Period

-61 days

Deletion Restorable Period

30 days

Deletion Hold Period

5 days

Explicit Renewals

Yes

Renewal Periods

1-9 years


API

Domain Registration

Domains can be registered in Real-Time with the API AddDomain command.

command = AddDomain
domain  = (DOMAIN)

REQUIRED

ownercontact0 = (CONTACT)
admincontact0 = (CONTACT)
techcontact0 = (CONTACT)
billingcontact0 = (CONTACT)
nameserver0 = (NAMESERVER)
nameserver1 = (NAMESERVER)

OPTIONAL

auth = <TEXT> | <NULL>
transferlock = 0 | 1 | <NULL>
subuser = <TEXT> | <NULL>



Limitations to .IN registrations


NIXI, the .IN Registry has implemented new limits to the amount of .IN domain names a single registrant can register. The policy is effective immediately under .IN, which includes all .IN subdomains and third levels, and prohibits individual registrants (private persons and organisations) from registering more than two domain names.

This applies across all registrars, e.g. any one registrant having registered more than two domains may have their domain(s) deleted by us or by the registry regardless of which registrar is used for prior registrations. This policy is not applied retroactively, so all registrations prior to February 1, 2022 are unaffected.

NIXI has stated that registrants can apply for written approval of additional registrations to their CEO.

Domain Transfer

The transfer has to be initiated by the gaining registrar and can be requested with the API TransferDomain command.
A valid Authorization Code must be provided to initiate a transfer successfully. You may obtain the authorization code from the losing registrar.
As soon as a domain transfer has been initiated it can either be approved ("ACK") by Registrar or denied ("NACK") by Registrar. If the registry receives neither a denial ("NACK") nor an approval ("ACK") the transfer will be ACKed after 5 days.

Please note that HEXONET is acting in compliance with ICANN Transfer Guidelines. The respective policies can be viewed under http://www.icann.org/transfers/ :

As soon as you have submitted a transfer request, the HEXONET system start the transfer through the official registry and the losing registrar will receive the transfer request. The losing registrar will then send an email to the domain registrant/administrative contact, allowing them to deny the pending transfer. If there is no response received within 5 days, the transfer will automatically be processed.

command = TransferDomain
domain = (DOMAIN)

REQUIRED

action = REQUEST | APPROVE | DENY | CANCEL | USERTRANSFER
auth = <TEXT>

OPTIONAL

order = CREATE | REPLACE | UPDATE

subuser = <TEXT> | <NULL>
period = <PERIOD>
transferlock = 0 | 1 | <NULL>

Delete Domain

Domains can be deleted with the API DeleteDomain command.
There is a Deletion Restorable Period of 30 days and a following Deletion Hold Period of 5 days.

command = DeleteDomain
domain = (DOMAIN)

REQUIRED

n/a


Restore Domain

Restores can be processed in realtime. A restore is possible within 30 days upon deletion. Please use the command RestoreDomain.

command = RestoreDomain
domain = (DOMAIN)

REQUIRED

n/a

OPTIONAL

renewalmode = <NULL> | <TEXT>
subuser = <TEXT>


Ownerchange

An Ownerchange is free of charge and can be done with the API ModifyDomain command.

TLD specific

There are no specific parameters available

Addons

RegistrarOC

ICANN Whois Data Reminder Policy (WDRP)

At least annually, a registrar must present to the registrant the current Whois information, and remind the registrant that provision of false Whois information can be grounds for cancellation of his domain name registration. Registrants must review their Whois data, and make any corrections.

ICANN Registrar Data Escrow Program (RDE)

Under the data escrow provision of the Registrar Accreditation Agreement (RAA), all ICANN-accredited registrars must regularly deposit a backup copy of their gTLD registration data with ICANN through ICANN's arrangement with Iron Mountain or they may elect to use a Third Party Provider of RDE services that has been approved by ICANN.

Restore Process

To restore a domain as a RegistrarOC customer, you simply have to execute the RestoreDomain command. HEXONET directly forwards the restore request to the registry, which performs the restore in real-time. As soon as the restore is complete, the domain will get assigned to your account with the original domain data.

Please do not initiate a restore directly at the registry (e.g. using the registrar webinterface). All restore operations must be performed through our system.