DOCUMENT LAYOUT

I.General provisions
II.Guiding principles for naming
III.Administrative operations
IV.Procedural guide

I - GENERAL PROVISIONS

1. INTRODUCTION

1. The Charter of the Association Française pour le Nommage Internet en Coopération (French Network Information Center), hereafter referred to as the "Naming Charter", is a consensual document whose aim is to ensure that domain names in the ".fr" zone are managed through agreement, for the benefit of all parties.

2. The Naming Charter is drawn up according to decisions taken by the relevant authorities within the AFNIC, working together with the "concertation committees" making up the organisation.

3. Consequently, the Naming Charter is an evolving document, resulting from the deliberations, work and agreements made by the AFNIC's members and partners.

4. Within the Naming Charter, the following terms will be defined as follows:

• "AFNIC": Association Française pour le Nommage Internet en Coopération (French Network Information Center), an association governed by the law of 1 July 1901 and the decree of 16 August 1901, to which the responsibility of administering the ".fr" Internet naming zone is delegated. The statutes and mission statement of the AFNIC are available on its website.
  
  
• "Naming Charter": The Charter is made up of the present document and the Procedural Guide. It is completed by a set of documents and information available on-line at the AFNIC website or directly from the association on request.
  
  
• "Internet Service Provider (ISP)": Technical service provider having signed a membership agreement with the AFNIC, in charge of processing the requests of its clients (the requesting bodies) in terms of domain name administration. List of ISPs.
  
  
• "Requesting body": Any natural person or legal entity requesting an administrative operation on a domain name, via an ISP who is a member of the AFNIC.
  
  
• "Administrative operation": Any administrative or technical operation relating to a domain name, based on requests and documents presented by ISPs. Examples are operations such as, but not limited to, Creation, Modification, Maintenance, Transmission, Transferring to another ISP, Removal, etc. of a domain name.
  
  
• "Procedural Guide": Document setting out all the technical details relating to carrying out an administrative operation on a domain name.
  
  
• "Nom de domaine orphelin" ("orphaned domain name") : The ISP is not managing a domain name any more, or the ISP has not signed the agreement with AFNIC again, or Its activity is not domain name anymore.

2. CONDITIONS OF ".FR" ACCESS

5. The enforceable version of the Naming Charter is the one available on the AFNIC website on the day that the AFNIC receives a request for an administrative operation from an ISP. Unless otherwise specified, new rules cannot be applied retroactively.

6. The Naming Charter only applies to domain names in the ".fr" naming zone.

7. A domain name within the ".fr" naming zone can be attributed to any requesting body officially registered in France or to any natural person living in France or of French nationality, within the provisions of the present Charter.

8. The attribution of a domain name grants the right to use the name to the requesting body and not to the ISP.

9. The ISP is the link between the AFNIC and the requesting body.

10. The technical relationship established between the AFNIC and the ISP within the framework of an administrative operation on a domain name is organised in accordance with the Naming Charter and put into practice by applying the Procedural Guide available on the AFNIC website.

11. Requesting Bodies must apply to an ISP for all types of administrative operation.

12. In particular, the ISP is responsible for:

• gathering all supporting documentation and information relating to a request for an administrative operation;
• checking the validity of the supporting documentation and information;
• following the instructions in the Procedural Guide.
• the ISP has a special responsibility to inform its clients, the requesting bodies, of any change or development affecting it (development or closure of the company, collective proceedings etc.) that could have an impact on the proper management of the domain names of the requesting bodies.

13. The requesting body must:

• Read and accept the terms of the present Charter;
• Verify that the request, and in particular the choice of wording to be used for the domain name:
  • Is legal in the eyes of the law and in particular the rules on public order,
  • Does not infringe the rights of third parties, such as (but not limited to) copyright, trademarks, human rights etc.
  • Complies with the provisions of the present Charter.
• Supply the ISP with the supporting documentation required as specified in the present Charter.
• Ensure that the information supplied to the ISP is correct and undertake to bring it up to date if necessary.

14. The requesting body has sole responsibility for documents, information and requests addressed to the ISP. The ISP is responsible for the proper forwarding of these documents to the AFNIC and for proper data entry within the framework of an administrative operation on a domain name. The requesting body must contact the ISP with any question or complaint regarding the request.

15. AFNIC domain names database has been declared to the CNIL (the National Commission For Informatics and Freedom).

16. The customer has a right to modify each personal information in accordance to the "Informatique et Libertйs" law of 6th january 1978.

