CHANNEL - Revision history

WikiAdmin: /* .CHANNEL Extensions */

2024-05-07T06:29:03Z

‎.CHANNEL Extensions

WikiAdmin: /* .CHANNEL Extensions */

2024-05-07T06:28:16Z

‎.CHANNEL Extensions

WikiAdmin: /* .CHANNEL Extensions */

2024-05-07T06:26:22Z

‎.CHANNEL Extensions

Timo at 20:43, 22 August 2023

2023-08-22T20:43:33Z

Timo: Timo moved page .CHANNEL to CHANNEL

2023-08-22T20:41:11Z

Timo moved page .CHANNEL to CHANNEL

WikiAdmin at 13:42, 29 June 2023

2023-06-29T13:42:26Z

WikiAdmin at 12:34, 29 June 2023

2023-06-29T12:34:35Z

WikiAdmin: /* .CHANNEL Extensions */

2022-05-05T13:13:57Z

‎.CHANNEL Extensions

WikiAdmin: /* .CHANNEL Security Requirement Additional Information */

2022-05-05T13:11:44Z

‎.CHANNEL Security Requirement Additional Information

WikiAdmin at 13:07, 5 May 2022

2022-05-05T13:07:19Z

← Older revision		Revision as of 06:29, 7 May 2024
Line 186:		Line 186:


−	.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].	+	.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.		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.

← Older revision		Revision as of 06:28, 7 May 2024
Line 186:		Line 186:


−	.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 [~~link to registrar page on~~ SSL~~, or Let’s Encrypt~~].	+	.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].

	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.		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.

@@ Line 188: / Line 188: @@
 .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 [link to registrar page on SSL, or Let’s Encrypt].
-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 .app is inscribed, only forces encryption on HTTPS connections, thus, .app 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.
+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>

@@ Line 9: / Line 9: @@
 | legal = [https://policies.google.com/terms Registry Policies]
 }}
-{{#repositoryinfo:  CRR-LIVE-KEYSYS | new }}
+{{#repositoryinfo:  CRR-LIVE-1API | channel }}
 {{Sidebar}}
 <div style="font-size: 250%;">'''.CHANNEL'''</div><br/>

@@ Line 1: / Line 1: @@
 {{Infobox nTLD
 | name = .CHANNEL
-| image    =[[File: New.png|250px]]
+| image    =[[File: Channel.png|250px]]
 | introduced = 2019
 | category = Technology

← Older revision		Revision as of 12:34, 29 June 2023
Line 14:		Line 14:

	.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, 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.
		+
		+	<b>.CHANNEL Security Requirements</b>
		+
		+	.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.
		+
		+	<b>Important:</b> 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__		__TOC__

@@ Line 169: / Line 169: @@
 <pre>
 X-CHANNEL-ACCEPT-HIGHLY-REGULATED-TAC = 1
 </pre>

@@ Line 161: / Line 161: @@
 </pre>
-=== .CHANNEL Security Requirement Additional Information ===
+=== .CHANNEL Extensions ===
-Google Registry has added .new to the [https://hstspreload.org/ HSTS preload list], which means that all websites using this TLD will be encrypted by default and will not allow insecure connections. Registrants must configure HTTPS serving for their domains in order for them to work in all major browsers. That is, they need to configure an SSL certificate in order for their .new domain to function in browsers.
+.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.
-<b>Important:</b> Please note that upon registration, registrants of .new must be aware of the security requirement outlined above, including that:
+Registrants must explicitly acknowledge this security requirement using the following parameter:
-* .new is a secure namespace, and
-* HTTPS is required for all .new websites, as they will be encrypted by default and will not allow insecure connections
 <pre>
-X-ACCEPT-SSL-REQUIREMENT = 1
+X-CHANNEL-ACCEPT-HIGHLY-REGULATED-TAC = 1
 </pre>

@@ Line 13: / Line 13: @@
 <div style="font-size: 250%;">'''.CHANNEL'''</div><br/>
-.CHANNEL, brought to you by Google Registry, is available to all registrants but features usage restrictions. All .CHANNEL domains must be used for action generation or online content creation. Some examples of current use cases include Google's docs.new, sheets.new and slides.new domains that automatically open new documents in the chosen program. It is also a secure domain and requires HTTPS in web browsers.
+.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.
 __TOC__