Bot intelligence record
360Monitoring
Usually allowUse the monitoring360 identifier to separate 360Monitoring uptime, accessibility, or site-health monitoring traffic from normal visitor requests in server logs.
- Operator
- 360Monitoring
- Family
- 360Monitoring
- Type
- Monitoring
- Source type
- Observed
- Last checked
- 2026-05-20
User-Agent Pattern
360Monitoringmonitoring360
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: monitoring360 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.
Uptime checks, managed website monitoring, synthetic tests, accessibility scans, or site-health reviews.
Record Details
Structured data- Operator
- 360Monitoring
- Family
- 360Monitoring
- Type
- Monitoring
- Purpose
- Monitoring
- Identity type
- Observed
- Confidence
- Low
- Last verified
- 2026-04-01
- Last checked
- 2026-05-20
- Source type
- Observed
- Verification
- Validate the identifying user-agent or signature against the operator documentation before creating hard allow rules.
- Spoofing risk
- User-agent strings can be spoofed. For allow-listing or low-friction rules, pair the published identifier with operator documentation or cryptographic verification when available.
Notes
360Monitoring is listed in the Botcrawl directory as a monitoring bot from 360Monitoring. The primary identifier for log review is monitoring360.
Identification
- User-agent pattern:
monitoring360 - Family: 360Monitoring
- Type: Monitoring
- Kind: Monitor
Common use
Uptime checks, managed website monitoring, synthetic tests, accessibility scans, or site-health reviews.
Verification and handling
Confirm the user-agent against server logs and use published operator documentation, IP ranges, reverse DNS, or other trust signals when available.
Directory guidance marks the risk level as Safe and the blocking decision as No. Do not rely on the user-agent string alone because user-agent strings can be copied or spoofed.
Robots.txt handling: No.
Evidence and Source
- Validate the identifying user-agent or signature against the operator documentation before creating hard allow rules.
- Match `monitoring360` as a case-insensitive substring in HTTP user-agent logs. Use bot_http_agent for full user-agent examples when the client sends a longer browser-like string. Do not treat a user-agent match alone as proof of identity for allow-listing.
- Uptime checks, managed website monitoring, synthetic tests, accessibility scans, or site-health reviews.
- User-agent strings can be spoofed. For allow-listing or low-friction rules, pair the published identifier with operator documentation or cryptographic verification when available.
Monitor This Bot In Edge
Botcrawl EdgeUse Botcrawl Edge to see matching traffic, create allow or block rules, and control this bot across connected sites.