Bot intelligence record
Splunk
Usually allowSplunk is a monitoring bot used for uptime monitoring, synthetic checks, performance measurement, accessibility review; it appears in server logs as `Rigor`.
- Operator
- Splunk
- Family
- Splunk
- Type
- Monitoring
- Source type
- Documented
- Last checked
- 2026-06-23
User-Agent Pattern
SplunkRigor
User-agent strings are identification signals, not proof of identity. Confirm important allow, block, or rate-limit decisions with logs, DNS or IP evidence, request behavior, or operator documentation when available.
Robots.txt Snippet
Click snippet to copyUser-agent: Rigor
Disallow: /Click the snippet to copy it, or highlight the text manually.
Handling Guidance
NoThis bot is usually safe to allow when the request source is verified and the traffic matches your site policy.
Splunk is used for uptime monitoring, synthetic checks, performance measurement, accessibility review, and site-health testing.
Record Details
Structured data- Operator
- Splunk
- Family
- Splunk
- Type
- Monitoring
- Purpose
- Monitoring
- Identity type
- Verified Bot
- Confidence
- Medium
- Last verified
- 2026-04-01
- Last checked
- 2026-06-23
- Source type
- Documented
- Verification
- Verify Splunk by matching `Rigor` to documented crawler-pattern evidence, then checking reverse DNS, IP ownership, request behavior, and crawl consistency.
- Spoofing risk
- Splunk has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.
Notes
- Splunk is a monitoring bot used for uptime monitoring, synthetic checks, performance measurement, accessibility review, and site-health testing.
- Its primary user-agent pattern is
Rigor; a representative HTTP user-agent isMozilla/5.0 (X11; Linux x86_64; Rigor) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.75 Safari/537.36. - Splunk is verified with Medium confidence. The identity type is Verified Bot, and the evidence basis is documented crawler-pattern evidence.
- Splunk does not have confirmed robots.txt behavior in the available public evidence.
- Splunk can usually be allowed after confirming the source and monitoring request volume.
Evidence and Source
- Verify Splunk by matching `Rigor` to documented crawler-pattern evidence, then checking reverse DNS, IP ownership, request behavior, and crawl consistency.
- Splunk traffic is primarily detected by the `Rigor` user-agent pattern; a representative HTTP user-agent is `Mozilla/5.0 (X11; Linux x86_64; Rigor) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.75 Safari/537.36`. Compare source IPs, reverse DNS, request paths, and crawl cadence before trusting the traffic.
- Splunk is used for uptime monitoring, synthetic checks, performance measurement, accessibility review, and site-health testing.
- Splunk has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.
Monitor This Bot In Edge
Botcrawl EdgeUse Botcrawl Edge to see matching traffic, identify related datacenter activity, and create allow, block, rate-limit, or log rules across connected sites.