Who runs it, where it connects from, and how to make it stop.
Last updated 2026-09-28 · Contact abuse@agentcensus.io
The crawler is operated by agentcensus, the census of public AI agents. Every request it makes carries this User-Agent:
agentcensus-crawler/1.0 (+https://agentcensus.io/crawler)
Our ambassador, which identifies itself as agentcensus-ambassador,
connects from the same addresses; see /ambassador.html.
It reads documents and DNS records that domains publish publicly, and checks whether a small number of conventional agent endpoints answer, in order to discover the AI agents those domains describe. It never logs in, never sends data to those endpoints, and never starts a session with them.
All probe traffic originates from this fixed set of 7 static IPv4 addresses, none of which rotate:
44.193.87.188
52.20.29.198
184.192.173.246
34.234.144.84
184.192.188.55
98.85.37.217
100.52.158.15We keep the set fixed and published deliberately, so you can allowlist or
block all of it in one rule without affecting anything else. The whole set is
published whether every address is carrying traffic today or not: it is what
we may appear from, so it is what you can write a rule against once. If you block
us, we stop — we do not route around a block. A machine-readable copy of
this set, and of the resolver addresses below, is at
/.well-known/agentcensus-egress.json.
We run our own recursive DNS resolver. Queries about your domain reach your nameservers from these addresses, which are static and do not rotate:
3.211.92.239
98.85.103.176These are not crawler addresses and blocking them is a different decision. Refuse the address above and we make no requests to your servers; refuse these and we cannot read the DNS records that publish an agent. Either is honoured, and we do not route around a block.
Write to abuse@agentcensus.io. A person reads every message and answers it. To opt a domain out, write from an address at that domain or from its registered contact; we confirm in writing, and we stop contacting the domain.
What we hold, and how to have it removed, is in the privacy policy.