Sro7xw: 1 revision imported

2025-03-14T10:56:15Z

1 revision imported

← Older revision	Revision as of 11:56, 14 March 2025
(No difference)

local>ImportBot: Imported from old wiki

2025-01-01T12:00:00Z

Imported from old wiki

New page

{{Infobox nTLD
| name = .CHANNEL
| image =[[File: Channel.png|250px]]
| introduced = 2019
| category = Technology
| registry = Google Registry
| idn capable = Yes
| webpage = [https://www.hexonet.net/ Register .CHANNEL]
| legal = [https://policies.google.com/terms Registry Policies]
}}
{{#repositoryinfo: CRR-LIVE-1API | channel }}
{{Sidebar}}
<div style="font-size: 250%;">'''.CHANNEL'''</div> 

.CHANNEL, brought to you by Google Registry, is exclusively for content creators and publishers to monetise their content. All .channel domains must present the user with a website where the creator can monetise their content or audience. No other use cases are allowed.

.CHANNEL Security Requirements

.CHANNEL is a secured namespace, meaning that websites using a .CHANNEL domain require an SSL certificate to work; .CHANNEL websites can only be accessed by web browsers using HTTPS through an encrypted and secured connection.

SSL certificates may be purchased through the HEXONET Control Panel or via API. More information on SSL certificates, including purchasing and obtaining certificates and API documentation, may be found [https://wiki.hexonet.net/wiki/SSL here].

.CHANNEL domain names that do not have an SSL certificate configured may still be used for email and other non-browser based uses.

Important: Please note that upon registration, registrants of .CHANNEL must be aware of this security requirement, including that:
* .CHANNEL is a secure namespace, and
* HTTPS is required for all .CHANNEL websites, as they will be encrypted by default and will not allow insecure connections

Additionally, registrants must be provided with resources about configuring HTTPS and obtaining an SSL certificate for their domain.

__TOC__

= 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}}
REQUIRED
<pre>
ownercontact0 = (CONTACT)
admincontact0 = (CONTACT)
techcontact0 = (CONTACT)
billingcontact0 = (CONTACT)
nameserver0 = (NAMESERVER)
nameserver1 = (NAMESERVER)

</pre>

OPTIONAL
<pre>
auth = (TEXT) | (NULL)
period = (PERIOD)
transferlock = 0 | 1 | (NULL)
</pre>

=== Domain Transfer ===
{{#var:TRANSFERSENTENCE}}
{{#var:TRANSFERDOMAINCOMMAND}}
REQUIRED
<pre>
auth = (TEXT)
</pre>

OPTIONAL
<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}}

OPTIONAL
<pre>
subuser = (TEXT)
renewalmode = (NULL) | (TEXT)
</pre>

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

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

REQUIRED
<pre>
generaterandomauth = 1
</pre>

=== .CHANNEL Extensions ===

.channel is exclusively for content creators and publishers to monetise their content. All .channel domains must present the user with a website where the creator can monetise their content or audience. No other use cases are allowed. By registering a .channel domain, you agree to follow the .channel Registration Policy. Please visit https://www.registry.google/policies/registration/channel/ for the full policy.

Registrants must explicitly acknowledge this security requirement using the following parameter:

<pre>
X-CHANNEL-ACCEPT-HIGHLY-REGULATED-TAC = 1
</pre>

.channel is a more secure domain, meaning that HTTPS is required for all .channel websites. You can buy your .channel domain name now, but in order for it to work properly in browsers you must first configure HTTPS serving. Â For more information about configuring HTTPS, including resources to obtain an SSL certificate, please visit [https://wiki.hexonet.net/wiki/SSL Hexonet SSL].

Please note: The SSL requirement is enforced at the browser level, so there is no mandated order of purchase. The HSTS Preload list, to which .channel is inscribed, only forces encryption on HTTPS connections, thus, .channel domain names that do not have an SSL certificate configured may still be used for other services like e-mail and non-browser based uses such as defensive registrations.

<pre>
X-ACCEPT-SSL-REQUIREMENT = 1
</pre>

= RegistrarOC =

{{#var:REGISTRAROCSENTENCE}}

{{#var:CATEGORY}}

CHANNEL - Revision history

Sro7xw: 1 revision imported

local>ImportBot: Imported from old wiki