Overview
Radian6 is a marketing crawler from Salesforce / Radian6 used for advertising quality review, contextual classification, brand-safety checks, and marketing intelligence.
Its primary user-agent pattern is Radian6.
Radian6 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.
Radian6 should be monitored first, then rate-limited or blocked if the crawl rate, paths, or behavior are unwanted.
Identity
- User-Agent Pattern
-
Radian6 - HTTP Agent Examples
-
Radian6 - Robots Token
- Radian6
- Identity Type
- Observed
- Evidence Method
- Treat `Radian6` 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
- Marketing crawler
- Kind
- Marketing crawler
- Family
- Salesforce / Radian6
- Purpose
- Marketing intelligence
Behavior and handling
- Common Use
- Radian6 is used for advertising quality review, contextual classification, brand-safety checks, and marketing intelligence.
- Detection Notes
- Radian6 traffic is primarily detected by the `Radian6` user-agent pattern. Compare source IPs, reverse DNS, request paths, and crawl cadence with Salesforce / Radian6 infrastructure before trusting the traffic.
- Respects robots.txt
- Unknown
- Spoofing Risk
- Radian6 has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.
- Risk
- Caution
- Recommended Handling
- Monitor
Rules and controls
- Robots.txt Snippet
-
# robots.txt behavior is unconfirmed. Do not rely on this rule without verification.
Relationships
- Operator
- Salesforce / Radian6 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.