17. The AFNIC is in no way responsible for verifying the contents, conformity or legality of supporting documentation submitted or communicated to it, insofar as these documents or details are approved or drafted by third parties (the clerk of the commercial court, the INPI (patent and trademark office), the préfecture (regional government), etc.).

18. The AFNIC does not research prior claims to domain names, but remains the guardian of the proper application of the Naming Charter. In this capacity, it will suspend any administrative operation requested on a domain name if the documents and/or information submitted do not comply with the provisions of the Naming Charter, but is not obliged to do so.

19. The AFNIC also reserves the right to suspend any domain name or request for an administrative operation in any case in which the provisions of the Naming Charter have not been respected or have been avoided, but is under no obligation to do so.

20. The right to use a domain name is dependent on the payment of an annual maintenance fee.

21. During the period of operation of a domain name, this maintenance fee is due from the most recent ISP responsible for the domain name, one year after the last fee-incurring administrative operation.

22. The administrative operations defined in the present document (section III) are invoiced to the ISP that requested them.

3. PRACTICAL PROVISIONS

23. The Naming Charter may be consulted at any time on the AFNIC website.

24. The Naming Charter is also available in the following format:

• Adobe PDF [.pdf]

25. To obtain a list of the most recently attributed domain names, the requesting body or the ISP can consult the AFNIC website.

26. For any other information, it is advisable to contact the appropriate attribution organisations, a list of which is available on the AFNIC website.

II - GUIDING PRINCIPLES FOR NAMING

1. DIVISIONS OF THE NAMING ZONE

1. The ".fr" naming zone is broken down into the following categories:

The "Public Domain"

This domain name category is directly organised and administered by the AFNIC.

It consists of the following extensions: ".fr", ".asso.fr", ".com.fr", ".nom.fr", ".prd.fr", ".presse.fr" and ".tm.fr".

This category is regulated according to the terms of the present Charter.

The "Sector-based Domain"

This domain name category identifies sectors of professional activity, and gives them a uniform structure.

It corresponds to sectors of activity regulated by a particular authority (e.g. professional associations, regulatory bodies, etc.).

This category of domain names is organised at the request of the relevant authority, which draws up naming regulations for its sector and submits them for the AFNIC's approval.

Once the naming regulations are approved, domain names in the sector are administered by the AFNIC according to the present Naming Charter and the relevant naming regulations.

Whenever a request is received, the AFNIC, with the relevant authorities in the regulated activity sectors, will examine the possibility of creating one or more sector-based domains.

"Naming Conventions"
This domain name category corresponds to domain names created in a common format for bodies in a single non-regulated sector of activity.

It is organised and administered by the AFNIC under the conditions set out in the present Charter.

Naming conventions are set up by the AFNIC as required.

2. Note: All these categories are likely to evolve and others are likely to be created.

2. GENERAL ORGANISATION


3. Any administrative operation on a domain name depends on supporting documentation and/or information, as specified in the present Charter, being submitted, with the possibility of regional or local variations in regulations.

4. As long as the domain name is in operation, the requesting body exercising the right to use the name must be able to prove that it adheres to the provisions in the present Naming Charter. In the event that, on receipt of a request for an administrative operation, the AFNIC becomes aware that one of the requesting body's domain names is no longer justified by supporting documentation, the request will go no further until the future of the domain name has been established (submission of supporting documentation or removal).

5. Certain terms may not be attributed as domain names, even if the request complies perfectly with the criteria mentioned above. These include the basic terms that are banned:

• relating to public order and decency,
• relating to the operation of the Internet,
• names of international organisations and countries that are signatories to the Paris Convention.

6. The same applies to the name France, the names reserved for French territorial organisations, and the names of regulated professions and titles (singular and plural), except those authorised in the present Charter. A non-exhaustive list is available on-line here.

7. Taking developments into account, the AFNIC reserves the right to take or reclaim possession of any domain name including a basic term that is banned without compensation but allowing sufficient time to complete the changeover.

8. Rules relating to Naming Conventions and to sector-based domains take priority over rules relating to the public domain category.

3. NAMING SYNTAX

9. The following forms are allowed:

• The letters of the alphabet from "A" to "Z" (no distinction as to case), the digits from "0" to "9" and the "-" (dash) symbol exclusively;
• Domain names with a maximum length of 255 characters (63 characters between each "." or label);
• Domain names made up of:
  • at least three letters ("aaa.fr") or one letter and one digit ("z2.fr"), with a simple ".fr" extension,
  • at least two characters ("aa.tm.fr", "m2.asso.fr"), in the other public domains.
