Qcbot is a bot in the monitoring and analytics bots category, operated by QUIC Cloud Inc..
qcbot is the web crawler for QUIC.cloud Onlin
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.
Sample user agent strings sent by Qcbot:
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; qcbot/1.0; +http://quic.cloud/bot.html) Chrome/112.0.0.0 Safari/537.36Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Mobile Safari/537.36 (compatible; qcbot/1.0; +http://quic.cloud/bot.html)Anyone 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.
Qcbot follows robots.txt, so these rules stop it crawling the paths you choose. robots.txt is a plain text file at the root of your domain, such as https://example.com/robots.txt.
User-agent: qcbot Disallow: /
User-agent: qcbot Disallow: /private/ Disallow: /search
User-agent: qcbot Allow: /blog/ Disallow: /
User-agent: qcbot Allow: / User-agent: * Disallow: /
User-agent: qcbot group, Qcbot ignores your User-agent: * rules, so repeat any that should still apply.qcbot from Qcbot's user agent; check QUIC Cloud Inc.'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 Qcbot if it is a service you use, and keep its visits out of page views and ad requests either way.
Transfon Security for publishersQcbot is not a person. Exclude it from campaign and conversion data so reports reflect real visitors.
Transfon Security for advertisersAllow Qcbot only if it works for your store, and keep it away from cart and checkout.
Transfon Security for e-commerceIf Qcbot 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 Qcbot 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
Qcbot is a bot in the monitoring and analytics bots category, operated by QUIC Cloud Inc.. qcbot is the web crawler for QUIC.cloud Onlin
Yes. Qcbot follows robots.txt, so a Disallow rule for the qcbot user agent stops it from crawling the paths you list.
Add "User-agent: qcbot" followed by "Disallow: /" to the robots.txt file at the root of your site. To enforce it, block requests whose user agent contains "qcbot" at your WAF. In Transfon Security that is one User Agent block rule.
No. robots.txt is voluntary, so Qcbot may not follow it, and anyone can send Qcbot's user agent, so a fake Qcbot 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.