WordpressNamecheap is a bot in the monitoring and analytics bots category, operated by Namecheap.
This is the major egress IP for our containerised WordPress platform so it is likely to be many flavours of WordPress and the potential to be any domain.
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.
WordpressNamecheap identifies itself with this user agent string:
WordPress/5.5.1; https://cresiap.org.mxAnyone 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 WordpressNamecheap 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: WordPress Disallow: /
User-agent: WordPress Disallow: /private/ Disallow: /search
User-agent: WordPress Allow: /blog/ Disallow: /
User-agent: WordPress Allow: / User-agent: * Disallow: /
User-agent: WordPress group, WordpressNamecheap ignores your User-agent: * rules, so repeat any that should still apply.WordPress from WordpressNamecheap's user agent; check Namecheap'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 WordpressNamecheap if it is a service you use, and keep its visits out of page views and ad requests either way.
Transfon Security for publishersWordpressNamecheap is not a person. Exclude it from campaign and conversion data so reports reflect real visitors.
Transfon Security for advertisersAllow WordpressNamecheap only if it works for your store, and keep it away from cart and checkout.
Transfon Security for e-commerceIf WordpressNamecheap 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 WordpressNamecheap 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
WordpressNamecheap is a bot in the monitoring and analytics bots category, operated by Namecheap. This is the major egress IP for our containerised WordPress platform so it is likely to be many flavours of WordPress and the potential to be any domain.
We have not confirmed whether WordpressNamecheap 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: WordPress" followed by "Disallow: /" to the robots.txt file at the root of your site. To enforce it, block requests whose user agent contains "WordPress/" at your WAF. In Transfon Security that is one User Agent block rule.
No. robots.txt is voluntary, so WordpressNamecheap may not follow it, and anyone can send WordpressNamecheap's user agent, so a fake WordpressNamecheap 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.