• The "." (period or full stop) as a sub-domain separator in the sector-based domain and naming convention categories.

10. The following forms are not allowed:

• Domain names made up solely of digits;
• Domain names beginning or ending with a "-" (dash);
• Accented characters.

It should be noted that only the letter will be retained in the case of accented letters (e.g. ñ and é will be registered as n and e respectively).

4. RULES APPLYING TO PUBLIC DOMAINS

For public domain names, no supporting document will be required to back up administrative operations, except for:

• ".fr" requests from operations that are not registered with the INSEE,
• requests from organisations established by law or decree,
• requests from organisations listed with professional associations,
• requests from organisations wanting to be registered under ".prd.fr".

The AFNIC reserves the right where necessary to request the submission of supporting documents in the following cases:

• regular inspections carried out at the AFNIC's discretion to monitor correct adherence to the naming charter,
• temporary or permanent loss of access to the databases enabling supporting documents to be verified,
• inconsistencies in the information retrieved by the AFNIC from these databases.

In the case of inspections carried out after the creation of a domain name, the ISP must submit the supporting documents within a period of at most 72 hours, after which time the domain name will be blocked.

11. The supporting documents required for carrying out an administrative operation on a domain name with a public domain extension in the ".fr" naming zone are described below:

12. The following rules govern the conditions for attributing domain names throughout the ".fr" naming zone, except for the ".com.fr" extension.

13. Abbreviations, shortened forms or other adaptations are possible, as are adding a term, which must be in French, such as Conseil (consulting), Agence (agency), Société (company), Groupe (group), Entreprise (business), in order to qualify the activity or domain name of the requesting body or in a case where a name has already been claimed. Such adaptations are only possible if they are justified according to the documents supplied in application of the present Charter.

14. The requesting body may obtain an unlimited number of domain names, as long as they are justified with regard to the Charter.

15. Where the supporting document is a K Bis extract or an INSEE identification, the requesting body may choose the name from among the following categories: corporate name, initials, shop sign and trading name. The same applies for supporting documents relating to other public domain extensions.

16. For domain names ending in ".fr" created on the basis of a definitive certificate approved by the INPI, the domain name must correspond precisely to the term on the certificate, within the framework of the syntax rules given in the Charter.

17. In the case of homonyms, the second trademark can only be registered in the ".tm.fr" domain - it will not be possible to add a distinctive element to obtain a ".fr" name.

18. The attribution of a domain name implies the responsibility of the requesting body, which must only register genuine parts of its organisation as sub-domains (e.g. it would be very ill-advised to register a name such as "companyB.companyA.fr").

19. Similarly, we strongly recommend that regional branches, subsidiaries, divisions, etc. of a single organisation be grouped together within the organisation's structure (e.g. "branch.company.fr", "subsidiary.group.fr").

SPECIFIC RULES FOR THE ".COM.FR" EXTENSION

22. The registration can only proceed if the name has not already been identically recorded under one of the public domain extensions.

23. Registering a name with the ".com.fr" extension does not prevent a requesting body from registering the same name under another public domain extension at a later date.

SPECIFIC RULES FOR THE ".NOM.FR" EXTENSION

24. The domain name of a natural person observes the following syntax: "patronymic.nom.fr", and/or "patronymic-freefield.nom.fr".

25. The patronymic corresponds to the surname, maiden name or pseudonym as it appears on the supplied proof of identity.

26. Anyone registering a name under the ".nom.fr" extension may request to take up the so-called "Ex-directory" option.

27. When the "Ex-directory" option is activated, no personal information (name, address, telephone or fax number, email address if applicable) can be accessed from the public database Whois. The only information that will appear in the database will be of a technical nature, such as technical contact details and details of the ISP and DNS servers.

SPECIFIC RULES FOR THE ".ASSO.FR" EXTENSION

28. Associations with an APE 911, 912, 80 or 74 code may register a name under the ".fr" extension if they wish. This option does not preclude a registration under the ".asso.fr" extension. Associations must provide a copy of their identification in the corresponding INSEE directory.

29. Associations may request a domain name corresponding to their initials, as long as the name is the exact acronym of their full name.

30. Associations may also request a domain name based on their trading name, as long as it is mentioned in the supporting documents.

5. RULES APPLYING TO SECTOR-BASED DOMAINS

31. The procedures applicable to each sector-based domain are defined in the corresponding naming regulations, available from any of the competent authorities listed on the AFNIC website.

