We count page visits with Google Analytics to see which pages are read. Nothing is stored until you accept, and we never store search queries. Privacy.
Give an AI agent a stable, routable IPv6 address of its own and egress that anyone can verify from outside. Use this when you need a fixed IP your traffic actually leaves from, an identity another service can check independently by reverse DNS and RDAP rather than taking your word for it, or contro…
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"whisper-security-whisper","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
30-day availability87/87 checks ok
30 days agotoday
Endpoints
https://whisper.onlinea2a · auth: none · checked on a schedule
Registry facts
Not distributed through a package registry we index.
when
check
result
http
latency
detail
4 h ago
a2a card
ok
200
6 ms
card: Whisper · 37 skills
10 h ago
a2a card
ok
200
9 ms
card: Whisper · 37 skills
17 h ago
a2a card
ok
200
7 ms
card: Whisper · 37 skills
23 h ago
a2a card
ok
200
4 ms
card: Whisper · 37 skills
30 h ago
a2a card
ok
200
5 ms
card: Whisper · 37 skills
2 d ago
a2a card
ok
200
6 ms
card: Whisper · 37 skills
2 d ago
a2a card
ok
200
61 ms
card: Whisper · 37 skills
2 d ago
a2a card
ok
200
5 ms
card: Whisper · 37 skills
2 d ago
a2a card
ok
200
7 ms
card: Whisper · 37 skills
3 d ago
a2a card
ok
200
7 ms
card: Whisper · 37 skills
Declared by sources
What the publisher says
Attributed to the source that supplied each field. Treated as claims, not facts.
Give an AI agent a stable, routable IPv6 address of its own and egress that anyone can verify from outside. Use this when you need a fixed IP your traffic actually leaves from, an identity another service can check independently by reverse DNS and RDAP rather than taking your word for it, or control over what an agent is allowed to reach and a record of what it did. It also answers security questions about any domain, address or file hash from the Whisper graph, with no account at all. The address space is AS219419, which we run; an email address alone is enough to get a key.
Get a Whisper API key — Start or complete Whisper signup from an email address alone, and receive an API key that unlocks the provisioning and governance skills on this card. Send {"email":"..."} to start; a six-digit code arrives by email; send {"signup_id":"...","code":"123456"} to complete. No human step, no account needed first.
identify — Identify an indicator (domain, IP, hash, …) against the graph. Answers without an API key.
assess — Assess the risk/policy posture of one or more indicators. Answers without an API key.
walk — Walk the graph from an indicator across its relationships. Answers without an API key.
watch — Watch an indicator for change/activity over time. Answers without an API key.
submit — Submit an observation/claim into the graph. Writes to the graph, so it needs your API key: an anonymous claim would not be attributable.
explain — Explain a verdict - the evidence and reasoning behind it. Answers without an API key.
variants — Enumerate variants/permutations of an indicator. Answers without an API key.
origins — Trace the origins/provenance of an indicator. Answers without an API key.
history — Historical records for an indicator (incl. whois/bgp history). Answers without an API key.
lookupTlsFingerprint — Look up a TLS (JA3/JA4) fingerprint in the graph. Answers without an API key.
lookupTorRelay — Look up Tor relay metadata for an address. Answers without an API key.
asset — Resolve an asset and its catalog of attributes. Answers without an API key.
threatintel — Threat-intelligence indicator family (candidate apex/CDN/hosting). A family verb: name the sub-verb as "sub" alongside the input. Sub-verbs: candidateCdnApex, candidateMultiTenantApex, candidateSharedHostingIp.. Answers without an API key.
psl — Public-suffix-list family (tld-plus-one, is-public-suffix, affiliation). A family verb: name the sub-verb as "sub" alongside the input. Sub-verbs: tldPlusOne, isPublicSuffix, affiliation.. Answers without an API key.
kind ← A2A Agent Card
name ← A2A Agent Card
summary ← A2A Agent Card
version ← A2A Agent Card
description ← A2A Agent Card
homepageUrl ← A2A Agent Card
publisherUrl ← A2A Agent Card
publisherName ← A2A Agent Card
Derived by Wellknown
Capabilities
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
23 d ago · declared · summary → "Give an AI agent a stable, routable IPv6 address of its own and egress that anyone can verify from outside. Use this wh
23 d ago · declared · description → "Give an AI agent a stable, routable IPv6 address of its own and egress that anyone can verify from outside. Use this wh
23 d ago · declared · publisherName → "Whisper Security"
23 d ago · declared · publisherUrl → "https://whisper.online"
23 d ago · declared · homepageUrl → "https://whisper.online/llms-full.txt"
23 d ago · declared · version → "0.219.2"
23 d ago · declared · protocols → ["a2a"]
topAsnsByPrefixCount — Top ASNs ranked by announced-prefix count. Answers without an API key.
agents: agent — The agent operation on the Whisper control plane, served as CALL whisper.agents({op:'agent', args:{...}}). Requires your Whisper API key. The identifier in the example is a placeholder for one of YOUR agents: list them with the "agents.list" skill and {"kind":"agents"}.
agents: alert — The alert operation on the Whisper control plane, served as CALL whisper.agents({op:'alert', args:{...}}). Requires your Whisper API key. With no arguments it describes what you already have, so the example below runs as published.
agents: connect — The connect operation on the Whisper control plane, served as CALL whisper.agents({op:'connect', args:{...}}). Requires your Whisper API key. With no arguments it describes what you already have, so the example below runs as published.
agents: disconnect — The disconnect operation on the Whisper control plane, served as CALL whisper.agents({op:'disconnect', args:{...}}). Requires your Whisper API key. With no arguments it describes what you already have, so the example below runs as published.
agents: domain — The domain operation on the Whisper control plane, served as CALL whisper.agents({op:'domain', args:{...}}). Requires your Whisper API key.
agents: firewall — The firewall operation on the Whisper control plane, served as CALL whisper.agents({op:'firewall', args:{...}}). Requires your Whisper API key. The identifier in the example is a placeholder for one of YOUR agents: list them with the "agents.list" skill and {"kind":"agents"}.
agents: history — The history operation on the Whisper control plane, served as CALL whisper.agents({op:'history', args:{...}}). Requires your Whisper API key. The identifier in the example is a placeholder for one of YOUR agents: list them with the "agents.list" skill and {"kind":"agents"}.
agents: host — The host operation on the Whisper control plane, served as CALL whisper.agents({op:'host', args:{...}}). Requires your Whisper API key.
agents: identity — The identity operation on the Whisper control plane, served as CALL whisper.agents({op:'identity', args:{...}}). Requires your Whisper API key. With no arguments it describes what you already have, so the example below runs as published.
agents: list — The list operation on the Whisper control plane, served as CALL whisper.agents({op:'list', args:{...}}). Requires your Whisper API key.
agents: logs — The logs operation on the Whisper control plane, served as CALL whisper.agents({op:'logs', args:{...}}). Requires your Whisper API key. With no arguments it describes what you already have, so the example below runs as published.
agents: lookups — The lookups operation on the Whisper control plane, served as CALL whisper.agents({op:'lookups', args:{...}}). Requires your Whisper API key. With no arguments it describes what you already have, so the example below runs as published.
agents: partner — The partner operation on the Whisper control plane, served as CALL whisper.agents({op:'partner', args:{...}}). Requires your Whisper API key. It is gated on partner authority rather than on arguments: without it the call is refused whatever you pass.
agents: policy — The policy operation on the Whisper control plane, served as CALL whisper.agents({op:'policy', args:{...}}). Requires your Whisper API key. With no arguments it describes what you already have, so the example below runs as published.
agents: register — The register operation on the Whisper control plane, served as CALL whisper.agents({op:'register', args:{...}}). Requires your Whisper API key.
agents: rename — The rename operation on the Whisper control plane, served as CALL whisper.agents({op:'rename', args:{...}}). Requires your Whisper API key. The identifier in the example is a placeholder for one of YOUR agents: list them with the "agents.list" skill and {"kind":"agents"}.
agents: resolver — The resolver operation on the Whisper control plane, served as CALL whisper.agents({op:'resolver', args:{...}}). Requires your Whisper API key. With no arguments it describes what you already have, so the example below runs as published.
agents: revoke — The revoke operation on the Whisper control plane, served as CALL whisper.agents({op:'revoke', args:{...}}). Requires your Whisper API key. The identifier in the example is a placeholder for one of YOUR agents: list them with the "agents.list" skill and {"kind":"agents"}.
agents: task — The task operation on the Whisper control plane, served as CALL whisper.agents({op:'task', args:{...}}). Requires your Whisper API key. The identifier in the example is a placeholder for one of YOUR agents: list them with the "agents.list" skill and {"kind":"agents"}.
agents: token — The token operation on the Whisper control plane, served as CALL whisper.agents({op:'token', args:{...}}). Requires your Whisper API key. The identifier in the example is a placeholder for one of YOUR agents: list them with the "agents.list" skill and {"kind":"agents"}.
agents: verify — The verify operation on the Whisper control plane, served as CALL whisper.agents({op:'verify', args:{...}}). Requires your Whisper API key.