Overview
atlassian-bot is a search crawler from Atlassian used for search indexing, URL discovery, page rendering, result freshness, and search-quality checks.
Its primary user-agent pattern is atlassian-bot.
atlassian-bot 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.
atlassian-bot should be reviewed against site policy, source evidence, crawl rate, and requested paths before a permanent allow or block rule is created.
Identity
- User-Agent Pattern
-
atlassian-bot - HTTP Agent Examples
-
atlassian-bot - Robots Token
- atlassian-bot
- Identity Type
- Observed
- Evidence Method
- Treat `atlassian-bot` 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
- Kind
- Crawler
- Family
- atlassian-bot
- Purpose
- Indexing
Behavior and handling
- Common Use
- atlassian-bot is used for search indexing, URL discovery, page rendering, result freshness, and search-quality checks.
- Detection Notes
- atlassian-bot traffic is primarily detected by the `atlassian-bot` user-agent pattern. Compare source IPs, reverse DNS, request paths, and crawl cadence with Atlassian infrastructure before trusting the traffic.
- Respects robots.txt
- Unknown
- Spoofing Risk
- atlassian-bot has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.
- Risk
- Neutral
- Recommended Handling
- Depends
Rules and controls
- Robots.txt Snippet
-
# robots.txt behavior is unconfirmed. Do not rely on this rule without verification.
Relationships
- Operator
- Atlassian 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.