RFC 7085: Top-Level Domains That Are Already Dotless
In plain English — editorial summary, not part of the RFC
Recent statements from the Internet Architecture Board (IAB) and the Internet Corporation of Assigned Names and Numbers (ICANN) Security and Stability Advisory Committee have focused on the problems that the DNS is likely to experience with top-level domains (TLDs) that contain address records (so-called "dotless domains"). In order to help researchers determine the extent of the issues with dotless domains, this document lists the current dotless TLDs and gives a script for finding them. This document lists data about dotless TLDs but does not address the policy and technology issues other than to point to the statements of others.
Document record
- Document ID
- RFC7085
- Published
- December 2013
- Authors
- J. Levine; P. Hoffman
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 6
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6927Variants in Second-Level Names Registered in Top-Level DomainsCurrent
May 2013
- RFC 7314Extension Mechanisms for DNS (EDNS) EXPIRE OptionCurrent
July 2014
- RFC 7958DNSSEC Trust Anchor Publication for the Root ZoneObsoleted
August 2016
- RFC 9199Considerations for Large Authoritative DNS Server OperatorsCurrent
March 2022
- RFC 6975Signaling Cryptographic Algorithm Understanding in DNS Security Extensions (DNSSEC)Current
July 2013
- RFC 6844DNS Certification Authority Authorization (CAA) Resource RecordObsoleted
January 2013
- RFC 6841A Framework for DNSSEC Policies and DNSSEC Practice StatementsCurrent
January 2013
- RFC 7344Automating DNSSEC Delegation Trust MaintenanceUpdated
September 2014
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?