imported>Ddmler: add email templates to alternative systems

2023-04-09T07:31:11Z

add email templates to alternative systems

New page

{{Short description|Randomly generated complex code}}
{{Redirect|EPP code|status codes|EPP status codes}}
An '''Auth-Code''',<ref name="icann-auth"/><ref name="icann-holder-faqs"/> also known as an '''EPP code''', '''authorization code''', '''transfer code''',<ref name="gandi-authinfo">{{cite web | url = https://docs.gandi.net/en/domain_names/transfer_out/auth_info.html | title = How to Find the Authorization Code (EPP Code) for a Transfer | location = Paris | publisher = [[Gandi.net|Gandi]] | work = Gandi.net Docs | accessdate = 2021-02-11 }}</ref> or '''Auth-Info Code''',<ref name="icann-auth"/> is a generated passcode required to [[domain name transfer|transfer an Internet domain name]] between [[domain registrar]]s; the code is intended to indicate that the [[domain name]] owner has authorized the transfer.<ref name="icann-holder-faqs">{{cite web | url = https://www.icann.org/resources/pages/name-holder-faqs-2017-10-10-en#:~:text=asking%20me%20for%20a%20code | title = FAQs for Registrants: Transferring Your Domain Name | publisher = [[Internet Corporation for Assigned Names and Numbers]] | accessdate = 2021-02-11 }}</ref>

Auth-Codes are created by the current registrar of the domain. The registrar is required to provide the Auth-Code to the domain name owner within five calendar days of the owner's request, and [[ICANN]] accepts complaints about registrars that do not. Some registrars allow Auth-Codes to be generated by the domain owners through the registrar's website. All [[Generic top-level domain|Generic top-level domains]] use an Auth-Code in their transfer process.<ref name="icann-auth">{{cite web | url = https://www.icann.org/resources/pages/auth-2013-05-03-en | title = About Auth-Code | publisher = [[Internet Corporation for Assigned Names and Numbers]] | accessdate = 2021-02-11 }}</ref>

The [[.nz]] domain registry used an eight-character Auth-Code called Unique Domain Authentication Identifier (UDAI) for domain transfers and name conflict procedures. The UDAI was provided to the domain owner by the domain's current registrar, and expired after 30 days.<ref>{{cite web |title=Check your UDAI |url=https://www.dnc.org.nz/udai |accessdate=2021-02-11 |publisher=[[Domain Name Commission]] Ltd |location=[[Wellington, New Zealand]]}}</ref><ref>{{cite web |title=More UDAI information |url=https://www.dnc.org.nz/udai-info |accessdate=2021-02-11 |publisher=[[Domain Name Commission]] Ltd |location=[[Wellington, New Zealand]]}}</ref> With the .nz registry update in 2022 the term UDAI was retired, and the passcode is now also referred to as an Auth-Code.<ref>{{Cite web |title=IRS General — InternetNZ Product Documentation 8.0a1 documentation |url=https://docs.internetnz.nz/registry/faq/irs/ |access-date=2023-04-09 |website=docs.internetnz.nz}}</ref>

==Alternative systems==
The [[.uk]] and [[.co.uk]] domain registry, instead of using a passcode, has the domain owner specify the new registrar using the old registrar.<ref name="gandi-authinfo"/><ref name="google-another">{{cite web | url = https://support.google.com/domains/answer/3251178?hl=en#co_uk | title = Transfer a domain to another registrar | work = Google Domains Help | publisher = Google Inc. | accessdate = 2021-02-11 }}</ref> The destination registrar is specified using the destination's registrar tag,<ref name="google-another"/> also known as an Internet Provider Security (IPS) tag or [[Nominet]] Provider tag.<ref name="gandi-authinfo"/>

Some registries use a document based approach either in conjunction with or instead of an Auth-Code. An example for that is [[.hu]] for which the registrant has to fill out a document and send it to the new registrar, who sends it to the registry to fulfill the domain transfer.<ref>{{Cite web |title=Document-based Domain Registration Procedures |url=https://www.domain.hu/document-based-domain-registration-procedures/ |access-date=2023-04-09 |website=Domain.hu |language=en-GB}}</ref>

The [[.is]] domain registry uses the domains admin [[NIC handle]] and the old registrar has to update it to the new registrars NIC handle.<ref>{{Cite web |title=ISNIC Registry: ISNIC EPP Interface Specification |url=https://www.isnic.is/en/epp#transfer |access-date=2023-04-09 |website=www.isnic.is}}</ref>

Some other registries use an email template (that may or may not be in part processed automatically) like [[.lr]] or [[.jm]]. In this case the technical contact is set to the registrar and can be updated by sending an updated template from the registrant or admin contacts email address.<ref>{{Cite web |title=.lr domain template |url=https://psg.com/dns/lr/lr.txt|access-date=2023-04-09}}</ref><ref>{{Cite web |title=.jm domain template |url=https://www.mona.uwi.edu/mits/sites/default/files/mits/domain_name_form.txt|access-date=2023-04-09}}</ref>

==See also==
* [[Domain lock]] — another attribute of a domain registration to prevent unauthorized domain transfers and other [[domain name scams]]
* [[Extensible Provisioning Protocol]] (EPP) — protocol used by a large number of [[domain registry|domain registries]] and registrars to communicate domain changes

==References==
{{reflist}}

[[Category:Computer access control]]
[[Category:Domain Name System]]

Auth-Code - Revision history

imported>Ddmler: add email templates to alternative systems