add(foundations): _for-sale DNS records (RFC 10023) - #165
Merged
Conversation
Overrules the /considered/ turn-down proposed in #151. RFC 10023 (Informational, July 2026, SIDN Labs) reserves the "_for-sale" leaf node name and IANA has registered it in the Underscored and Globally Scoped DNS Node Names registry. Status `optional`: it applies only when the domain is actually for sale, which is the definition of context-dependent. The misconception the page is written against is that this is domain parking. It is nearly the opposite — the record sits beside a live site, is invisible to browsers, and answers the question WHOIS and RDAP cannot, since a name being registered has never implied it is unavailable. Wires for-sale-dns into relatedSlugs on dnssec, caa-records and dns-aid. Adds the changelog entry, the per-page OG image and the four count-driven ones, and re-signs SKILL.md (167 -> 168 pages). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Deploying specification-website with
|
| Latest commit: |
083d527
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://2f8a41b1.specification-website.pages.dev |
| Branch Preview URL: | https://add-for-sale-dns-node-name.specification-website.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overrules the
/considered/turn-down proposed in #151, per maintainer decision. #151 will be closed unmerged.What changed
New spec page:
/spec/foundations/for-sale-dns/, statusoptional.Also wires
for-sale-dnsintorelatedSlugsondnssec,caa-recordsanddns-aid; adds the changelog entry, the per-page OG image plus the four count-driven ones, and re-signsSKILL.md(167 → 168 pages).Sources
TXT | _for-sale | RFC 10023.Status justification
optional, which is the honest reading of "depends on context" — the page applies only to domains actually for sale. Notrecommended: most sites should not publish this, and the RFC is explicit that any text suggesting a domain is not for sale is invalid content, so there is no neutral value to recommend.The misconception it is written against
That
_for-saleis a way of parking a domain. It is nearly the opposite: the record sits in DNS beside a live site, is invisible to browsers, and can be toggled at will. RFC 10023 designs for exactly that case. The secondary confusion is with registration data — WHOIS/RDAP answer "is this registered?", and a registered name may still be purchasable, which is the gap the convention exists to fill.Category
Filed under foundations, alongside the other site-level identity and discovery signals (
canonical-url,feed-discovery,websub,open-graph).securitywas the alternative, sincecaa-recordsanddnsseclive there — but that category groups by purpose ("headers, transport, and policies that keep visitors safe"), and_for-salehas no security purpose. Easy to move while the URL is new if you disagree.Not shipped here
This site does not publish a
_for-salerecord — specification.website is not for sale. The page says so in one line, per the "specced, deliberately not shipped" shape in CLAUDE.md.Verified
npm run lint,format:check,check:skill(168 pages, digest ✓),astro check(0 errors),npm run build(168 indexed). Page appears on/spec/,/spec/foundations/,/checklist/,/llms.txt,/sitemap-foundations.xml,/okf/foundations/for-sale-dns.md, the changelog anchor and the changelog RSS feed. The inlinednsseccross-link resolves to/spec/security/dnssec/— correct category, per CLAUDE.md rule 8.🤖 Generated with Claude Code