_for-sale DNS records

A recently proposed RFC 10023 introduces the _for-sale DNS TXT record, a new mechanism designed to indicate that a domain is available for purchase. Unlike traditional domain parking pages or WHOIS data, this record sits silently in the DNS, allowing the domain's website and services to remain fully operational while simultaneously signaling its sale status to interested parties like brokers or automated services.

Key aspects of this specification include:

• Format: A TXT record at _for-sale.example.com includes a mandatory version tag (v=FORSALE1;) and optional key-value pairs like ftxt= (free text), furi= (contact URI), fval= (asking price), and fcod= (proprietary code).
• Distinction from Parking: It explicitly states this is not for parking domains, as it doesn't replace the live site and is invisible to browsers.
• Intended Audience: Primarily designed for brokers and automated availability services, not individual users, to bridge the gap left by WHOIS privacy.
• Implementation Rules: Requires v=FORSALE1;, one tag-value pair per record (multiple records form an RRset), a single character-string per record (max 255 octets), a low TTL (<= 3600s), placement at a leaf node, and removal when no longer for sale.
• Common Mistakes Addressed: Warns against cramming multiple pairs, publishing aspirationally, assuming it's binding, wildcards, and trusting ftxt/furi content due to potential malicious use.
• Verification: Provides dig commands to check the record's existence, format, TTL, and DNSSEC validation.

The proposed standard aims to create a standardized, externally checkable signal for domain availability, addressing the long-standing problem of buyers being unable to ascertain if an active domain is for sale without resorting to cold emails or unreliable methods.