Misplaced Pages

Auth-Code: Difference between revisions

Article snapshot taken from[REDACTED] with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editNext edit →Content deleted Content addedVisualWikitext
Revision as of 18:41, 10 March 2007 editNick Levinson (talk | contribs)Extended confirmed users8,605 edits .com like .net for code; gTLDs yes, ccTLDs maybe; departures; & clean-up; edit of Feb15-07 mine← Previous edit Revision as of 19:11, 10 March 2007 edit undoNick Levinson (talk | contribs)Extended confirmed users8,605 editsm Edit posted Feb15 server-dated 16th, thus same.Next edit →
Line 5: Line 5:
The code supports transferring any domain in the above top-level domains from one ] to another. If the code is not provided, then those domains generally cannot be transferred. The code helps identify the domain name holder; it does not constitute transfer approval. The code supports transferring any domain in the above top-level domains from one ] to another. If the code is not provided, then those domains generally cannot be transferred. The code helps identify the domain name holder; it does not constitute transfer approval.


The transfer takes place within 10 days or less. The transfer should take place within 10 days, probably 5.


When getting a new registrar, locate the auth-info code and procedure early. Registrars may assume your only interest in the code is so you can take your business away, and might impede your getting your code when you have only a few days left before losing your domain. They might call the code something else (foiling searches), leave it off FAQs, and ignore your emails, and resellers may be even less helpful. Find out in the beginning and keep notes (at the risk that they'll change the method but at least you'll have a starting point). If they're uncooperative, maybe complain via <http://reports.internic.net/cgi/registrars/problem-report.cgi>. When getting a new registrar, locate the auth-info code and procedure early. Registrars may assume your only interest in the code is so you can take your business away, and might impede your getting your code when you have only a few days left before losing your domain. They might call the code something else (foiling searches), leave it off FAQs, and ignore your emails, and resellers may be even less helpful. Find out in the beginning and keep notes (at the risk that they'll change the method but at least you'll have a starting point). If they're uncooperative, maybe complain via <http://reports.internic.net/cgi/registrars/problem-report.cgi>.

Revision as of 19:11, 10 March 2007

Transfer Secret is a Domain Transfer Secret (Transfer Key), a key or code granted by all the registrars for various gTLDs and possibly some ccTLDs, including .COM and .net domains (for a while they didn't). Whether a ccTLD needs a code is generally up to the ccTLD's national authority.

The code is officially called an AuthInfo Code, an AuthInfo code, and an Auth-Info code by ICANN and registry operators. It is alternatively called an auth code by registrar Tucows, a transfer key, a transfer secret, and an EPP code.

The code supports transferring any domain in the above top-level domains from one Registrar to another. If the code is not provided, then those domains generally cannot be transferred. The code helps identify the domain name holder; it does not constitute transfer approval.

The transfer should take place within 10 days, probably 5.

When getting a new registrar, locate the auth-info code and procedure early. Registrars may assume your only interest in the code is so you can take your business away, and might impede your getting your code when you have only a few days left before losing your domain. They might call the code something else (foiling searches), leave it off FAQs, and ignore your emails, and resellers may be even less helpful. Find out in the beginning and keep notes (at the risk that they'll change the method but at least you'll have a starting point). If they're uncooperative, maybe complain via <http://reports.internic.net/cgi/registrars/problem-report.cgi>.

On ICANN oversight, see http://www.icann.org/transfers/policy-12jul04.htm, as accessed Feb. 8, 2007, especially §A5. Registry operators may have their own provisions in agreements with registrars; those agreements may be posted on operators' websites.


Stub icon

This Internet domain name article is a stub. You can help Misplaced Pages by expanding it.

Categories:
Auth-Code: Difference between revisions Add topic