.tf Domain TLD Registration Transfer Information

.tf Domain

.tf is the Internet country code top-level domain (ccTLD) for the French Southern and Antarctic Lands. Along with .fr, .nc, .pm, .re, .wf and .yt it is administered by AFNIC. Before October 23, 2004, Adamsnames, based in Cambridge, administered this TLD.

The French Southern and Antarctic Lands are territories either recognised as French or claimed but suspended under the Antarctic Treaty System France, and the domain name derives from the French, Terres australes et antarctiques françaises. Part of the French claim includes a section of the continent of Antarctica, creating an overlap between .tf and the general Antarctica domain .aq.

The .tf domain-name has popular usage for sites related to the game Team Fortress 2. Many of these sites are commonly used for marketing of virtual goods originating from Team Fortress 2 and, by extension, the Steam Community Market. Examples of these sites are backpack.tf, scrap.tf, and marketplace.tf which all facilitate trade relating to TF2 items and goods.

This text was written in the article .tf on Wikipedia and is available under the GNU Free Documentation License. A List of the authors is available on Wikipedia.

Available Suffixes

Registrations on second level (e.g. domain.tf): yes

Useful information

Whois Server whois.nic.tf

Contact Requirements

Available Types:

Owner has to be Person or Org

Owner has to fill the following fields:

CompanyNumber if country is fr and type is org
CountryOfBirth if type is person
DateOfBirth if type is person
PlaceOfBirth if CountryOfBirth is fr and type is person
PlaceOfBirthPostalCode if CountryOfBirth is fr and type is person
VatId if country is at, be, bg, hr, cy, cz, dk, ee, fi, de, gb, gr, hu, ie, it, lt, lu, mt, nl, pl, pt, ro, sk, si, es, se and type is org
For contacts in Australia the state field must contain the code of the state or territory. (ACT, NSW, NT, QLD, SA, TAS, VIC, WA)
See https://en.wikipedia.org/wiki/ISO_3166-2:AU
For contacts in Brazil the state field must contain the code of the state. (AC, AL, AP, AM, BA, CE, DF, ES, GO, MA, MT, MS, MG, PA, PB, PR, PE, PI, RJ, RN, RS, RO, RR, SC, SP, SE, TO)
See https://en.wikipedia.org/wiki/ISO_3166-2:BR
For contacts in Canada the state field must contain the code of the province or territory. (AB, BC, MB, NB, NL, NS, ON, PE, QC, SK, NT, NU, YT)
See https://en.wikipedia.org/wiki/ISO_3166-2:CA
For contacts in United Kingdom the state field must contain the code of the county. (ABC, ABD, ABE, AGB, AGY, AND, ...)
See https://en.wikipedia.org/wiki/ISO_3166-2:GB
For contacts in Ireland the state field must contain the code of the county. (CW, CN, CE, CO, DL, D, G, KY, KE, KK, LS, LM,LK, LD, LH, MO, MH, MN, OY, RN, SO, TA, WD, WH, WX, WW)
See https://en.wikipedia.org/wiki/ISO_3166-2:IE
For contacts in Italy the state field must contain the code of the province. (AG, AL, AN, AP, AQ, AR, AT, AV, BA, BG, BI, BL, ...)
See https://en.wikipedia.org/wiki/ISO_3166-2:IT
For contacts in Japan the state field must contain the code of the prefectures. (01, 02, ..., 47)
See https://en.wikipedia.org/wiki/ISO_3166-2:JP
For contacts in Mexico the state field must contain the code of the state. (AGU, BCN, BCS, CAM, CHH, CHP, CMX, COA, COL, DUR, ...)
See https://en.wikipedia.org/wiki/ISO_3166-2:MX
For contacts in United States the state field must contain the code of the state. (AL, AK, AZ, AR, CA, CO, CT, ...)
See https://en.wikipedia.org/wiki/ISO_3166-2:US
The name of a contact must consist of two words.
The city name may not contain '(', ')', '[', ']', '_', '=', '+' '"' or '~'.

