SE - Revision history

WikiAdmin: /* Authorization Code */

2024-06-28T08:15:11Z

‎Authorization Code

2024-06-05T13:39:41Z

‎Authorization Code

2024-06-05T13:35:01Z

‎Authorization Code

2024-06-04T21:57:45Z

‎TLD specific

2024-03-22T09:11:27Z

2024-03-01T12:08:07Z

‎Ownerchange

2024-02-23T08:39:14Z

2024-02-23T08:38:38Z

2024-02-23T08:38:03Z

TLD Specific - Contact Verification

2023-11-28T20:17:24Z

‎Deletion

@@ Line 243: / Line 243: @@
 === Authorization Code ===
 As of June 1, 2024, it will no longer be possible to set an authorization code manually. All auth codes are set by the registry.
-To retrieve the auth code, please use the ModidyDomain command with a random auth code. The registry will then respond with the current authorization code.
+To retrieve the auth code, please use the ModifyDomain command with a random auth code. The registry will then respond with the current authorization code.

← Older revision		Revision as of 13:39, 5 June 2024
Line 245:		Line 245:
	To retrieve the auth code, please use the ModidyDomain command with a random auth code. The registry will then respond with the current authorization code.		To retrieve the auth code, please use the ModidyDomain command with a random auth code. The registry will then respond with the current authorization code.

−	~~The authorisation code includes a total of 16 letters and digits separated by dashes, in the following format:~~
−
−	~~XXXX-AAAA-BBBB-CCCC~~

	It will '''''be valid for 14 days''''' by requesting a new authorization code. You can generate a new authcode by removing the domain transfer lock.		It will '''''be valid for 14 days''''' by requesting a new authorization code. You can generate a new authcode by removing the domain transfer lock.

← Older revision		Revision as of 13:35, 5 June 2024
Line 242:		Line 242:

	=== Authorization Code ===		=== Authorization Code ===
		+	As of June 1, 2024, it will no longer be possible to set an authorization code manually. All auth codes are set by the registry.
		+	To retrieve the auth code, please use the ModidyDomain command with a random auth code. The registry will then respond with the current authorization code.
		+
	The authorisation code includes a total of 16 letters and digits separated by dashes, in the following format:		The authorisation code includes a total of 16 letters and digits separated by dashes, in the following format:

← Older revision		Revision as of 21:57, 4 June 2024
Line 248:		Line 248:
	It will '''''be valid for 14 days''''' by requesting a new authorization code. You can generate a new authcode by removing the domain transfer lock.		It will '''''be valid for 14 days''''' by requesting a new authorization code. You can generate a new authcode by removing the domain transfer lock.

		+	=== OTE TLD is not .SE ===
		+	.TEST is the TLD that IIS uses in their test platform. .SE is not accepted but .TEST is.

	= Addons =		= Addons =

@@ Line 240: / Line 240: @@
 === Deletion ===
 Please note, that the registry will send an invoice to the owner of a domain providing him the possibility to pay the renewal fee directly to the registry. If the invoice is not paid to NIC.se the domain will be finally deleted. If the registrant doesn't want the registry to send an invoice, they have to send a completed [[Media:Form_se_termination.pdf|Termination Fax]] directly to [http://www.iis.se/ NIC.se].
 = Addons =

← Older revision		Revision as of 08:39, 23 February 2024
Line 167:		Line 167:

	{{Warnbox\| Starting March 1st 2024, we will introduce Contact Verification to validate the Registrant Contact Information. [https://wiki.hexonet.net/wiki/Registrant_Verification Registrant Verification]}}		{{Warnbox\| Starting March 1st 2024, we will introduce Contact Verification to validate the Registrant Contact Information. [https://wiki.hexonet.net/wiki/Registrant_Verification Registrant Verification]}}
−
	'''Some special parameters have to be specified:'''		'''Some special parameters have to be specified:'''

← Older revision		Revision as of 08:38, 23 February 2024
Line 167:		Line 167:

	{{Warnbox\| Starting March 1st 2024, we will introduce Contact Verification to validate the Registrant Contact Information. [https://wiki.hexonet.net/wiki/Registrant_Verification Registrant Verification]}}		{{Warnbox\| Starting March 1st 2024, we will introduce Contact Verification to validate the Registrant Contact Information. [https://wiki.hexonet.net/wiki/Registrant_Verification Registrant Verification]}}
−

	'''Some special parameters have to be specified:'''		'''Some special parameters have to be specified:'''

← Older revision		Revision as of 08:38, 23 February 2024
Line 165:		Line 165:

	=== Registration ===		=== Registration ===
		+
		+	{{Warnbox\| Starting March 1st 2024, we will introduce Contact Verification to validate the Registrant Contact Information. [https://wiki.hexonet.net/wiki/Registrant_Verification Registrant Verification]}}
		+
		+
	'''Some special parameters have to be specified:'''		'''Some special parameters have to be specified:'''

@@ Line 237: / Line 237: @@
 === Deletion ===
-Please note, that the registry will send an invoice to the owner of a domain providing him the possibility to pay the renewal fee directly to the registry. If the invoice is not paid to NIC.se the domain will be finally deleted. If you don't want the registry to send an invoice you have to send the respective [[Media:Form_se_termination.pdf|Termination Fax]] directly to [http://www.iis.se/ NIC.se].
+Please note, that the registry will send an invoice to the owner of a domain providing him the possibility to pay the renewal fee directly to the registry. If the invoice is not paid to NIC.se the domain will be finally deleted. If the registrant doesn't want the registry to send an invoice, they have to send a completed [[Media:Form_se_termination.pdf|Termination Fax]] directly to [http://www.iis.se/ NIC.se].
 === Ownerchange ===