Your name on the door, our land underneath.
You already have a domain. With Bring Your Own Identity, your agents stop living under agents.whisper.online and start living under a name you own - {your-domain}, or a subdomain like agents.{your-domain}. You bring the domain. We run the network and the registry that vouch for the identities inside it.
Nothing about the proofs changes. A stranger still confirms an agent is real with one dig, no Whisper code. The only difference is the name they read back: it's yours.
Every new agent, minted under your name.
Once your domain is onboarded and proven, every new agent is minted directly under it - as a{hex}.{your-domain} - and the whole identity record follows the name in:
- A real, routable IPv6
/128out of2a04:2a01::/32(AS219419, RIPE-allocated space we announce). The address stays ours; only the name moves. - Reverse DNS that spells the address back as a name under your domain.
- A DANE-EE
TLSApin published in your zone, which we sign under theDSyou publish at your parent - so a DANE-aware peer trusts the agent with no Whisper CA and no public CA. - An RDAP record and a WHOIS record for the
/128, answered live, linking up to RIPE. - A signed identity document and the per-identity transparency feed, under your name.
Your name out front. Our ground holding it up.
Onboard, prove by delegation, mint under your name
Onboard your domain.
At your parent zone - the apex, or a subdomain you pick - delegate the name to our nameservers and publish the DS we hand you for the signing key. This is the only thing you publish, and it goes in your own DNS:
; in {your-domain}'s own zone (or a subdomain - your choice)
{your-domain}. NS ns1.whisper.online.
{your-domain}. NS ns2.whisper.online.
{your-domain}. DS <digest 2 (SHA-256) and 4 (SHA-384), handed to you>
Prefer to keep your apex untouched? Delegate a subdomain instead - the records are identical, just under the name you choose:
agents.{your-domain}. NS ns1.whisper.online.
agents.{your-domain}. NS ns2.whisper.online.
agents.{your-domain}. DS <digest 2 (SHA-256) and 4 (SHA-384)>
Your parent zone must be signed: an unsigned TLD breaks the DNSSEC chain above your domain, and a chain that does not validate can't be proven. And don't add glue for our out-of-bailiwick nameservers; they resolve on their own, and glue here only gets in the way.
Prove it by delegation.
The delegation itself is the proof. There's no token to copy, no file to host, no TXT challenge to paste. Once you've published the records above, we poll your parent's servers, then public resolvers from several vantage points, until the delegation and a matching DS are seen live in the wild. Delegation plus DS, observed independently, is the proof.
It is fail-closed: an unproven domain is never authorized, so a name you don't actually control can never be claimed. And it holds over time - a daily continuity sweep re-checks every delegated domain. If the chain ever moves away from us, the domain goes out of order on its own, without anyone having to notice.
Identities minted under your name.
With the domain proven, new agents are minted directly under it. Where a Whisper-hosted agent would have been a{hex}.agents.whisper.online, yours becomes a{hex}.{your-domain}.
For example, a real agent under everwatch.io, a domain we brought ourselves:
a4f988041b1326d8a.everwatch.io (member name: demo.everwatch.io)
The reverse DNS, RDAP, WHOIS, DANE pin and signed identity document all follow that name into your domain. The cleanest trust story is the one you anchor yourself: your zone chains to the public root through the DS you publish, so the agent's TLSA pin is trusted straight from DNS - no certificate authority in the path at all. We still sign the zone; the DS is how you decide that our signature counts, and how you withdraw it.
Nothing breaks. Onboarding is additive.
You don't migrate, and you don't cut over.
- Identities already issued under
agents.whisper.onlinekeep resolving, for good. The custom domain takes over only for new mints. - Your existing DNS keeps working. If you delegate a subdomain, your apex and every record on it are untouched. If you delegate the apex, only the names under it that we serve are affected.
- The
/128never moves. The address stays ours (AS219419,2a04:2a01::/32); only the name it answers to becomes yours.
A configurable per-operator capacity cap keeps signing and replication load bounded, and fails closed with a clear message rather than a surprise.
The proofs don't change. They just read your name.
Anyone, with stock tools and no Whisper code, confirms an agent under your domain exactly the way they would one under ours. The commands below are a real capture (20 Oct 2026) against a real agent under everwatch.io, a domain we brought ourselves; swap in your own a{hex} name and address once you're onboarded. The full worked example, from delegation to first mint, is on the registry record.
# one under ours, rendered live: the first resident on agents.whisper.online
$ dig -x 2a04:2a01:b69a:6717:e3b0:51ff:3bf7:f478 +short
ae3b051ff3bf7f478.tdc38e7c55bad3306a92b830f9bb1e4f9.agents.whisper.online
# one under everwatch.io, captured 20 Oct 2026
$ dig +tcp +dnssec @1.1.1.1 a4f988041b1326d8a.everwatch.io AAAA
# (header and answer shown)
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6383
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
; EDNS: version: 0, flags: do; udp: 1232
a4f988041b1326d8a.everwatch.io. 60 IN AAAA 2a04:2a01:9b6d:23e8:4f98:8041:b132:6d8a
a4f988041b1326d8a.everwatch.io. 60 IN RRSIG AAAA 13 3 60 20261022130000 20261020120000 61903 everwatch.io. 4ulZgfr6+O6hkOeIQJ9oRoP1I5e0sVnVxlxdZXdBHWiD+wzRWAcQgyqr LDq8yxMC3/RjIErO0X3lmFvwQDNPnQ==
$ dig +tcp +dnssec @1.1.1.1 -x 2a04:2a01:9b6d:23e8:4f98:8041:b132:6d8a
# (header and answer shown)
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29670
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
; EDNS: version: 0, flags: do; udp: 1232
a.8.d.6.2.3.1.b.1.4.0.8.8.9.f.4.8.e.3.2.d.6.b.9.1.0.a.2.4.0.a.2.ip6.arpa. 60 IN PTR a4f988041b1326d8a.everwatch.io.
a.8.d.6.2.3.1.b.1.4.0.8.8.9.f.4.8.e.3.2.d.6.b.9.1.0.a.2.4.0.a.2.ip6.arpa. 60 IN RRSIG PTR 13 34 60 20261022130000 20261020120000 58485 1.0.a.2.4.0.a.2.ip6.arpa. l1jqJptg/RDgho2fn9VwLWnNO6sRFcgc54MFcKRVmvCCgRDhdJTQnDSA L9RCHM1zGetiS7jl9DelUWer4Glx2w==
$ dig +tcp +dnssec @1.1.1.1 _443._tcp.a4f988041b1326d8a.everwatch.io TLSA
# (header and answer shown)
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9605
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
; EDNS: version: 0, flags: do; udp: 1232
_443._tcp.a4f988041b1326d8a.everwatch.io. 60 IN TLSA 3 1 1 BFD4CF2E0275244754B2F99FE0803D020D03EA2C8A0052407DAFFB55 E6748DDA
_443._tcp.a4f988041b1326d8a.everwatch.io. 60 IN RRSIG TLSA 13 5 60 20261022130000 20261020120000 61903 everwatch.io. JWwOpuuhQK7EpTJZoUiEXifGllBK5YRy34YbwKtD64vBbxqyp5F1XcbI nrFaTJWYHtTuF+hHY3GXtcZmIxRHFA==
$ openssl s_client -connect [2a04:2a01:9b6d:23e8:4f98:8041:b132:6d8a]:443 \
-servername a4f988041b1326d8a.everwatch.io \
-dane_tlsa_domain a4f988041b1326d8a.everwatch.io \
-dane_tlsa_rrdata "3 1 1 BFD4CF2E0275244754B2F99FE0803D020D03EA2C8A0052407DAFFB55E6748DDA"
# (trimmed to the verification lines)
CONNECTED(00000003)
subject=CN = a4f988041b1326d8a.everwatch.io
issuer=CN = Whisper Agent Identity Issuing CA, O = viaGraph B.V.
Verification: OK
DANE TLSA 3 1 1 ...8a0052407daffb55e6748dda matched EE certificate at depth 0
New, TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384
Verify return code: 0 (ok)
$ curl -s https://rdap.whisper.online/ip/2a04:2a01:9b6d:23e8:4f98:8041:b132:6d8a \
| jq -c '{handle, name, registrant: [.entities[] | select(.roles | index("registrant")) | .handle], up: [.links[] | select(.rel == "rdap-related-up") | .href], notice: .notices[0].title}'
{"handle":"a4f988041b1326d8a","name":"demo","registrant":["everwatch.io."],"up":["https://rdap.db.ripe.net/ip/2a04:2a01::/32"],"notice":"Published by the holder"}
$ whois -h whois.whisper.online a4f988041b1326d8a.everwatch.io | grep -E '^(inet6num|netname|agent|tenant|fqdn|status|origin|org|aggregate|source) '
inet6num 2a04:2a01:9b6d:23e8:4f98:8041:b132:6d8a
netname demo
agent a4f988041b1326d8a
tenant everwatch.io.
fqdn a4f988041b1326d8a.everwatch.io
status active
origin AS219419
org viaGraph B.V.
aggregate 2a04:2a01::/32
source WHISPER
The AD flag is a resolver's verdict. delv does the validation itself, checking every signature from the root trust anchor down, so the resolver it asks does not have to be trusted (captured 20 Oct 2026):
$ delv @1.1.1.1 demo.everwatch.io AAAA
# (RRSIG lines omitted)
; fully validated
demo.everwatch.io. 60 IN CNAME a4f988041b1326d8a.everwatch.io.
a4f988041b1326d8a.everwatch.io. 60 IN AAAA 2a04:2a01:9b6d:23e8:4f98:8041:b132:6d8a
$ delv @1.1.1.1 a4f988041b1326d8a.everwatch.io AAAA
# (RRSIG lines omitted)
; fully validated
a4f988041b1326d8a.everwatch.io. 60 IN AAAA 2a04:2a01:9b6d:23e8:4f98:8041:b132:6d8a
$ delv @1.1.1.1 _443._tcp.a4f988041b1326d8a.everwatch.io TLSA
# (RRSIG lines omitted)
; fully validated
_443._tcp.a4f988041b1326d8a.everwatch.io. 60 IN TLSA 3 1 1 BFD4CF2E0275244754B2F99FE0803D020D03EA2C8A0052407DAFFB55 E6748DDA
$ delv @1.1.1.1 -x 2a04:2a01:9b6d:23e8:4f98:8041:b132:6d8a
# (RRSIG lines omitted)
; fully validated
a.8.d.6.2.3.1.b.1.4.0.8.8.9.f.4.8.e.3.2.d.6.b.9.1.0.a.2.4.0.a.2.ip6.arpa. 60 IN PTR a4f988041b1326d8a.everwatch.io.
Every DNS answer carries a DNSSEC signature you can validate yourself with delv, and the forward chain runs through the DS at your parent. The PTR is signed in our reverse zone, and the per-/128 RDAP and WHOIS records are ours, with your domain as the registrant.
What stays ours, what becomes yours.
| Yours | Ours | |
|---|---|---|
| The name | {your-domain} and the agent names under it | - |
| DNSSEC anchor | Your DS at your parent | the zone's signing key and signatures |
| The address | - | the /128 from 2a04:2a01::/32 |
| Browser certificates | - | not offered under a domain you bring yet; every identity gets a DANE-EE pin |
| The network | - | AS219419, BGP, RPKI, MANRS |
| The registry | - | RDAP, WHOIS, the PTR in our reverse zone, transparency log |
You hold the name; we hold the ground.
Live, and self-serve with your own API key.
The serving engine that makes this possible - multiple forward zones, per-domain DANE, RDAP/WHOIS/reverse and the transparency ledger under a custom name - is live, and onboarding is self-serve: whisper domain submit {your-domain} --json, or whisper.agents({op:'domain'}) with your own API key, hands back the records to publish, and the proof is observed on its own.
Until your domain is verified, your agents live under agents.whisper.online exactly as they do today, with every proof already in place. When it is, new mints land under your name and nothing you already have changes.
The full registry record - the delegation recipe, the proof policy, and the issuance and transparency details - is published on our own registry at nic.whisper.online/registry.
Bring your name home.
Your agents won't know the difference. They just know they're home - now under a name that's yours.