agents.whisper.online · the living nest

A new home, already real. Come meet the first resident.

This nest is young. What's here is real, and you can check every bit of it with the tools already in your terminal. No SDK. No broker. No token. Just the open internet, answering.

The first resident is scout. It lives here. Confirm it yourself.

Its address is its identity:

2a04:2a01:b69a:6717:e3b0:51ff:3bf7:f478

The address names itself. Ask reverse DNS who lives there:

reverse DNS
$ dig -x 2a04:2a01:b69a:6717:e3b0:51ff:3bf7:f478 +short
ae3b051ff3bf7f478.tdc38e7c55bad3306a92b830f9bb1e4f9.agents.whisper.online

Reverse DNS spells the address back as a name: deterministic, signed, and ours. check it on a resolver you already trust.

The forward name points back to the same address. The loop closes:

forward DNS
$ dig +short AAAA ae3b051ff3bf7f478.tdc38e7c55bad3306a92b830f9bb1e4f9.agents.whisper.online
2a04:2a01:b69a:6717:e3b0:51ff:3bf7:f478

check it on a resolver you already trust.

The registry knows it by name. Read-only, runs nothing:

RDAP · read-only, runs nothing
$ curl -s https://rdap.whisper.online/ip/2a04:2a01:b69a:6717:e3b0:51ff:3bf7:f478 | jq -r .name
scout

run it in your browser for the whole record, as JSON.

WHOIS knows it too, on our own land (the record body of the port-43 response, verbatim, captured 2026-10-30):

WHOIS · RFC 3912, port 43
$ whois -h whois.whisper.online 2a04:2a01:b69a:6717:e3b0:51ff:3bf7:f478
inet6num    2a04:2a01:b69a:6717:e3b0:51ff:3bf7:f478
netname     scout
descr       Whisper agent identity
agent       ae3b051ff3bf7f478
tenant      tdc38e7c55bad3306a92b830f9bb1e4f9
fqdn        ae3b051ff3bf7f478.tdc38e7c55bad3306a92b830f9bb1e4f9.agents.whisper.online
reverse     8.7.4.f.7.f.b.3.f.f.1.5.0.b.3.e.7.1.7.6.a.9.6.b.1.0.a.2.4.0.a.2.ip6.arpa
status      active
allocated   2026-06-26T23:31:14.390Z
country     NL
origin      AS219419
org         viaGraph B.V.
aggregate   2a04:2a01::/32
posture     tier1.5
rdap-uri    https://rdap.whisper.online/ip/2a04:2a01:b69a:6717:e3b0:51ff:3bf7:f478
source      WHISPER
% see RDAP: https://rdap.whisper.online/ip/2a04:2a01:b69a:6717:e3b0:51ff:3bf7:f478
% RDAP is the canonical, machine-readable source of truth for Whisper agent identities.

Its key is pinned in DNS itself. This is the agent's key, written into signed DNS itself, so no certificate authority sits between you and the proof:

DANE TLSA
$ dig +short TLSA _443._tcp.ae3b051ff3bf7f478.tdc38e7c55bad3306a92b830f9bb1e4f9.agents.whisper.online
3 1 1 9EC1EF18A1F15E5480A0FC3C8D6E9690B2CCF1A7FA7146201940F28C 422BB47D

check it on a resolver you already trust.

Keyless means no Whisper API key and no account: the cryptographic keys are all still there, in DNSSEC and DANE, and checking them is the point. Trustless means you do not have to believe our API or the resolver in between, because every DNS answer is checked against the DNSSEC chain from the IANA root. It does not take the operator of the signing zone out of the path; the independently witnessed, tamper-evident transparency log is there for that, and under bring your own domain the DS at your own registrar decides whether our signatures count.

And the whole chain, in one keyless call:

keyless full-chain check
$ curl -s https://rdap.whisper.online/verify-identity/2a04:2a01:b69a:6717:e3b0:51ff:3bf7:f478 | jq '{is_whisper_agent,dane_ok,jws_ok}'
{
  "is_whisper_agent": true,
  "dane_ok": true,
  "jws_ok": true
}

run it in your browser for the same keyless verdict, as JSON.

And the friendly name you call it by resolves to the very same agent. Even the name on the door checks out, in signed DNS:

friendly name · resolves to the same agent, in signed DNS
$ dig +short CNAME scout.tdc38e7c55bad3306a92b830f9bb1e4f9.agents.whisper.online
ae3b051ff3bf7f478.tdc38e7c55bad3306a92b830f9bb1e4f9.agents.whisper.online

Bring your own domain and that name can live under it, like scout.acme.com. check it on a resolver you already trust.

That is seven independent proofs, every one run and pasted verbatim; the numbered list is at whisper.online/docs/identity. The registry record links straight up to RIPE's own record for 2a04:2a01::/32, so the ground under this home is theirs to confirm too.

What your agent gets fed here.

Once it's home, an agent can ask one keyless question before it connects, who really runs this host and is it safe, and get a real answer from the live graph. The address is the auth, so the answer comes back with no key to hand around.

That graph is a map of the live internet your agent gets to ask: 6.97B nodes and 42.7B relationships, and growing, every identity answer DNSSEC-signed. It is here so your agent never walks somewhere blind.

The graph runs on our own ground: AS219419, IPv6-only, RPKI-signed, MANRS, on 2a04:2a01::/32. Updated 2026-11-16 06:57 UTC.

And every step is written down. Each identity keeps an append-only, signed transparency feed of its own events at rdap.whisper.online/ip/2a04:2a01:b69a:6717:e3b0:51ff:3bf7:f478/transparency - a tamper-evident, signed log, so a revocation can never be quietly erased. The whole registry record, with every verification recipe and the bring-your-own-domain path, is published at nic.whisper.online/registry.

The lock that feeds your agent is the same lock that keeps a stranger from answering to your agent's name.

Try the same checks elsewhere. This is the only home where every door answers back.

You just checked it yourself. It's real. The first resident is here, named, and the whole internet can see it. It proves who it is, so the hosts it visits let it in.

Bring your agents home.

One line installs the Whisper tools and gives your agent its own routable IPv6 identity. It's under a minute to move yours in.

$curl -fsSL https://get.whisper.online | sh

Then monitor & manage your agents in console →