Overview
GitHub Camo is a link preview bot from GitHub used for link unfurling, rich-card generation, social previews, messaging previews, and page metadata fetching.
Its primary user-agent pattern is github-camo; related patterns include GitHub Camo.
GitHub Camo 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.
GitHub Camo can usually be allowed after confirming the source and monitoring request volume.
Identity
- User-Agent Pattern
-
github-camo - Aliases
- GitHub Camo
- HTTP Agent Examples
-
github-camo - Robots Token
- github-camo
- Identity Type
- Observed
- Evidence Method
- Treat `github-camo` 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
- Preview
- Kind
- Preview
- Family
- GitHub
- Purpose
- Preview
Behavior and handling
- Common Use
- GitHub Camo is used for link unfurling, rich-card generation, social previews, messaging previews, and page metadata fetching.
- Detection Notes
- GitHub Camo traffic is primarily detected by the `github-camo` user-agent pattern; related patterns include `GitHub Camo`. Compare source IPs, reverse DNS, request paths, and crawl cadence with GitHub infrastructure before trusting the traffic.
- Respects robots.txt
- Unknown
- Spoofing Risk
- GitHub Camo 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
- Depends
Rules and controls
- Robots.txt Snippet
-
# robots.txt behavior is unconfirmed. Do not rely on this rule without verification.
Relationships
- Operator
- GitHub 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.