360Monitoring is a bot in the monitoring and analytics bots category, operated by 360Monitoring.
Empowering Developers to Monitor Sites & Servers, Easily
Monitoring bots check uptime, performance and page changes on behalf of a site owner or a third party. Allow the services you run yourself and exclude them from analytics so they do not inflate page views.
360Monitoring identifies itself with this user agent string:
monitoring360Anyone can copy a user agent string. Transfon Security also checks where each request comes from, so a request that claims to be a known crawler but comes from the wrong network is treated as a fake, not as the real crawler.
We have not confirmed whether 360Monitoring follows robots.txt. Add a rule, then check your logs to see that it stopped. robots.txt is a plain text file at the root of your domain, such as https://example.com/robots.txt.
User-agent: monitoring360 Disallow: /
User-agent: monitoring360 Disallow: /private/ Disallow: /search
User-agent: monitoring360 Allow: /blog/ Disallow: /
User-agent: monitoring360 Allow: / User-agent: * Disallow: /
User-agent: monitoring360 group, 360Monitoring ignores your User-agent: * rules, so repeat any that should still apply.monitoring360 from 360Monitoring's user agent; check 360Monitoring's own documentation if it publishes a different robots.txt name.Treat robots.txt as a statement of your policy, and enforce it where requests arrive.
Allow 360Monitoring if it is a service you use, and keep its visits out of page views and ad requests either way.
Transfon Security for publishers360Monitoring is not a person. Exclude it from campaign and conversion data so reports reflect real visitors.
Transfon Security for advertisersAllow 360Monitoring only if it works for your store, and keep it away from cart and checkout.
Transfon Security for e-commerceIf 360Monitoring is a service you use, allow it on the endpoints it needs and block it elsewhere.
Transfon Security for SaaS and APIsrobots.txt is a request, not an enforcement. Transfon Security shows 360Monitoring by name in the Top Bots report, so you can see how often it visits and which pages it reads. Block or allow it with a User Agent rule, or slow it down with a rate limit decision rule.
Transfon Security
360Monitoring is a bot in the monitoring and analytics bots category, operated by 360Monitoring. Empowering Developers to Monitor Sites & Servers, Easily
We have not confirmed whether 360Monitoring follows robots.txt. Add a robots.txt rule, then check your logs to see that it stopped, and block it by user agent if it did not.
Add "User-agent: monitoring360" followed by "Disallow: /" to the robots.txt file at the root of your site. To enforce it, block requests whose user agent contains "monitoring360" at your WAF. In Transfon Security that is one User Agent block rule.
No. robots.txt is voluntary, so 360Monitoring may not follow it, and anyone can send 360Monitoring's user agent, so a fake 360Monitoring ignores your rule. Enforce the rule where requests arrive, at your WAF, and check the source network.
Monitoring bots check uptime, performance and page changes on behalf of a site owner or a third party. Allow the services you run yourself and exclude them from analytics so they do not inflate page views.
Transfon Security identifies every bot in this directory in your traffic reports, flags fake search crawlers, and lets you allow, block or rate limit each bot.
Privacy, security, monetization, and performance insights. A few emails a month, no spam.