Join our Newsletter — 33% off our NHI Course
Home› Glossary› Cyber Security› RFC 2606
Cyber Security

RFC 2606

← Back to Glossary
By NHI Mgmt Group Updated November 16, 2026 Domain: Cyber Security

RFC 2606 is an Internet standards document that reserves certain domain names and top-level domains for documentation and testing. It defines names such as example, invalid and localhost so they can be used safely in software examples, DNS configuration and lab systems without colliding with real internet names.

What RFC 2606 Is For

RFC 2606 is about giving engineers safe, reserved names to use in documentation, tutorials and test environments. That matters because examples need to look realistic without accidentally resolving to live internet assets, triggering DNS leakage, or creating ambiguity between placeholder data and production configuration.

It is best understood as a namespace safety document. By reserving well-known labels and top-level domains for non-production use, it reduces the chance that sample code, lab DNS entries or config snippets will interfere with real services or be mistaken for legitimate targets.

Why Reserved Names Matter in Practice

Reserved names are a small control with outsized value because DNS examples are copied into automation, runbooks and lab systems. If a placeholder looks real, it can create accidental external calls, false ownership assumptions, or confusion during incident response and troubleshooting.

The practical benefit is consistency. When teams use reserved domains such as example, invalid and localhost in the intended way, they make documentation easier to trust and reduce the risk that a copied configuration reaches beyond the environment where it was meant to stay.

How RFC 2606 Supports Testing and Documentation

RFC 2606 gives authors a stable reference point for writing examples that should never be treated as real infrastructure. That helps developers, SREs and security teams document DNS settings, web links and local services without needing ad hoc placeholder conventions that vary from team to team.

It also supports repeatable testing. Lab systems often need domain-like strings, but test data should remain unmistakably non-production. Reserved names help separate demonstration content from operational assets, which is especially useful when examples are embedded in configuration files, IaC templates or onboarding material.

Common Misuse and Configuration Pitfalls

The main pitfall is treating reserved names as if they were ordinary example strings with no operational significance. In reality, they are meant to be used intentionally and consistently, because the boundary between “sample” and “real” can blur once documentation is copied into scripts, tickets or deployment pipelines.

Another issue is partial adoption. If one team uses reserved names while another invents local placeholders, the organisation loses a shared convention. That increases the chance of broken examples, inconsistent training material and accidental dependence on domains that were never meant to exist outside a lab.

Risk and Threat Considerations

Misused placeholder domains can create operational and security exposure when copied into production-adjacent workflows. The risk is not the RFC itself, but the failure to keep reserved names clearly separated from real endpoints, especially in automation, DNS configuration and documentation that gets reused verbatim.

Failure mechanism: A placeholder that looks like a real domain can be resolved, called or trusted in the wrong context, leading to unintended outbound traffic, misdirection, or confusion about what is controlled and what is only illustrative.

Impact: The result can include broken integrations, leakage of test traffic, false assumptions during validation, and in some environments an avoidable path for security or incident-response mistakes.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST CSF 2.0 and NIST SP 800-53 Rev 5 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST CSF 2.0GV.PO-01 — PolicyReserved-name use is a documentation and naming policy decision.
PR.DS-01 — Data-at-RestExamples and configs should avoid accidentally exposing operational data through copied placeholders.
Recommendation — Adopt a naming policy that requires reserved domains in examples and lab documentation. Protect sample configurations so placeholder values cannot be mistaken for production data.
NIST SP 800-53 Rev 5CM-8 — System Component InventoryReserved test names help distinguish non-production references from real assets in inventories.
Recommendation — Maintain inventories that clearly separate reserved test references from live system assets.

Practitioner Guidance

Why practitioners should care: RFC 2606 is a governance tool for keeping examples non-operational. Use it deliberately in docs, labs and reference configs so placeholder material remains recognisably separate from live DNS or internet-facing systems.

Common misunderstanding: Reserved names are not just a writing convenience. They are a control against confusion, and that matters when examples are copied into automation, shared with external parties or used to teach new staff how production systems should be named.

Practitioner takeaway: Standardise on reserved names for all public examples and test artefacts, then review your documentation templates so they never encourage real-world collisions.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org