NekudaPaymentExecutor is an AI agent in the other bots category, operated by Nekuda.
Executes secure checkout via browser agent using user card and signed mandate.
Bots that do not fit the other categories. Review their purpose and allow only what you need.
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.
We have not confirmed whether NekudaPaymentExecutor 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: NekudaPaymentExecutor Disallow: /
User-agent: NekudaPaymentExecutor Disallow: /private/ Disallow: /search
User-agent: NekudaPaymentExecutor Allow: /blog/ Disallow: /
User-agent: NekudaPaymentExecutor Allow: / User-agent: * Disallow: /
User-agent: NekudaPaymentExecutor group, NekudaPaymentExecutor ignores your User-agent: * rules, so repeat any that should still apply.NekudaPaymentExecutor from NekudaPaymentExecutor's user agent; check Nekuda'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 NekudaPaymentExecutor if it is a service you use, and keep its visits out of page views and ad requests either way.
Transfon Security for publishersNekudaPaymentExecutor is not a person. Exclude it from campaign and conversion data so reports reflect real visitors.
Transfon Security for advertisersAllow NekudaPaymentExecutor only if it works for your store, and keep it away from cart and checkout.
Transfon Security for e-commerceIf NekudaPaymentExecutor 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 NekudaPaymentExecutor 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
NekudaPaymentExecutor is an AI agent in the other bots category, operated by Nekuda. Executes secure checkout via browser agent using user card and signed mandate.
We have not confirmed whether NekudaPaymentExecutor 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: NekudaPaymentExecutor" followed by "Disallow: /" to the robots.txt file at the root of your site. To enforce it, block requests whose user agent contains "NekudaPaymentExecutor" at your WAF. In Transfon Security that is one User Agent block rule.
No. robots.txt is voluntary, so NekudaPaymentExecutor may not follow it, and anyone can send NekudaPaymentExecutor's user agent, so a fake NekudaPaymentExecutor ignores your rule. Enforce the rule where requests arrive, at your WAF, and check the source network.
Bots that do not fit the other categories. Review their purpose and allow only what you need.
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.