Editing PORN

{{Infobox nTLD
| name = .PORN
| image    =[[File:Porn.png|200px]]
| introduced = 2015
| category = Adult
| registry = ARI
| idn capable = Yes
| webpage = [https://www.hexonet.net/domain-name/porn Register .PORN]
| legal = TBA
}}
{{#repositoryinfo: ARI-LIVE-1API | porn }} 
{{Sidebar}}
<div style="font-size: 250%;">'''.PORN'''</div><br/>
__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 =
{{Summarybox
| TLD={{#IfEmpty: {{#var:TLD}} | {{#var:TLD}} | - }}
| Registry={{#IfEmpty: {{#var:REGISTRYURL}} | [{{#var:REGISTRYURL}} {{#var:REGISTRYURLNAME}}] | - }}
| Dispute Policy={{#IfEmpty: {{#var:REGISTRYDISPUTEPOLICY}} | [{{#var:REGISTRYDISPUTEPOLICY}} Rules] | - }}
| Registrar={{#var:REGISTRAR}}
| WHOIS-Server={{#var:REGISTRYWHOISSERVER}}
| WHOIS-Update={{#var:REGISTRYWHOISUPDATE}}
| IDN capable={{#var:REGISTRYIDNCAPABLE}}
| Restore capable={{#var:RESTOREPOLICY}}
| Handle Updates={{#var:REGISTRYHANDLEUPDATE}}
| Registration System={{#var:REGISTRYREGISTRATIONSYSTEM}}
| Min. Characters={{#var:REGISTRYCHARSMIN}}
| Max. Characters={{#var:REGISTRYCHARSMAX}}
| Charset={{#var:REGISTRYDOMAINNAMECHARSET}}
| Limitations={{#var:CONTACTSLIMITATIONSENTENCE}}
| Transferclass={{#var:REGISTRYTRANSFERCLASS}}
| Transfer Period={{#var:ZONETRANSFERPERIODS}}
| Transfer Authcode required={{#var:REGISTRYTRANSFERREQUIREAUTHCODE}} {{#var:REGISTRYTRANSFERREQUIREAUTHCODEADDITION}}
| Transfer ACK by={{#var:REGISTRYTRANSFERACKBY}}
| Transfer NACK by={{#var:REGISTRYTRANSFERNACKBY}}
| Transfer Real-Time={{#var:REGISTRYTRANSFERREALTIME}}
| Transfer Lock={{#var:REGISTRYTRANSFERLOCK}}
| Transfer Pending Period={{#var:REGISTRYTRANSFERPENDINGPERIOD}}
| Transfer Expire Action={{#var:REGISTRYTRANSFEREXPIREACTION}}
| Transfer Confirmation={{#var:ZONEPOLICYDOMAINTRANSFERCONFIRMATION}}
| Transfer included={{#var:REGISTRYTRADETRANSFERINCLUDED}}
| Owner Change by={{#var:ZONEPOLICYREGISTRANTNAMECHANGEBY}}
| Trade Period={{#var:ZONETRADEPERIODS}}
| Trade Real-Time={{#var:REGISTRYTRADEREALTIME}}
| Trade Confirmation={{#var:ZONEPOLICYDOMAINTRADECONFIRMATION}}
| Trade ACK by={{#var:REGISTRYTRADEACKBY}}
| Trade NACK by={{#var:REGISTRYTRADENACKBY}}
| Nameservers={{#var:NAMESERVERMIN}} to {{#var:NAMESERVERMAX}}
| Nameserverchecks={{#var:REGISTRYNAMESERVERCHECKS}}
| Host IP-Adresses Type={{#var:HOSTIPADDRESSESTYPE}}
| Hosts managed as={{#var:HOSTMANAGEDAS}}
| Root DNS Update={{#var:REGISTRYNAMESERVERROOTUPDATE}}
| SEC DNS Interface={{#var:ZONESECDNSINTERFACE}}
}}

= Periods =
{{Summarybox
| Registration Period={{#var:ZONEREGISTRATIONPERIODS}}
| Add Grace Period={{#var:ZONEREGISTRATIONGRACEPERIOD}}
| Finalization Period={{#var:ZONERENEWALFINALIZATIONPERIOD}}
| Failure Period={{#var:ZONERENEWALFAILUREPERIOD}}
| Accounting Period={{#var:ZONERENEWALACCOUNTINGPERIOD}}
| Payment Period={{#var:ZONERENEWALPAYMENTPERIOD}}
| Deletion Restorable Period={{#var:DELETIONRESTORABLEPERIOD}}
| Deletion Hold Period={{#var:DELETIONHOLDPERIOD}}
| Explicit Renewal={{#var:REGISTRYEXPLICITRENEWAL}}
| Renewal Period={{#var:ZONERENEWALPERIODS}}
}}

= API =

=== Domain Registration ===
{{#var:REGISTRATIONSENTENCE}}
{{#var:ADDDOMAINCOMMAND}}
<span class="label label-important">REQUIRED</span>
<pre>
ownercontact0 = (CONTACT)
admincontact0 = (CONTACT)
techcontact0 = (CONTACT)
billingcontact0 = (CONTACT)
nameserver0 = (NAMESERVER)
nameserver1 = (NAMESERVER)
</pre>

<span class="label label-info">OPTIONAL</span>
<pre>
auth = (TEXT) | (NULL)
period = (PERIOD)
transferlock = 0 | 1 | (NULL)
</pre>

=== Domain Transfer ===
{{#var:TRANSFERSENTENCE}}
{{#var:TRANSFERDOMAINCOMMAND}}
<span class="label label-important">REQUIRED</span>
<pre>
auth = (TEXT)
</pre>

<span class="label label-info">OPTIONAL</span>
<pre>
period = (PERIOD)
transferlock = 0 | 1 | (NULL)
action = REQUEST | APPROVE | DENY | CANCEL | USERTRANSFER
</pre>

=== Delete Domain ===
{{#var:DELETESENTENCE}}
{{#var:DELETEDOMAINCOMMAND}}

=== Restore Domain ===
{{#var:RESTOREPOLICYSENTENCE}}
{{#var:RESTOREDOMAINCOMMAND}}

<span class="label label-info">OPTIONAL</span>
<pre>
subuser = (TEXT)
renewalmode = (NULL) | (TEXT)
</pre>

=== Ownerchange ===
{{#var:TRADESENTENCE}}
<pre>
command = ModifyDomain
domain = (DOMAIN)
</pre>

<span class="label label-important">REQUIRED</span>
<pre>
ownercontact0 = (CONTACT)
</pre>

= TLD specific =

=== 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:

*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:<br>
<pre>
command = ModifyDomain
domain = (DOMAIN)
</pre>

<span class="label label-important">REQUIRED</span>
<pre>
generaterandomauth = 1
</pre>

= Addons =

{{#var:DOMAINADDONTABLE}}

= RegistrarOC =

{{#var:REGISTRAROCSENTENCE}}

{{#var:CATEGORY}}