Revision as of 18:04, 2 March 2015 (view source) WikiAdmin (Talk | contribs) (Created page with "{{Infobox nTLD | name = .ADULT | image =200px | introduced = 2015 | category = Adult | registry = Afilias | idn capable = Yes | webpage = [https://www....")		Latest revision as of 12:20, 20 August 2021 (view source) WikiAdmin (Talk | contribs)
(12 intermediate revisions by 2 users not shown)
Line 1:		Line 1:
	{{Infobox nTLD		{{Infobox nTLD
	| name = .ADULT		| name = .ADULT
−	| image    =[[File:Afilias.jpg|200px]]	+	| image    =[[File:Adult.png|200px]]
	| introduced = 2015		| introduced = 2015
	| category = Adult		| category = Adult
−	| registry = Afilias	+	| registry = ARI
	| idn capable = Yes		| idn capable = Yes
	| webpage = [https://www.hexonet.net/domain-name/adult Register .ADULT]		| webpage = [https://www.hexonet.net/domain-name/adult Register .ADULT]
	| legal = TBA		| legal = TBA
	}}		}}
−	{{#repositoryinfo:  AFILIASSRS-LIVE-1API | adult }}	+	{{#repositoryinfo:  ARI-LIVE-1API | adult }}
	{{Sidebar}}		{{Sidebar}}
	<div style="font-size: 250%;">'''.ADULT'''</div><br/>		<div style="font-size: 250%;">'''.ADULT'''</div><br/>
	__TOC__		__TOC__
		+
		+	= Registration Information =
		+
		+	* '''TMCH Sunrise''': Starting March 2 - April 1, 2015, .PORN and .ADULT will be made available for a thirty day (30) period to trademark holders who are registered in the Trademark Clearinghouse (TMCH), as required under ICANN’s Rights Protection Mechanism.
		+	* '''Sunrise B''':  April 6 - April 30, 2015, This priority registration period is for 2011. XXX Sunrise B applicants.
		+	* '''Domain Matching''': May 6- May 31, 2015, registered owners of any .XXX domain (EXAMPLE.XXX) will be given priority to register its counterpart in .ADULT and .PORN (EXAMPLE.PORN and EXAMPLE.ADULT).  The Domain Matching Program will be available to all .XXX registrants who have a .XXX registration as of April 30, 2015.
		+	* '''General Availability''':  June 4, 2015, anyone can register a .PORN / .ADULT domain during this time, even individuals / entities outside the adult entertainment industry
		+
		+	= Sunrise B and Matching Eligibility =
		+
		+	'''Sunrise B Eligibility Requirements''' - Sunrise B Registration Requests in an ICM gTLD may only be submitted by the same Applicant that submitted a successful .XXX Sunrise B Reservation Request. The Applicant must use the same Accredited Registrar of Record that sponsored the Applicant in its underlying, directly matching .XXX Sunrise B Reservation Request; if such Registrar of Record is unwilling or unable to participate in the ICM gTLD Sunrise B Program, then the Applicant may use an alternate Accredited Registrar(s) designated by ICM. In the event there was more than one successful .XXX Sunrise B Reservation Request for the same second level domain name in the .XXX TLD, then, more than one Applicant may submit a Sunrise B Registration Request during the ICM gTLD Sunrise B Program for the directly matching second level domain name in an ICM gTLD. The Registry will allocate the matching second level domain name in the ICM gTLD on a first-come, first-served basis.
		+
		+	'''Domain Matching Eligibility Requirements''' - Only the Registrant of the directly matching .XXX TLD Registration is eligible to submit a Domain Matching Registration Request for the directly matching second level domain name in an ICM gTLD. The Applicant must use the same Accredited Registrar of Record that sponsored the Applicant in its underlying, directly matching .XXX Registration; if such Registrar of Record is unwilling or unable to participate in the ICM gTLD Domain Matching Program, then the Applicant may use an alternate Accredited Registrar(s) designated by ICM. The underlying, directly matching .XXX second level domain name must be registered by such Applicant as of April 30, 2015.
		+
	= Registry =		= Registry =
	{{Summarybox		{{Summarybox
Line 135:		Line 149:
	=== Authorization code ===		=== Authorization code ===
−	There are special requirements regarding the format of the authorization code. Please consider the following restrictions, if you want to assign a new authorization code to a .COM domain:	+	There are special requirements regarding the format of the authorization code. Please consider the following restrictions, if you want to assign a new authorization code to a domain:
	*Minimum 8 characters		*Minimum 8 characters

---

Latest revision as of 12:20, 20 August 2021

.ADULT
Overview
Introduced	2015
Category	Adult
Registry	ARI
IDN Capable	Yes
Dispute Policy	ICANN Rules
Webpage	Register .ADULT
Legal Information
Legal	TBA

Contents 1 Registration Information 2 Sunrise B and Matching Eligibility 3 Registry 4 Periods 5 API 5.1 Domain Registration 5.2 Domain Transfer 5.3 Delete Domain 5.4 Restore Domain 5.5 Ownerchange 6 TLD specific 6.1 Authorization code 7 Addons 8 RegistrarOC 8.1 ICANN Whois Data Reminder Policy (WDRP) 8.2 ICANN Registrar Data Escrow Program (RDE) 8.3 Restore Process

[edit] Registration Information

• TMCH Sunrise: Starting March 2 - April 1, 2015, .PORN and .ADULT will be made available for a thirty day (30) period to trademark holders who are registered in the Trademark Clearinghouse (TMCH), as required under ICANN’s Rights Protection Mechanism.
• Sunrise B: April 6 - April 30, 2015, This priority registration period is for 2011. XXX Sunrise B applicants.
• Domain Matching: May 6- May 31, 2015, registered owners of any .XXX domain (EXAMPLE.XXX) will be given priority to register its counterpart in .ADULT and .PORN (EXAMPLE.PORN and EXAMPLE.ADULT). The Domain Matching Program will be available to all .XXX registrants who have a .XXX registration as of April 30, 2015.
• General Availability: June 4, 2015, anyone can register a .PORN / .ADULT domain during this time, even individuals / entities outside the adult entertainment industry

[edit] Sunrise B and Matching Eligibility

Sunrise B Eligibility Requirements - Sunrise B Registration Requests in an ICM gTLD may only be submitted by the same Applicant that submitted a successful .XXX Sunrise B Reservation Request. The Applicant must use the same Accredited Registrar of Record that sponsored the Applicant in its underlying, directly matching .XXX Sunrise B Reservation Request; if such Registrar of Record is unwilling or unable to participate in the ICM gTLD Sunrise B Program, then the Applicant may use an alternate Accredited Registrar(s) designated by ICM. In the event there was more than one successful .XXX Sunrise B Reservation Request for the same second level domain name in the .XXX TLD, then, more than one Applicant may submit a Sunrise B Registration Request during the ICM gTLD Sunrise B Program for the directly matching second level domain name in an ICM gTLD. The Registry will allocate the matching second level domain name in the ICM gTLD on a first-come, first-served basis.

Domain Matching Eligibility Requirements - Only the Registrant of the directly matching .XXX TLD Registration is eligible to submit a Domain Matching Registration Request for the directly matching second level domain name in an ICM gTLD. The Applicant must use the same Accredited Registrar of Record that sponsored the Applicant in its underlying, directly matching .XXX Registration; if such Registrar of Record is unwilling or unable to participate in the ICM gTLD Domain Matching Program, then the Applicant may use an alternate Accredited Registrar(s) designated by ICM. The underlying, directly matching .XXX second level domain name must be registered by such Applicant as of April 30, 2015.

[edit] Registry

TLD	.adult
Registry	Neustar
Dispute Policy	Rules
Registrar	1api GmbH
WHOIS-Update	Real-Time
Min. Characters	2
Max. Characters	63
Character Set	Letters and numbers Hyphens ("-"), however not at the beginning or directly in front of the TLD IDN: allowed
Limitations	Registrant Contacts: Required: 1 / Maximum: 1 Admin Contacts: Required: 1 / Maximum: 1 Tech Contacts: Required: 1 / Maximum: 1 Billing Contacts: Required: 0 / Maximum: 1
{{{Possible Extensions}}}
IDN capable	Yes
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
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	ICANN-TRADE

[edit] Periods

{{{Possible Extensions}}}
Registration Periods	1-10 years
Add Grace Period	0 days
Accounting Period	-5 days
Finalization Period	1 day
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

[edit] API

[edit] 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)
period = (PERIOD)
transferlock = 0 | 1 | (NULL)

[edit] 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

auth = (TEXT)

OPTIONAL

period = (PERIOD)
transferlock = 0 | 1 | (NULL)
action = REQUEST | APPROVE | DENY | CANCEL | USERTRANSFER

[edit] 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)

[edit] 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)

OPTIONAL

subuser = (TEXT)
renewalmode = (NULL) | (TEXT)

[edit] Ownerchange

All contact information with the exception of registrant Name, Firstname and Organisation can be updated through the ModifyDomain command.
In order to change the owner you have to request a trade with the TradeDomain command. This can be done through our web interface or through our API:

command = TradeDomain
domain = <DOMAIN>
ownercontact0 = <CONTACT>

command = ModifyDomain
domain = (DOMAIN)

REQUIRED

ownercontact0 = (CONTACT)

[edit] TLD specific

[edit] Authorization code

There are special requirements regarding the format of the authorization code. Please consider the following restrictions, if you want to assign a new authorization code to a domain:

• Minimum 8 characters
• having at least one (1) numeric,
• one (1) alphabetic, and
• one (1) special character

You may generate a valid random auth code by adding this parameter to the ModifyDomain command:

command = ModifyDomain
domain = (DOMAIN)

REQUIRED

generaterandomauth = 1

[edit] Addons

The following overview shows you all available Domain Addons which can be used for this special kind of TLD. It also shows the respective API parameters which are required to activate the Domain Addons:

Addon Class	Parameter to (de)activate *1)	Renewal term *2)	Affected Parameters *3)
Proxy (WHOISTRUSTEELITE_ARI)	X-ACCEPT-WHOISTRUSTEELITE-TAC = 0 | 1	1 month	All Contacts
Proxy (WHOISTRUSTEE_ARI)	X-ACCEPT-WHOISTRUSTEE-TAC = 0 | 1	1 month	All Contacts

[edit] 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.