Independent intelligence for the automated web.

monitoring

Splunk

Splunk is a monitoring bot used for uptime monitoring, synthetic checks, performance measurement, accessibility review.

Verifiedactivemonitor
01

Quick answer

What is Splunk?

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 is Mozilla/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.

02

Identity

How to identify this Bot

User-Agent
Rigor
robots.txt token
Rigor
HTTP agent
Mozilla/5.0 (X11Linux x86_64Rigor) AppleWebKit/537.36 (KHTMLlike Gecko) Chrome/86.0.4240.75 Safari/537.36
Operator
Splunk
Family
Splunk
Technical kind
monitor
Identity method
verified-bot
03

Behavior

Purpose, behavior, and practical context

Purpose
monitoring
Common use
Splunk is used for uptime monitoring, synthetic checks, performance measurement, accessibility review, and site-health testing.
Respects robots.txt
unknown
Spoofing risk
Splunk has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.
Detection notes
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.
04

Verification and controls

Verification and blocking guidance

Verification method
Verify Splunk by matching `Rigor` to documented crawler-pattern evidence, then checking reverse DNS, IP ownership, request behavior, and crawl consistency.
General blocking snippet
User-agent: RigorDisallow: /
05

Related records

Related Bots