Overview
NewRelicPinger is a monitoring bot from New Relic used for uptime monitoring, synthetic checks, performance measurement, accessibility review, and site-health testing.
Its primary user-agent pattern is NewRelicPinger.
NewRelicPinger 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.
NewRelicPinger can usually be allowed after confirming the source and monitoring request volume.
Identity
- User-Agent Pattern
-
NewRelicPinger - HTTP Agent Examples
-
NewRelicPinger - Robots Token
- NewRelicPinger
- Identity Type
- Observed
- Evidence Method
- Treat `NewRelicPinger` 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
- Monitoring bot
- Kind
- Monitoring bot
- Family
- New Relic
- Purpose
- Uptime and performance monitoring
Behavior and handling
- Common Use
- NewRelicPinger is used for uptime monitoring, synthetic checks, performance measurement, accessibility review, and site-health testing.
- Detection Notes
- NewRelicPinger traffic is primarily detected by the `NewRelicPinger` user-agent pattern. Compare source IPs, reverse DNS, request paths, and crawl cadence with New Relic infrastructure before trusting the traffic.
- Respects robots.txt
- Unknown
- Spoofing Risk
- NewRelicPinger has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.
- Risk
- Neutral
- Recommended Handling
- Allow
Rules and controls
- Robots.txt Snippet
-
# robots.txt behavior is unconfirmed. Do not rely on this rule without verification.
Relationships
- Operator
- New Relic 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.