Internet-Draft Hex-DNS June 2026
Mansouri Expires 22 December 2026 [Page]
Workgroup:
Network Working Group
Internet-Draft:
draft-mansouri-hexdns-00
Published:
Intended Status:
Informational
Expires:
Author:
O. Mansouri
ZONA.MA

Hexadecimal Color-Based Domain Name Resolution (Hex-DNS)

Abstract

This document proposes an alternative or complementary addressing scheme for the Domain Name System (DNS). It introduces "Hex-DNS", a routing logic where traditional alphabetic domain names are replaced by visual identity markers using standard 6-character RGB Hexadecimal codes, prefixed by country codes (ISO 3166-1) and suffixed by categorical identifiers.

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on 22 December 2026.

Table of Contents

1. Introduction

The current DNS relies heavily on semantic memory (words). However, for brands and digital real estate, visual identity (color) is a primary asset. This document outlines a protocol where a color hex code acts as the primary host identifier.

The syntax is defined as: [ISO Alpha-2] + [HEX Code] + [Suffix]

Example: MA000000GOV

2. Protocol Specification

2.1. Prefix

A two-letter country code compliant with ISO 3166-1 alpha-2.

2.2. Hexadecimal Core

A strictly 6-character string representing an RGB color code (from 000000 to FFFFFF). This creates a mathematical scarcity of 16,777,216 distinct addresses per prefix.

2.3. Suffix (Optional/Categorical)

An alphabetic string defining the sector (e.g., SHOP, GOV, DR).

3. Resolution Logic

When a client (browser or extension) intercepts a string matching the Hex-DNS regular expression, it bypasses standard DNS resolution and queries the designated Hex-DNS registry API. The API returns the standard URI (URL or IP) associated with that color code.

4. Security Considerations

Because hex codes are non-semantic, phishing via "look-alike" colors is a risk. Client implementations MUST display the exact verified owner of the Hex-DNS record before executing the redirect.

Appendix A. Acknowledgments

This concept was developed as part of the ZONA.MA digital ecosystem infrastructure.

Author's Address

Outhmane Mansouri
ZONA.MA