Overview
Accoona-AI-Agent is a search crawler from Accoona used for search indexing, URL discovery, page rendering, result freshness, and search-quality checks.
Its primary user-agent pattern is Accoona-AI-Agent.
Accoona-AI-Agent is Unverified at the identity-evidence level. The listed identity remains useful for detection, but this record does not currently contain authoritative evidence sufficient to authenticate the identity claim.
Robots.txt behavior is not currently confirmed.
Accoona-AI-Agent should be monitored first, then rate-limited or blocked if the crawl rate, paths, or behavior are unwanted.
Identity
- User-Agent Pattern
-
Accoona-AI-Agent - HTTP Agent Examples
-
Accoona-AI-Agent - Robots Token
- Accoona-AI-Agent
- Identity Type
- Observed
- Evidence Method
- Treat `Accoona-AI-Agent` as an identity signal only. Confirm it with current operator documentation, cryptographic verification, forward-confirmed reverse DNS, source-network ownership, or other authoritative evidence before trusting the claimed identity.
Classification
- Type
- Search engine crawler
- Kind
- Search engine crawler
- Family
- Accoona
- Purpose
- Search indexing
Behavior and handling
- Common Use
- Accoona-AI-Agent is used for search indexing, URL discovery, page rendering, result freshness, and search-quality checks.
- Detection Notes
- Accoona-AI-Agent traffic is primarily detected by the `Accoona-AI-Agent` user-agent pattern. Compare source IPs, reverse DNS, request paths, and crawl cadence with Accoona infrastructure before trusting the traffic.
- Respects robots.txt
- Unknown
- Spoofing Risk
- Accoona-AI-Agent has high spoofing risk because the pattern is low-confidence or observation-based; do not trust the user-agent by itself.
- Risk
- Neutral
- Recommended Handling
- Monitor
Rules and controls
- Robots.txt Snippet
-
# robots.txt behavior is unconfirmed. Do not rely on this rule without verification.
Relationships
- Operator
- Accoona Checked 2026-08-07
Relationships without an Evidence link are normalized from the canonical directory record. They should not be interpreted as independent proof of physical presence or request origin.