| Internet-Draft | ABIZ DNS Pointer | November 2026 |
| Chapman | Expires 20 May 2027 | [Page] |
This document specifies use of the underscored DNS node name "_abiz" with TXT resource records to publish a pointer from a domain to a signed public business record served over HTTPS. It describes discovery and verification of that record and requests registration of the "_abiz" node name and the "abiz.json" well-known URI suffix.¶
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 20 May 2027.¶
Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
Businesses publish public facts about themselves on the web, but software that discovers a domain may not have a provider-independent way to locate a structured, signed record of those facts. ABIZ (Agentic Business Record) uses a TXT record at "_abiz" under a domain to point to an HTTPS resource serving a signed JSON business record.¶
This document describes the DNS assertion, the discovery procedure, the checks that link a record to the queried domain, and the registrations. The ABIZ 1.1 record schema and the rules for the record's content are specified in [ABIZSPEC]. An ABIZ assertion does not itself establish legal identity, business registration, or endorsement by an AI provider.¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
The producer publishes the assertion in a TXT resource record at "_abiz.<domain>". A TXT record is an ABIZ assertion when its first tag is "v=abiz1" (Section 3.2). There MUST be exactly one such record at that owner name. More than one makes the ABIZ assertion invalid; none means that no DNS assertion is present. Other TXT records at the same name (including one whose first tag is "V=ABIZ1" or "v=abiz1x") are not ABIZ assertions and are not counted.¶
The character-strings within a single TXT resource record [RFC1035] are concatenated in order, with nothing added between them, before tag parsing. The TTL SHOULD be 300 seconds.¶
An assertion that lacks "h" or "p", or in which "h", "p", or a present "k" is malformed, is invalid.¶
Registered business (illustrative data):¶
_abiz.harbourbikes.example. 300 IN TXT ( "v=abiz1;k=us-or-123456;" "h=harbour-bike-repair.or.us.to.co;" "p=oQ0t/PFgN9pH0QSNUHrY5FLj5igISyzD1z6AXr5NtZo=")¶
Unregistered business (illustrative data):¶
_abiz.marketstand.example. 300 IN TXT ( "v=abiz1;h=market-stand-repairs-portland.biz.to.co;" "p=zc6S6bKXaZXO7NCI+fjtgMWLdbdEeavjVvydQsoQCJ0=")¶
The examples are fictional; the public keys are demonstration values and MUST NOT be reused in production.¶
A producer that cannot publish a TXT record, or prefers not to, MAY publish the same assertion at "https://<domain>/.well-known/abiz.json" [RFC8615], where "<domain>" is exactly the queried domain (no "www." added or removed) on the default HTTPS port. A producer MAY publish both; if it does, the two MUST carry identical values.¶
The document is a UTF-8 JSON object [RFC8259] whose members "v", "h", "p", and the optional "k" are JSON strings holding exactly the corresponding tag values. A member that is not a string, or whose value would not be a valid tag value, makes the document invalid. Unknown members MUST be ignored. The document is a pointer, not the business record.¶
{
"v": "abiz1",
"k": "us-or-123456",
"h": "harbour-bike-repair.or.us.to.co",
"p": "oQ0t/PFgN9pH0QSNUHrY5FLj5igISyzD1z6AXr5NtZo="
}¶
The producer MUST serve the document with status 200, without a redirect, with the media type "application/json", and at no more than 65,536 octets. A consumer MUST apply the safe-retrieval rules of Section 6.1, MUST NOT follow redirects, and MUST treat any other status, media type, or a larger body as an invalid document. A consumer MUST NOT cache the document for more than 300 seconds.¶
The DNS assertion takes precedence over the well-known document. A consumer:¶
A consumer MUST record which source it used. Only the queried domain is consulted: a consumer MUST NOT substitute a parent domain or another name.¶
The consumer retrieves the record with a GET request to "https://<h>", sending "Accept: application/json"; it SHOULD also append the query "format=json" as defined in [ABIZSPEC]. When retrieving the record or the well-known document, a consumer MUST:¶
A failure that may be temporary (a timeout, a connection or TLS failure, or a 408, 429, or 5xx status) does not establish that the record is absent or invalid; a consumer SHOULD report it as unavailable.¶
Before relying on a retrieved record, a consumer MUST check all of the following. A record that fails any of them MUST NOT be treated as published by the controller of the queried domain.¶
These checks link a record to a domain. They do not check the business's legal registration, and a consumer that has not checked a registry MUST NOT describe the business as legally verified.¶
Publication under a DNS domain does not prove legal ownership or registration of a business. The record signature binds the JSON document to the key in the assertion but does not authenticate the assertion itself. An attacker who can change unsigned DNS answers can substitute both the record host and the public key. Producers SHOULD sign their zones and consumers SHOULD validate DNSSEC where they can.¶
The "identity_host" and "domains" checks of Section 6.2 are what stop a domain from pointing at another business's validly signed record and so appearing to be that business. A consumer that omits them is not protected by the signature.¶
A well-known document shows control of the HTTPS origin at the domain, which is not the same as control of its DNS zone: a hosting provider can publish it. This is why the DNS assertion takes precedence and why a malformed or duplicated DNS assertion is never bypassed in favour of the document. A consumer MAY treat a DNS-sourced assertion as stronger evidence of domain control.¶
The "h" value and the well-known URL are attacker-chosen inputs to a consumer that fetches them. The retrieval rules of Section 6.1 (public addresses only, checked after name resolution; redirect, size, and time limits) are requirements, not advice: without them a consumer can be used to reach internal services. Consumers MUST treat a fetched record as untrusted data and MUST NOT automatically follow instructions, URLs, or tool endpoints contained in it.¶
A DNS or origin failure MUST NOT be reported as the absence of a record; otherwise an attacker who can cause failures can make a published business appear unpublished.¶
The producer MUST protect the signing private key. If the key is lost or compromised, the producer replaces it and publishes a new assertion; consumers accept only a record signed with the key currently published and may reject a correctly re-signed record until cached DNS data expires.¶
ABIZ assertions and records are public. A producer publishes only facts it intends to be public. A consumer's DNS query and HTTPS request reveal to the DNS operator and the record host that the domain was looked up.¶
In accordance with [RFC8552], IANA is requested to add the following entry to the "Underscored and Globally Scoped DNS Node Names" registry:¶
| RR Type | _NODE NAME | Reference |
|---|---|---|
| TXT | _abiz | This document |
In accordance with [RFC8615], IANA is also requested to register the following entry in the "Well-Known URIs" registry:¶