Admin has to fill the following fields:

For contacts in Australia the state field must contain the code of the state or territory. (ACT, NSW, NT, QLD, SA, TAS, VIC, WA)
See https://en.wikipedia.org/wiki/ISO_3166-2:AU
For contacts in Brazil the state field must contain the code of the state. (AC, AL, AP, AM, BA, CE, DF, ES, GO, MA, MT, MS, MG, PA, PB, PR, PE, PI, RJ, RN, RS, RO, RR, SC, SP, SE, TO)
See https://en.wikipedia.org/wiki/ISO_3166-2:BR
For contacts in Canada the state field must contain the code of the province or territory. (AB, BC, MB, NB, NL, NS, ON, PE, QC, SK, NT, NU, YT)
See https://en.wikipedia.org/wiki/ISO_3166-2:CA
For contacts in United Kingdom the state field must contain the code of the county. (ABC, ABD, ABE, AGB, AGY, AND, ...)
See https://en.wikipedia.org/wiki/ISO_3166-2:GB
For contacts in Ireland the state field must contain the code of the county. (CW, CN, CE, CO, DL, D, G, KY, KE, KK, LS, LM,LK, LD, LH, MO, MH, MN, OY, RN, SO, TA, WD, WH, WX, WW)
See https://en.wikipedia.org/wiki/ISO_3166-2:IE
For contacts in Italy the state field must contain the code of the province. (AG, AL, AN, AP, AQ, AR, AT, AV, BA, BG, BI, BL, ...)
See https://en.wikipedia.org/wiki/ISO_3166-2:IT
For contacts in Japan the state field must contain the code of the prefectures. (01, 02, ..., 47)
See https://en.wikipedia.org/wiki/ISO_3166-2:JP
For contacts in Mexico the state field must contain the code of the state. (AGU, BCN, BCS, CAM, CHH, CHP, CMX, COA, COL, DUR, ...)
See https://en.wikipedia.org/wiki/ISO_3166-2:MX
For contacts in United States the state field must contain the code of the state. (AL, AK, AZ, AR, CA, CO, CT, ...)
See https://en.wikipedia.org/wiki/ISO_3166-2:US
The name of a contact must consist of two words.
The city name may not contain '(', ')', '[', ']', '_', '=', '+' '"' or '~'.

Tech has to fill the following fields:

For contacts in Australia the state field must contain the code of the state or territory. (ACT, NSW, NT, QLD, SA, TAS, VIC, WA)
See https://en.wikipedia.org/wiki/ISO_3166-2:AU
For contacts in Brazil the state field must contain the code of the state. (AC, AL, AP, AM, BA, CE, DF, ES, GO, MA, MT, MS, MG, PA, PB, PR, PE, PI, RJ, RN, RS, RO, RR, SC, SP, SE, TO)
See https://en.wikipedia.org/wiki/ISO_3166-2:BR
For contacts in Canada the state field must contain the code of the province or territory. (AB, BC, MB, NB, NL, NS, ON, PE, QC, SK, NT, NU, YT)
See https://en.wikipedia.org/wiki/ISO_3166-2:CA
For contacts in United Kingdom the state field must contain the code of the county. (ABC, ABD, ABE, AGB, AGY, AND, ...)
See https://en.wikipedia.org/wiki/ISO_3166-2:GB
For contacts in Ireland the state field must contain the code of the county. (CW, CN, CE, CO, DL, D, G, KY, KE, KK, LS, LM,LK, LD, LH, MO, MH, MN, OY, RN, SO, TA, WD, WH, WX, WW)
See https://en.wikipedia.org/wiki/ISO_3166-2:IE
For contacts in Italy the state field must contain the code of the province. (AG, AL, AN, AP, AQ, AR, AT, AV, BA, BG, BI, BL, ...)
See https://en.wikipedia.org/wiki/ISO_3166-2:IT
For contacts in Japan the state field must contain the code of the prefectures. (01, 02, ..., 47)
See https://en.wikipedia.org/wiki/ISO_3166-2:JP
For contacts in Mexico the state field must contain the code of the state. (AGU, BCN, BCS, CAM, CHH, CHP, CMX, COA, COL, DUR, ...)
See https://en.wikipedia.org/wiki/ISO_3166-2:MX
For contacts in United States the state field must contain the code of the state. (AL, AK, AZ, AR, CA, CO, CT, ...)
See https://en.wikipedia.org/wiki/ISO_3166-2:US
The name of a contact must consist of two words.
The city name may not contain '(', ')', '[', ']', '_', '=', '+' '"' or '~'.