6.SPECIFIC RULES FOR NAMING CONVENTIONS

32. AFNIC is not controling the common registered root for conventions, as they are not compulsory anymore. This is the reponsability of the asking entity.

33. Requesting bodies concerned by the conventions below may obtain an unlimited number of domains, as long as they keep the common registered root identifying them.

Académies (education authorities): registration format: ac-name.fr (where "name" is the authority), e.g. ac-lyon.fr. An identification from the INSEE directory must be supplied. (Secondary schools and junior high schools are registered as sub-domains of the corresponding education authorities, but private establishments not funded by an authority are registered directly under the ".fr" extension).

Ambassades (embassies): registration format: amb-name.fr (where "name" is the name of a city or country), e.g. amb-wash.fr (French embassy in Washington). An identification from the INSEE directory must be supplied, or, failing that, a letter on embassy headed notepaper signed by the ambassador.

Assistance publique (public welfare): registration format: ap-name.fr (where "name" is a town), e.g. ap-hop-paris.fr (Hospitals of the City of Paris). An identification from the INSEE directory must be supplied.

Bibliothèques municipales (municipal libraries): registration format: bm-name.fr (where "name" is a town), e.g. bm-lyon.fr. An identification from the INSEE directory must be supplied.

Bovin de Croissance (cattle growth): naming convention set up by the Fédération Bovins Croissance (cattle growth federation). Registration format: department-bovins-croissance.fr (where "department" is the name of the department). E.g. creuse-bovins-croissance.fr (Creuse cattle growth union). An identification from the INSEE directory or other proof must be supplied.

Caisses d'allocations familiales (family benefit organisations): domain subject to the authority of the Caisse Nationale d'Allocations Familiales (CNAF) (national family benefits fund). Registered under .caf.fr. Contact the administration manager for the zone.

Caisses régionales d'assurance maladie des artisans et commerçants (regional self-employed workers' health fund): domain subject to the authority of the Caisse Nationale d'Assurance Maladies des Professions Indépendantes (national health insurance fund for independent professions). Registration format: canam.fr. Contact the administration manager for the zone.

Caisses d'Epargne (bank): domain subject to the authority of the Centre National des Caisses d'Epargne (CENCEP) (national Caisses d'Epargne centre). Registration format: caisse-epargne.fr. Contact the administration manager for the zone.

Centres d'économie rurale (rural economy centres): registration format: cerxx.asso.fr (where "xx" is the number of the department). An identification from the INSEE directory, certificate of declaration from the préfecture or copy of the appearance in the Official Journal must be supplied.

Centres hospitaliers (hospitals): registration format: chu-xx.fr or chru-xx.fr or ch-xx.fr or hopital-xx.fr (where "xx" is the name of the town or of the hospital). E.g. chu-rouen.fr (Centre Hospitalier Universitaire de Rouen - University Hospital of Rouen). An identification from the INSEE directory must be supplied.

Centres régionaux de la propriété forestière (regional forest estates centres): domain subject to the authority of the Centre Régional de la Propriété forestière d'Alsace Lorraine (regional forest estates centre of Alsace-Lorraine). Registration format: crpf.fr. Contact the administration manager for the zone.

Chambres des Métiers (chambers of trade): registration format: cm-name.fr (where "name" is a town). e.g. cm-annecy.fr (Chambre des métiers de Haute Savoie - chamber of trade of Haute Savoie). An identification from the INSEE directory must be supplied.

Comités départementaux du tourisme (department tourism committees): registration format: cdt-name.fr and/or cdt-tourisme-name.fr (where "name" is a department). E.g. cdt-vaucluse.fr (Comité Départemental du Tourisme du Vaucluse - Vaucluse department tourism committee). An identification from the INSEE directory must be supplied.

Comités régionaux du tourisme (regional tourism committees): registration format: crt-name.fr (where "name" is a region). E.g. crt-aquitaine.fr (Aquitaine region tourism committee). An identification from the INSEE directory must be supplied.

Communautés d'agglomérations (urban area communities, previously called districts): registration format: agglo-name.fr (where "name" is the urban community). E.g. agglo-montbeliard.fr (Communauté d'Agglomérations du pays de Montbeliard - urban community of Montbeliard). An identification from the INSEE directory must be supplied.

Communautés de communes (communities of municipalities): registration format: cc-name.fr (where "name" has been officially declared). E.g. cc-confolentais.fr (community of Confolentais municipalities). A K Bis extract or identification from the INSEE directory must be supplied.

