_for-sale DNS records: Standardizing Domain Acquisition Signals in Public Zone Files

_for-sale DNS records has rapidly emerged as one of the most widely discussed internet infrastructure proposals across the developer ecosystem today, accumulating 396 upvotes on Hacker News and generating intense architectural debate among systems engineers, network administrators, and domain registrars.

Originating from the specification.website RFC draft, this proposal addresses fundamental flaws in the secondary domain market: ad-bloated domain parking pages, spam-heavy WHOIS scrapers, and opaque broker commissions. In this comprehensive 2,500-word technical guide, we analyze the zone file specification, query workflows, DNSSEC security semantics, and community reactions.

For over three decades, indicating that a domain name is available for purchase has required hosting custom web pages, listing domains on proprietary auction platforms (such as Sedo, Dan, or Afternic), or exposing personal contact information in public WHOIS directories.

1.1 The Flaws of Legacy Domain Parking

This status quo introduces severe operational and security drawbacks for software engineers and domain portfolio managers:

The _for-sale DNS specification solves this by moving availability signaling directly into the Domain Name System (DNS) via a dedicated TXT record at the _for-sale subdomain node.

The core specification defines a deterministic key-value payload stored inside a public DNS TXT record. By querying _for-sale.yourdomain.com, any DNS resolver, crawler, or CLI tool can programmatically verify sale status in milliseconds without making HTTP requests.

2.1 Zone File Record Syntax & Schema

A compliant _for-sale TXT record follows a key-value tag format with a mandatory version tag v=FORSALE1:

; Compliant BIND9 / Zone File Entry for _for-sale TXT Record
_for-sale.example.com.  3600  IN  TXT  "v=FORSALE1; uri=https://example.com/buy; price=2500; currency=USD; contact=mailto:domain-sales@example.com"

2.2 Field Tag Definitions

• v=FORSALE1 (Mandatory): Specifies protocol version for parser backwards compatibility.
• uri= (Optional): Direct URL pointing to a self-hosted checkout page, escrow service, or transaction portal.
• price= (Optional): Fixed buy-it-now price or minimum starting offer integer value.
• currency= (Optional): ISO 4217 3-letter currency code (e.g. USD, EUR, GBP).
• contact= (Optional): Direct URI for inquiries, such as mailto: or an encrypted contact endpoint.

2.3 Programmatic Querying in Node.js & Terminal Tools

Developers can query _for-sale records using standard terminal tools or Node.js scripts:

# Terminal query using dig
dig +short TXT _for-sale.example.com

// TypeScript Implementation for Programmatic _for-sale DNS Resolution
import { Resolver } from 'dns/promises';

export interface ForSaleRecord {
  version: string;
  uri?: string;
  price?: number;
  currency?: string;
  contact?: string;
}

export async function parseForSaleRecord(domain: string): Promise<ForSaleRecord | null> {
  const resolver = new Resolver();
  try {
    const records = await resolver.resolveTxt(`_for-sale.${domain}`);
    const flatString = records.flat().join('');

    if (!flatString.startsWith('v=FORSALE1')) return null;

    const tags: Record<string, string> = {};
    flatString.split(';').forEach((pair) => {
      const [key, val] = pair.split('=').map((s) => s.trim());
      if (key && val) tags[key] = val;
    });

    return {
      version: tags['v'],
      uri: tags['uri'],
      price: tags['price'] ? parseInt(tags['price'], 10) : undefined,
      currency: tags['currency'],
      contact: tags['contact'],
    };
  } catch (error) {
    return null;
  }
}

• Original Draft Specification: Read full proposal on specification.website
• Hacker News Conversation: Join community discussion on Hacker News