Other automated crawlers
Panscient is a bot that crawls the web automatically. Compiles data on businesses and business professionals that is structured using AI and machine learning. It is documented as honouring robots.txt, but no IP range list or reverse-DNS convention is published, so a request carrying this user agent cannot be proven genuine.
Request says
"Panscient"
Checked against
Nothing published
Live check
No operator check exists for Panscient. This still shows what the address really is.
Reference
| User agent | PanscientToken only: match on the substring. |
|---|---|
| Operator | Panscient |
| Purpose | Data collection and analysis using machine learning and AI. |
| Respects robots.txt | Honourssource |
| Verification method | Claim onlyNone published, user agent only No IP range file and no reverse-DNS convention have been published for this agent. The user-agent string is the only signal, and any client can send it, so treat a match as a claim rather than proof. |
| Crawl pattern | The Panscient web crawler will request a page at most once every second from the same domain name or the same IP address. |
| Robots.txt tokens | Panscientpanscient.com |
| Operator documentation | None published |
Compiles data on businesses and business professionals that is structured using AI and machine learning.
robots.txt
Paste one at the root of your domain. Rules are per token.
User-agent: Panscient
User-agent: panscient.com
Disallow: /User-agent: Panscient
User-agent: panscient.com
Allow: /User-agent: Panscient
User-agent: panscient.com
Allow: /
Disallow: /account/
Disallow: /checkout/
Disallow: /searchEdit the Disallow paths to match your own URLs.
Blocking Panscient stops this specific token. Check your logs afterwards, because operators that ignore robots.txt often come back under a different name.
Build a file for every crawlerFAQ
Panscient is a bot that crawls the web automatically. Compiles data on businesses and business professionals that is structured using AI and machine learning. It is documented as honouring robots.txt, but no IP range list or reverse-DNS convention is published, so a request carrying this user agent cannot be proven genuine.
Yes. The operator documents that Panscient reads robots.txt and follows Disallow rules for its own token. Rules take effect on the next fetch of the file, which can be hours or days after you publish them.
You cannot, at least not from the request itself. No IP range file and no reverse-DNS convention have been published for this agent. The user-agent string is the only signal, and any client can send it, so treat a match as a claim rather than proof. Compare the source IP against hosting and datacenter ranges instead, and rate limit anything that behaves like a crawler.
Add these user-agent tokens (Panscient, panscient.com) to robots.txt with Disallow: /. If the crawler ignores robots.txt, match the user agent at your CDN or reverse proxy and return 403 there instead.
Blocking Panscient stops this specific token. Check your logs afterwards, because operators that ignore robots.txt often come back under a different name.