Confédération de l'Artisanat et des Petites Entreprises du Bâtiment (confederation of small building firms and craftsmen): naming convention set up by the Confédération de l'artisanat et des petites entreprises du bâtiment. Registration format: three domain names, one of which must be capeb-xx.fr (where "xx" is the name of the department or region). If several entities exists within a single department, xx is the name of the town where the structure is located rather than the department number). Other domain names must keep the root capeb, e.g. capeb-ain.fr/capeb01.fr (Confédération de l'Ain). An identification from the INSEE directory must be supplied.

Conseils généraux (department councils): registration format: cgxx.fr and/or cg-xx.fr and/or xx.fr (where "xx" is the number or name of the department). E.g. cg23.fr/creuse.fr/cg-creuse.fr (Conseil Général de la Creuse). An identification from the INSEE directory must be supplied. Note: "departmentnumber.fr" cannot be registered.

Conseils régionaux (regional councils): registration format: crxx.fr and/or cr-xx.fr and/or xx.fr(where "xx" is the name of the region). E.g. cr-aquitaine.fr, aquitaine.fr , craquitaine.fr (Conseil Régional d'Aquitaine). An identification from the INSEE directory must be supplied.

Consulates: registration format: consulnameofcountry-nameoftown.fr (for foreign consulates in France) and consulfrance-nameoftown.fr (for French consulates abroad). An identification from the INSEE directory must be supplied, or, failing this, a letter on Consulate headed paper signed by the Consul.

Contrôle laitier (dairy checks): naming convention set up by the Fédération de Contrôle Laitier (dairy inspection federation). Registration format: departement-controle-laitier.fr (where "departement" is the name of the department). E.g. calvados-controle-laitier.fr (Syndicat d'Elevage du contrôle laitier du Calvados - Calvados farmers' dairy inspection union). An identification from the INSEE direction or other proof must be supplied.

Crédit Agricole (bank): naming convention set up by the Caisse Nationale du Crédit Agricole. 3 domain names; registration format for Crédit Agricole branches and subsidiaries: ca-name.fr, + 2 other domains depending on the supporting documentation (where "name" is the name of the branch). E.g. ca-alsace.fr. A K Bis extract or an identification from the INSEE directory must be supplied.

Districts (former name for communautés d'agglomérations): registration format: district-xxx.fr (where "xxx" is the name of the district or town). E.g. district-parthenay.fr or district-vernon.fr. An identification from the INSEE directory must be supplied.

Ecoles d'agriculture (agricultural schools): public colleges are registered as sub-domains of educagri.fr. E.g. esa-angers.educagri.fr. Requests should be made directly to the administrative manager for the educagri.fr domain.

Ecoles régionales des beaux-arts (regional art colleges): registration format: erba-name.fr (where "name" is a town). E.g. erba-rennes.fr (Ecoles Régionales des Beaux-Arts de Rennes - regional art college of Rennes). An identification from the INSEE directory must be supplied.

Fédération Nationale des Centres de Lutte Contre le Cancer (national federation of cancer research centres): domain subject to the authority of the Fédération Nationale des Centres de Lutte Contre Le Cancer. Registration under fnclcc.fr. Contact the administration manager for the zone.

Fédération départementale des syndicats d'exploitants agricoles (department federation of agricultural operator unions): naming convention set up by the Fédération nationale des syndicats d'exploitants agricoles. Registration format: fdseaxx.fr (where "xx" is the department number). E.g. fdsea51.fr (Marne department federation).

Fédération départementale et régionale du Bâtiment, unions et syndicats nationaux (department and regional building federation, national trade unions): naming convention set up by the Fédération Française du batiment (French building federation). Registration format: ffbatiment-xx.fr (where "xx" is the department number), ffbatiment-region.fr (where "region" is the name of the region, in full or abbreviated), ffbatiment-union.fr (where "union" is the name or initials of the trade union).

Greta: Registration format: name.greta.fr (where "name" is the official name, initials or trading name of the organisation), e.g. gts93.greta.fr (greta tertiaire sud 93 - southern tertiary greta 93). This convention is subject to the authority of the AFNIC.

Groupama and Crama: registration format: groupama-name.fr (where "name" is spelt in full, in initials or abbreviated). E.g. groupama-ca.fr or groupama-centre-atlantique.fr for the Centre Atlantique Groupama; groupama-normandie.fr for the Normandy Crama. A K Bis extract or identification from the INSEE directory must be supplied.

Instituts Universitaires de Formation des Maîtres (university teacher training institutes): domain subject to the authority of the Institut Universitaire des Maîtres de Paris (Paris university teacher training institute). Registration format: iufm.fr. Contact the administration manager for the zone.

Instituts Universitaires de Technologie (university technology institutes): registration format:: iut-name.fr (where "name" is the name of a town). E.g. iut-lannion.fr. It is recommended that IUTs be included in the hierarchy of the university of which they are part, e.g. iut.univ-aix.fr rather than iut-aix.fr. An identification from the INSEE directory must be supplied.

Mairies et Villes (towns and town halls): registration format: mairie-xx.fr and/or ville-xx.fr and/or xx.fr (where "xx" is the name of a town). E.g. mairie-metz.fr, ville-metz.fr, metz.fr. An identification from the INSEE directory must be supplied. Note:
-for localities with the same name, the department number will be added as a matter of course.
-the department number may be added to all or part of the locality name on request, as long as two localities with the same name do not exist within one department.
- A company holding a trademark registered before 1985 can obtain a domain name corresponding to the name of a town. E.g. evian.fr for the Evian company.

Offices de tourisme (tourist offices): registration format: ot-name.fr (where "name" is a town). E.g. ot-avignon.fr. An identification from the INSEE directory must be supplied.

Offices de tourisme étrangers (foreign tourist offices): registration format: name-tourisme.fr (where "name" is the name of the country in French). E.g. italie-tourisme.fr. An identification from the INSEE directory must be supplied.

Technopoles (technology hubs): registration format: tech-name.fr (where "name" is a town). E..g. tech-quimper.fr. An identification from the INSEE directory must be supplied.

Unions des associations des familles (unions of family associations): domain subject to the authority of the Fédération des Unions des Associations des Familles (federation of family association unions). Registration under unaf.fr. Contact the administration manager for the zone.

Universités (universities): registration format: univ-name.fr or u-name.fr (where "name" is the name of the university, often tied to a city). E.g. univ-rennes1.fr (University of Rennes 1), u-grenoble3.fr (University of Grenoble 3). An identification from the INSEE directory must be supplied.

III. ADMINISTRATIVE OPERATIONS ON DOMAIN NAMES

1. CREATING A DOMAIN NAME

1. The creation phase for a domain name, i.e. the phase preparing for the registration and attribution of a domain name, is carried out on behalf of the requesting body in collaboration with the AFNIC by the ISP, chosen from the list of available ISPs available on the AFNIC website.

2. The "First arrived, first served" rule is applied for each creation of a domain name, respecting the Naming Charter.

3. Requests for the creation of a domain name must never infringe the rights of third parties or threaten public order.

4. In this context, the AFNIC reserves the right to employ any measures in order to counteract any infringement of the rights of third parties, and the option of using any appropriate procedure against offenders, but is not obliged to do so.

5. If a domain name is created on the basis of provisional supporting documents (e.g. a provisional K Bis extract or one in the process of being modified), and if the AFNIC cannot verify the existence of the definitive documents in the databases within the allotted time, the AFNIC will suspend the domain name.

6. The domain name remains registered in the name of the requesting body in the database, but may no longer be used to access the corresponding services (website, email etc.). The domain name is suspended for a maximum of one month.

7. It is the requesting body's responsibility to resolve the situation by supplying the AFNIC, via its ISP, with the proofs. During this period the AFNIC will do its best to place the domain name back into service within 72 hours after having received the definitive documents.

8. If the situation is not resolved within the allotted time, the domain name is removed without notice or compensation. Once the domain name has been removed, it can be reassigned to any third party making a request within the terms of the present Charter.

9. In order to ensure the proper management of the naming zone, the AFNIC will not pre-register or reserve domain names prior to the full request for the creation of a domain name.

2. MODIFICATIONS TO DOMAIN NAMES OR TECHNICAL OR ADMINISTRATIVE ELEMENTS

10. The requesting body may, through its ISP, request that a domain name be modified in response to changes in the supporting documents (such as changes in the corporate name, trading name, shop name, association name or changes to a trademark etc.).

11. A modification request can only be undertaken by the AFNIC if the requesting body provides the corresponding supporting documents.

12. The modification of a domain name can involve an initial "migration period" of 1 (one) or 2 (two) months, at the requesting body's discretion, during which both the previous and the new names are active simultaneously.

13. The requesting body may ask for a further delay of no more than 1 (one) year starting from the date of the modification request submitted by the ISP to the AFNIC, on condition that the corresponding supporting documents are supplied and that the maximum number of domain names that can be allocated is not exceeded. The extra time granted by the AFNIC varies according to the age of the domain name initially registered.

14. The requesting body may, through its ISP, request changes in the administrative details held on it (such as the technical or administrative contact person, address etc.).

15. In the context of a "company transformation", i.e. a change in the legal status of a company during its existence (such as when a limited company becomes a public limited company), the requesting body must submit to the AFNIC, through its ISP, the supporting documents certifying the change.

3. TRANSMISSION OF A DOMAIN NAME

16. The "transmission" of a domain name may arise in the following cases: company merger or demerger, partial transfer of assets, agreement between parent and subsidiary companies, transfer of a trademark, collective procedures or as a result of a judicial decision.

17. For administrative and technical reasons, the transmission of a domain name in the abovementioned cases entails removing and then recreating the domain name. The two operations take place on the same day. The transmission procedure is designed to avoid the domain name being subsequently reassigned to any other unauthorised party.

18. Like all administrative operations, requests for the transmission of a domain name are addressed to the AFNIC by an ISP on behalf of the requesting body.

19. The requesting body on whose behalf the transmission is taking place must satisfy the requirements of the Charter, in particular in terms of supplying the necessary supporting documents.

20. The transmission of a domain name must not have effects that run contrary to the Naming Charter.

21. The contribution of the ISP must be strictly in accordance with the Procedural Guide.

22. In all cases, the AFNIC reserves the right to require any further supporting documents necessary in addition to those already identified in the present Naming Charter in order to carry out the necessary verification.

3.1. MERGERS

23. The term "merger" refers to the operation described in articles L 236-1 and L 236-3 of the Commercial Code ("fusion"), by which at least two companies come together to form one company. This operation may result from the transfer of property belonging to one or several companies, either to an existing company or to a new one made up of them.

24. When a request for the transmission of a domain name follows a merger, the governing body of the new company or the purchasing company must include the following with the request for each of the companies involved in the merger:

• A copy of the K Bis extract of the companies concerned;
• A certified copy of the announcements made in legal journals;
• The acceptance letter based on the AFNIC template available here, signed by the initial requesting body, confirming its provisional acceptance of the transmission and of all the preliminary steps to be taken involving third parties (particularly, the original ISP).

3.2 DEMERGER

25. The term "demerger" refers to the operation described in articles L 236-1 and L 236-3 of the Commercial Code ("scission"), by which a company (the "scindée" or "split" company) transfers its property to two or more existing or new companies.

26. When a request for the transmission of a domain name follows a demerger, the governing body of the beneficiary company must include with its request:

• A copy of the K Bis extract for each company involved mentioning the demerger;
• A certified copy of the announcements made in legal journals;
• The acceptance letter based on the AFNIC template available here, signed by the initial requesting body, confirming its provisional acceptance of the transmission and of all the preliminary steps to be taken involving third parties (particularly, the original ISP).

3.3 PARTIAL TRANSFER OF ASSETS

27. The term "partial transfer of assets" refers to the operation described in article L 236-22 of the Commercial Code ("apport partiel d'actifs"), by which a company transfers a part of its assets to another company (existing or new), in exchange for shares released by the company benefiting from the transfer, on the express condition that the partial transfer of assets applies to the assets and liabilities of a complete branch of activity.

28. When a request for the transmission of a domain name follows a partial transfer of assets under a demerger settlement, the governing body of the beneficiary company must include a statement from the company's auditor, if there is one, or a chartered accountant if not, certifying that:

• The partial transfer of assets agreement mentions the option for the demerger settlement;
• The domain name of the transferring company is indeed included in this transfer.

29. The requesting body must also include with the request:

• A copy of the K Bis extract for the companies involved mentioning the partial transfer of assets;
• A certified copy of the announcements made in legal journals;
• The acceptance letter based on the AFNIC template available here, signed by the initial requesting body confirming its provisional acceptance of the transmission and of all the preliminary steps to be taken involving third parties (particularly, the original ISP).

3.4. AGREEMENTS BETWEEN PARENT AND SUBSIDIARY COMPANIES

30. The term "parent company" refers to a company owning more than half the capital of another company and "subsidiary company" refers to a company more than half of whose capital is owned by another company, in accordance with article L 233-1 of the Commercial Code ("société mère" and "filiale" respectively).

31. When a request for the transmission of a domain name is made in the context of an agreement between a parent company and its subsidiary, the governing body of the parent company or the subsidiary must include with the request:

• Any documents justifying the transmission,
• A statement from the auditor or, if there is no auditor, a chartered accountant, certifying that a link exists between the parent company and the subsidiary,
• The letter of acceptance based on the AFNIC template available here, signed by the initial requesting body, confirming its provisional acceptance of the transmission and of all the preliminary steps to be taken involving third parties (particularly, the original ISP).

3.5. TRANSFER OF A TRADEMARK

32. In the case of the transfer of a properly registered trademark, the domain name with the ".tm.fr" extension is removed, without an express request from the transferring company and the concessionary who will benefit from a transmission procedure.

33. In this case, it is up to the party which is the first to take action to communicate to the AFNIC through the ISP:

• The up-to-date inscriptions in the Registre national des marques (national trademark register) mentioning the transfer of the trademark;
• The acceptance letter according to the AFNIC template available here, signed by the initial requesting body, confirming its provisional acceptance of the transmission and of all the preliminary steps to be taken involving third parties (in particular, the original ISP).

3.6. COLLECTIVE INSOLVENCY PROCEDURES

34. If the requesting body is subject to insolvency proceedings, the AFNIC will proceed with the transmission of the domain name as ordered by the competent judicial authorities.

3.7. JUDICIAL DECISIONS

35. The AFNIC will carry out any administrative operation ordered by a judicial decision in the terms of the decision, and under the following conditions:

• When all parties involved agree to carry out the judicial decision and inform AFNIC by registered letter with confirmation of receipt ;
  or
  
• When the AFNIC is informed by a bailiff, on behalf of the contending party which is the first to take action, of an immediately enforceable judicial decision, with good reason, in application of article 514 of the new Civil Procedure Code, with proof that the party has been informed of the decision ;
  or
  
• When the AFNIC is informed by a bailiff, on behalf of the contending party which is the first to take action, of an immediately enforceable judicial decision within the meaning of article 515 of the new Civil Procedure Code, with proof that the party has been informed of the decision, and on presentation of proof of any surety settlement ordered by the judge, in application of article 517 of the new Civil Procedure Code ;
  or
  
• When the AFNIC is informed by a bailiff, on behalf of the contending party which is the first to take action, of a judgement possessing the force of law within the meaning of article 500 of the new Civil Procedure Code, for which proof will be provided. Depending on the circumstances, this proof may, for example, consist of the submission of a certificate of no appeal or of notification of the appeal judgement.

36. Casein the event that a judicial decision is reversed, the AFNIC will proceed to implement the new administrative deeds ordered, under the same conditions.

37. The AFNIC may not undertake petitions that do not meet these conditions, and may not be bound, for example, by letters dispatched or by writs.

38. The AFNIC cannot be held responsible for any administrative operations undertaken in application of a judicial decision, and the requesting body will guarantee the AFNIC against any claim.

39. The requesting body must supply the AFNIC, through the ISP, with the supporting documents required by the Naming Charter within one month. If this is not done, the use of the domain name by the requesting body may be suspended until the situation is resolved.

40. The technical and administrative expenses incurred in the transmission are due from the requesting body, and it is up to the requesting body to seek reimbursement from one or other of the parties involved as need be.

4. GIVING UP A DOMAIN NAME

41. The operation of a domain name in the ".fr" zone depends on having the right to use it. As a result, no form of disposal of a domain name, either gratuitously or for a consideration, can be enforceable against the AFNIC.

42. Consequently, any removal/recreation operation on a domain name is carried out at the risk of the requesting body. It should be remembered that as soon as a domain name is removed it returns to the public domain, and can thus be reattributed at any time to any other requesting body respecting the present Naming Charter.

5. CHANGING THE ISP

43. As long as the necessary agreement has been made with the ISP, the requesting body may ask for a change of delegation, which consists of the technical transfer of the domain name from one ISP to another.

44. To make this change, it is the responsibility of:

• the requesting body to make the necessary arrangements with the ISPs so that they can proceed with the change of delegation;
  
  
• the ISPs involved to proceed with the change of delegation properly on behalf of the requesting body.

45. The ISP to whom the domain name is being delegated must ensure that the technical change does not affect the administration of the domain name.

46. Procedure and delay regarding the Change of provider are available on the "Guide des Procйdures" ("Procedural Guide").

6. REMOVAL OF A DOMAIN NAME

47. At any time, the requesting body through its ISP may ask that the domain name be removed. This request cannot be revoked and requires no justification.

48.