Overview
ProfoundBot is a user triggered fetcher associated with Profound and used for user triggered page retrieval.
The primary identifying User-Agent token is ProfoundBot. Representative HTTP request identity: ProfoundBot/1.0 (+https://docs.tryprofound.com/bots).
Directory status: Active. Identity classification: Verified with High confidence. Identity type: official documented.
This identity is recorded as not honoring robots.txt Disallow directives; use server-side access controls when restriction is required.
Risk classification: Neutral. Evaluate request context and site policy before allowing, rate-limiting, or blocking.
Identity
- User-Agent Pattern
-
ProfoundBot - HTTP Agent Examples
-
ProfoundBot/1.0 (+https://docs.tryprofound.com/bots) - Identity Type
- Officially documented
- Evidence Method
- Match the exact ProfoundBot User-Agent. For domains enrolled in Profound static-IP fetching, corroborate against `54.71.251.60`, `54.185.59.110`, or `100.22.234.65`; default AWS egress is dynamic.
Classification
- Type
- AI
- Kind
- User-triggered fetcher
- Family
- Profound
- Purpose
- User-triggered page retrieval
Behavior and handling
- Common Use
- fetching one public webpage supplied by a Profound user or API request
- Detection Notes
- ProfoundBot is user-initiated and fetches one supplied public page rather than recursively crawling. robots.txt Disallow support is explicitly planned but not currently enforced.
- Respects robots.txt
- No
- Spoofing Risk
- The ProfoundBot User-Agent can be copied. Dedicated egress IPs provide stronger corroboration only for domains enrolled in Profound static-IP fetching.
- Risk
- Neutral
- Recommended Handling
- Depends
Rules and controls
- Robots.txt Snippet
-
# ProfoundBot does not currently honor robots.txt Disallow. Use WAF/CDN or server-side User-Agent/IP controls to restrict it.