Zone has to fill the following fields:

For contacts in Australia the state field must contain the code of the state or territory. (ACT, NSW, NT, QLD, SA, TAS, VIC, WA)
See https://en.wikipedia.org/wiki/ISO_3166-2:AU
For contacts in Brazil the state field must contain the code of the state. (AC, AL, AP, AM, BA, CE, DF, ES, GO, MA, MT, MS, MG, PA, PB, PR, PE, PI, RJ, RN, RS, RO, RR, SC, SP, SE, TO)
See https://en.wikipedia.org/wiki/ISO_3166-2:BR
For contacts in Canada the state field must contain the code of the province or territory. (AB, BC, MB, NB, NL, NS, ON, PE, QC, SK, NT, NU, YT)
See https://en.wikipedia.org/wiki/ISO_3166-2:CA
For contacts in United Kingdom the state field must contain the code of the county. (ABC, ABD, ABE, AGB, AGY, AND, ...)
See https://en.wikipedia.org/wiki/ISO_3166-2:GB
For contacts in Ireland the state field must contain the code of the county. (CW, CN, CE, CO, DL, D, G, KY, KE, KK, LS, LM,LK, LD, LH, MO, MH, MN, OY, RN, SO, TA, WD, WH, WX, WW)
See https://en.wikipedia.org/wiki/ISO_3166-2:IE
For contacts in Italy the state field must contain the code of the province. (AG, AL, AN, AP, AQ, AR, AT, AV, BA, BG, BI, BL, ...)
See https://en.wikipedia.org/wiki/ISO_3166-2:IT
For contacts in Japan the state field must contain the code of the prefectures. (01, 02, ..., 47)
See https://en.wikipedia.org/wiki/ISO_3166-2:JP
For contacts in Mexico the state field must contain the code of the state. (AGU, BCN, BCS, CAM, CHH, CHP, CMX, COA, COL, DUR, ...)
See https://en.wikipedia.org/wiki/ISO_3166-2:MX
For contacts in United States the state field must contain the code of the state. (AL, AK, AZ, AR, CA, CO, CT, ...)
See https://en.wikipedia.org/wiki/ISO_3166-2:US
The name of a contact must consist of two words.
The city name may not contain '(', ')', '[', ']', '_', '=', '+' '"' or '~'.

Transfer

The transfer has to be initiated through our system. A valid Authorization Code has to be provided to initiate a transfer successfully. You may obtain the authorization code from the old registrar. Normally a transfer will be completed in 8 days. After a transfer, our system syncronizes the owner of the domain from the registry to our system. If possible, you can start an owner change if you want to replace the synced owner.

Ownerchange

An Ownerchange may produce costs. Please refer to your pricelist. The Ownerchange can be started easily in our system. The old Owner and new Owner will receive an email from the registry and they have to confirm the Ownerchange. An Ownerchange will reset the payed period and the domain will be renewed immediately for one year.

Nameserver

check: yes
IP-Types: IPv4/IPv6
DNSSEC: yes
min. Nameserver: 2
max. Nameserver: 13

Restore

A Restore is not supported by the registry.