Overview
360Monitoring is a website-monitoring agent used for availability and performance checks.
Its documented HTTP user-agent is Mozilla/5.0 (compatible; monitoring360bot/1.1; +https://app.360monitoring.com/bot.html). The stable identifying token is monitoring360bot; monitoring360 may also appear in filtering rules.
360Monitoring is verified with High confidence from current operator documentation. Because a user-agent string can be copied, source addresses should be corroborated against the operator’s current monitoring-node allowlist when authentication matters.
Robots.txt behavior is not documented as the enforcement mechanism for these monitoring checks.
Identity
- User-Agent Pattern
-
monitoring360bot - Aliases
- monitoring360; monitoring360bot/1.1
- HTTP Agent Examples
-
Mozilla/5.0 (compatible; monitoring360bot/1.1; +https://app.360monitoring.com/bot.html) - Robots Token
- monitoring360
- Identity Type
- Officially documented
- Evidence Method
- Match the `monitoring360bot` token and corroborate the source address against the operator’s current monitoring-node allowlist when stronger verification is required.
Classification
- Type
- Monitoring
- Kind
- Monitor
- Family
- 360Monitoring
- Purpose
- Monitoring
Behavior and handling
- Common Use
- Website availability, uptime, and performance monitoring.
- Detection Notes
- Detect by `monitoring360bot` in the HTTP User-Agent. Do not use the former placeholder-like `user_agent monitoring360` value as an exact signature.
- Respects robots.txt
- Unknown
- Spoofing Risk
- The user-agent can be copied; source-address corroboration provides stronger evidence than the token alone.
- Risk
- Safe
- Recommended Handling
- Do not block
Rules and controls
- Robots.txt Snippet
-
# Monitoring traffic is not documented as robots.txt-controlled. Use application or network policy if blocking is required.
Relationships
- Operator
- 360Monitoring Checked 2026-09-02
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.
Changes
-
Directory evidence unverified verifiedRecorded 2026-09-03 00:45:39 UTC
-
Identity type observed official-documentedRecorded 2026-09-03 00:45:39 UTC
-
Evidence method Verify 360Monitoring by matching `monitoring360` to observed traffic patterns and user-agent evidence, then checking reverse DNS, IP ownership, request behavior, and crawl consistency. Match the `monitoring360bot` token and corroborate the source address against the operator’s current monitoring-node allowlist when stronger verification is required.Recorded 2026-09-03 00:45:39 UTC
This timeline records selected public-field transitions after Botcrawl established the 4.28 history baseline. It is not a complete reconstruction of changes made before that baseline.