Question

Supposons que vous souhaitiez fournir un exemple d'URL dans la documentation. La bonne chose à faire est d’utiliser exemple.com , car c’est l’emplacement défini pour de telles choses et tout ce que vous proposez est susceptible d’être réellement enregistré quelque part et de servir qui sait quoi à vos lecteurs. .

Ma question est la suivante: que faites-vous si vous devez fournir deux exemples contrastés? Le meilleur que j'ai vu est site1.example.com et site2.example.com, mais cela ne suffit pas toujours. D'autres idées?

Mise à jour:
Accepté @ La réponse de Yuval, puisqu'il s'agit de la réponse la plus techniquement correcte. Cependant, en raison de forces indépendantes de ma volonté, je travaille avec Jekke (tempuri.com).

Était-ce utile?

La solution

Utilisez example.net et example.org .

Conformément à la RFC 2606 , ils sont tous réservés ( Résumé de Wikipedia ).

Autres conseils

La RFC 2606 réserve également le TLD (domaine de premier niveau) ".example". alors vous peut utiliser "foobar.example", "quelque chose.exemple", "stackoverflow.example", etc.

Malheureusement, tous ces noms incluent la chaîne "exemple". et par conséquent, ne se distinguent pas suffisamment dans la documentation. J'espère il y aura une mise à jour de la RFC 2606 un jour, avec plus de noms.

As previously mentioned, example.com, example.net and example.org were officially reserved by the IETF for documentation purposes. Additionally, ICANN has also reserved example.edu.

Some ccTLDs and newer gTLDs have equivalent example domains reserved. Most probably, all gTLDs managed by ICANN have the same restrictions regarding reserved names. Further below, I've listed a few that I've been able to confirm as reserved.

On some occasions, I need an example domain name longer than 8 characters (excluding the TLD itself) and it doesn't matter that it isn't valid — I just want it to not resolve. Therefore using an underscore in the domain name is an acceptable solution in those cases (e.g. example_domain.com or your_domain.com).

Another alternative TLD, although not officially reserved, would be .tld (!). I've looked at ICANN's new gTLD current application status list and .tld doesn't show up. So any domain could be used under this TLD (e.g. example.tld or yourdomain.tld). I would however recommend using it with caution, as the fact that it's not currently assigned doesn't mean no one will ever apply for it. As a side note, be aware that both Amazon EU and Charleston Road Registry have applied for .dev.

Reserved generic example TLDs (not including the latest expansion):

Reserved country code example TLDs (not a complete list):

  • example.ae (Domain reserved by .aeDA)
  • example.at (Registered by NIC.AT GmbH. admin: NIC.AT Role)
  • example.bg (Registration status: forbidden)
  • example.ca (Restricted: not available for registration)
  • example.co (Domain is on list of restricted and reserved names)
  • example.hk (Domain is currently not available for registration)
  • example.jp (Reserved)
    including co.jp ne.jp or.jp subdomains
  • example.la (Banned)
  • example.nl (Registered by Stichting Internet Domeinregistratie Nederland)
  • example.pt (Registration forbidden. Article 9, point 1)
    including com.pt net.pt org.pt edu.pt int.pt nome.pt publ.pt subdomains
  • example.se (Registration blocked. Example and test domains.)
  • example.su (Stop-list: Domain can not be registered.)
  • example.sx (Unavailable)

References:

You can also use tempuri.org, like is used in many XML-based examples.

I'm wondering if you can squeeze in some character into the URL that would make it invalid if cut and pasted into a browser. A little like 555-XXXX numbers in movies.

There is also example.net and example.org. If you need another, I don't see a problem with using a domain you already control.

Licencié sous: CC-BY-SA avec attribution
Non affilié à StackOverflow
scroll top