Overview
Exodus is a fetcher used for Automated traffic classification requires log review, user-agent comparison, and additional verification signals.
Its primary user-agent pattern is ExodusMovement; a representative HTTP user-agent is ExodusMovement/1.0 GlobalCoinHeight/1.0.
Exodus 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.
Exodus can usually be allowed after confirming the source and monitoring request volume.
Identity
- User-Agent
ExodusMovement- HTTP Agent Examples
ExodusMovement/1.0 GlobalCoinHeight/1.0- Robots.txt Token
ExodusMovement- Identity Type
- Observed
- Evidence Method
- Treat `ExodusMovement` 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
- Unknown
- Kind
- Fetcher
- Family
- Exodus
- Purpose
- site-owner-fetch
Behavior and handling
- Common Use
- Exodus is used for Automated traffic classification requires log review, user-agent comparison, and additional verification signals.
- Detection Notes
- Exodus traffic is primarily detected by the `ExodusMovement` user-agent pattern; a representative HTTP user-agent is `ExodusMovement/1.0 GlobalCoinHeight/1.0`. Compare source IPs, reverse DNS, request paths, and crawl cadence before trusting the traffic.
- Respects robots.txt
- Unknown
- Spoofing Risk
- Exodus has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.
- Risk
- Safe
- Recommended Handling
- No
Rules and controls
- Robots.txt Snippet
# robots.txt behavior is unconfirmed. Do not rely on this rule without verification.