CHANNEL
- Domains
- Main_Page|All Domains
- NewTLD_Main_Page| NewTLDs
- Premium_Domains_Main_Page| Premium Domains
- Services
- Registry_Lock|Registry Lock
- Trademark_Clearinghouse|Trademark Clearinghouse
- Early_Access_Program|Early Access Program (EAP)
- DPML|DPML
- Backorder|Backorder
- EOI_API|EOI Service
- Web_Apps|Web Apps
- RegistrarOC|RegistrarOC
- AdultBlock|AdultBlock
- AUValidation|.AU Validation Service for Natural Persons
- API & SDK
- Domain_API|Domain API
- DNS_API|DNS API
- DNSSEC|DNSSEC API
- SSL|SSL API
- Weebly API|Weebly API
- RootServer|Rootserver API
- Renewal_System|Renewal System API
- Core_API|System API
- EPP_Gateway|EPP Gateway
- https://www.hexonet.net/resellers/integration#api%7CSDKs
- Modules & Tools
- https://www.hexonet.net/resellers/integration#whmcs%7CWHMCS modules
- https://www.hexonet.net/resellers/integration#blesta%7CBlesta modules
- ISPAPI | ISPAPI Command-line interface
- Control Panel & Tools
- ControlPanel | Control Panel
- ICANN Policies
- IRTP|IRTP - Change of Registrant Policy
- ERRP| ERRP - Expired Domain Recovery Policy
- Registrant_Verification|Registrant Verification
- HEXONET & Partners
.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 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.
Registry[edit]
| .CHANNEL | |
| File:Channel.png | |
| Overview | |
| Introduced | 2019 |
|---|---|
| Category | Technology |
| Registry | Google Registry |
| IDN Capable | Yes |
| Dispute Policy | ICANN Rules |
| Webpage | Register .CHANNEL |
| Legal Information | |
| Legal | Registry Policies |
| 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}} |
| Min. Characters |
{{#var:REGISTRYCHARSMIN}} |
| Max. Characters |
{{#var:REGISTRYCHARSMAX}} |
| Character Set |
{{#var:REGISTRYDOMAINNAMECHARSET}} |
| Limitations |
{{#var:CONTACTSLIMITATIONSENTENCE}} |
| IDN capable |
{{#var:REGISTRYIDNCAPABLE}} |
| Restore capable |
{{#var:RESTOREPOLICY}} |
| Handle Updates |
{{#var:REGISTRYHANDLEUPDATE}} |
| Registration System |
{{#var:REGISTRYREGISTRATIONSYSTEM}} |
| Allowed number of NS |
{{#var:NAMESERVERMIN}} to {{#var:NAMESERVERMAX}} |
| Registry Nameservercheck |
{{#var:REGISTRYNAMESERVERCHECKS}} |
| Host IP-Addresses Type |
{{#var:HOSTIPADDRESSESTYPE}} |
| Hosts managed as |
{{#var:HOSTMANAGEDAS}} |
| Root Nameserver Update |
{{#var:REGISTRYNAMESERVERROOTUPDATE}} |
| SEC DNS Interface |
{{#var:ZONESECDNSINTERFACE}} |
| Transferclass |
{{#var:REGISTRYTRANSFERCLASS}} |
| Transfer Periods |
{{#var:ZONETRANSFERPERIODS}} |
| Transfer Authcode required |
{{#var:REGISTRYTRANSFERREQUIREAUTHCODE}} {{#var:REGISTRYTRANSFERREQUIREAUTHCODEADDITION}} |
| Transfer Real-Time |
{{#var:REGISTRYTRANSFERREALTIME}} |
| Transfer Lock |
{{#var:REGISTRYTRANSFERLOCK}} |
| Transfer Confirmation (Request / Approve) |
{{#var:ZONEPOLICYDOMAINTRANSFERCONFIRMATION}} |
| Owner Change by |
{{#var:ZONEPOLICYREGISTRANTNAMECHANGEBY}} |
| Trade Real-Time |
{{#var:REGISTRYTRADEREALTIME}} |
| Trade Periods |
{{#var:ZONETRADEPERIODS}} |
| Transfer included |
{{#var:REGISTRYTRADETRANSFERINCLUDED}} |
| Trade Confirmation (Request / Approve) |
{{#var:ZONEPOLICYDOMAINTRADECONFIRMATION}} |
| Trade ACK by |
{{#var:REGISTRYTRADEACKBY}} |
| Trade NACK by |
{{#var:REGISTRYTRADENACKBY}} |
Periods[edit]
| Registration Periods |
{{#var:ZONEREGISTRATIONPERIODS}} |
| Add Grace Period |
{{#var:ZONEREGISTRATIONGRACEPERIOD}} |
| Accounting Period |
{{#var:ZONERENEWALACCOUNTINGPERIOD}} |
| Finalization Period |
{{#var:ZONERENEWALFINALIZATIONPERIOD}} |
| Failure Period |
{{#var:ZONERENEWALFAILUREPERIOD}} |
| Payment Period |
{{#var:ZONERENEWALPAYMENTPERIOD}} |
| Deletion Restorable Period |
{{#var:DELETIONRESTORABLEPERIOD}} |
| Deletion Hold Period |
{{#var:DELETIONHOLDPERIOD}} |
| Explicit Renewals |
{{#var:REGISTRYEXPLICITRENEWAL}} |
| Renewal Periods |
{{#var:ZONERENEWALPERIODS}} |
API[edit]
Domain Registration[edit]
{{#var:REGISTRATIONSENTENCE}} {{#var:ADDDOMAINCOMMAND}} REQUIRED
ownercontact0 = (CONTACT) admincontact0 = (CONTACT) techcontact0 = (CONTACT) billingcontact0 = (CONTACT) nameserver0 = (NAMESERVER) nameserver1 = (NAMESERVER)
OPTIONAL
auth = (TEXT) | (NULL) period = (PERIOD) transferlock = 0 | 1 | (NULL)
Domain Transfer[edit]
{{#var:TRANSFERSENTENCE}} {{#var:TRANSFERDOMAINCOMMAND}} REQUIRED
auth = (TEXT)
OPTIONAL
period = (PERIOD) transferlock = 0 | 1 | (NULL) action = REQUEST | APPROVE | DENY | CANCEL | USERTRANSFER
Delete Domain[edit]
{{#var:DELETESENTENCE}} {{#var:DELETEDOMAINCOMMAND}}
Restore Domain[edit]
{{#var:RESTOREPOLICYSENTENCE}} {{#var:RESTOREDOMAINCOMMAND}}
OPTIONAL
subuser = (TEXT) renewalmode = (NULL) | (TEXT)
Ownerchange[edit]
{{#var:TRADESENTENCE}}
command = ModifyDomain domain = (DOMAIN)
REQUIRED
ownercontact0 = (CONTACT)
TLD specific[edit]
Authorization code[edit]
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
.CHANNEL Extensions[edit]
.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:
X-CHANNEL-ACCEPT-HIGHLY-REGULATED-TAC = 1
.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 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.
X-ACCEPT-SSL-REQUIREMENT = 1
RegistrarOC[edit]
{{#var:REGISTRAROCSENTENCE}}
{{#var:CATEGORY}}