| Introduced | 1999 |
|---|---|
| TLD type | Reserved top-level domain |
| Status | Reserved to prevent confusion and conflict |
| Registry | IANA |
| Sponsor | None |
| Intended use | Example top-level domain for documentation |
| Actual use | Sometimes used in intended manner in documentation |
| Registration restrictions | no registrations are possible |
| Structure | as needed in example usage |
| Documents | RFC 2606 |
| Dispute policies | None |
| Registry website | None |
The name example is reserved by the Internet Engineering Task Force (IETF) as a domain name that may not be installed as a top-level domain in the Domain Name System (DNS) of the Internet.[1]
YouTube Encyclopedic
-
1/3Views:379 571699 440188 378
-
Elevator Pitch Example - How To Create A Personal Elevator Pitch
-
Linear Transformations , Example 1, Part 1 of 2
-
Python Examples | Python Programs For Beginners | Python Tutorial For Beginners | Edureka
Transcription
Reserved DNS names
In 1999, the Internet Engineering Task Force reserved the DNS labels example, invalid, localhost, and test so that they may not be installed into the root zone of the Domain Name System.[1]
The reason for reservation of these top-level domain names is to reduce the likelihood of conflict and confusion. This allows the use of these names for either documentation purposes or in local testing scenarios.
Purpose
The top-level domain example is explicitly intended to be used in documentation or other technical writing, when domain names are presented as examples in usage or presentation of concepts of the Domain Name System or the Internet.
See also
- example.com
- 192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24 – IPv4 ranges reserved for documentation and example code.[2]
- 2001:db8::/32 – IPv6 range reserved for documentation.[3]
References
- ^ a b D. Eastlake; A. Panitz (June 1999). Reserved Top Level DNS Names. Network Working Group. doi:10.17487/RFC2606. BCP 32. RFC 2606. Best Common Practice. Updated by RFC 6761.
- ^ J. Arkko; M. Cotton; L. Vegoda (January 2010). IPv4 Address Blocks Reserved for Documentation. Internet Engineering Task Force. doi:10.17487/RFC5737. ISSN 2070-1721. RFC 5737. Informational. Updates RFC 1166.
- ^ G. Huston; A. Lord; P. Smith (July 2004). IPv6 Address Prefix Reserved for Documentation. Network Working Group. doi:10.17487/RFC3849. RFC 3849. Informational.
This page was last edited on 24 February 2024, at 19:54