Overview
Sentry is a monitoring bot used for uptime monitoring, synthetic checks, performance measurement, accessibility review, and site-health testing.
Its primary user-agent pattern is https://sentry.io; a representative HTTP user-agent is sentry/10.0.0.dev0 (https://sentry.io).
Sentry is verified with Medium confidence. The identity type is Verified Bot, and the evidence basis is a public crawler reference or source-linked documentation.
Sentry is marked as not reliably governed by robots.txt directives; use server-side rules if the traffic should be restricted.
Sentry can usually be allowed after confirming the source and monitoring request volume.
Identity
- User-Agent Pattern
-
https://sentry.io - HTTP Agent Examples
-
sentry/10.0.0.dev0 (https://sentry.io) - Robots Token
- https://sentry.io
- Identity Type
- Verified bot
- Evidence Method
- Verify Sentry by matching `https://sentry.io` to a public crawler reference or source-linked documentation, then checking reverse DNS, IP ownership, request behavior, and crawl consistency.
Classification
- Type
- Monitoring
- Kind
- Monitor
- Family
- Sentry
- Purpose
- Monitoring
Behavior and handling
- Common Use
- Sentry is used for uptime monitoring, synthetic checks, performance measurement, accessibility review, and site-health testing.
- Detection Notes
- Sentry traffic is primarily detected by the `https://sentry.io` user-agent pattern; a representative HTTP user-agent is `sentry/10.0.0.dev0 (https://sentry.io)`. Compare source IPs, reverse DNS, request paths, and crawl cadence before trusting the traffic.
- Respects robots.txt
- No
- Spoofing Risk
- Sentry 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
- Do not block
Rules and controls
- Robots.txt Snippet
-
# This agent may ignore robots.txt. Use authenticated access controls or network policy when blocking is required.
Relationships
- Operator
- Sentry Checked 2026-06-23
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.