What is EasyCron?

EasyCron is a bot in the webhook senders category, operated by EasyCron.

Bot name
EasyCron
Operator
EasyCron
Type
Bot
Respects robots.txt
Not confirmed
robots.txt user agent
EasyCron
Signs requests (Web Bot Auth)
No

About EasyCron

EasyCron is an online cron job service. Users can schedule an HTTP request to be made at a specific date and time.

Webhook senders call your endpoints to deliver events from payment, messaging and SaaS platforms. Blocking them breaks integrations. Allow them on the webhook paths they need and nowhere else.

EasyCron user agent

EasyCron identifies itself with this user agent string:

  • EasyCron/1.0 (https://www.easycron.com/)

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.

How to block EasyCron in robots.txt

We have not confirmed whether EasyCron 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.

Block EasyCron from the whole site

User-agent: EasyCron
Disallow: /

Block EasyCron from some folders

User-agent: EasyCron
Disallow: /private/
Disallow: /search

Allow EasyCron only on some folders

User-agent: EasyCron
Allow: /blog/
Disallow: /

Allow EasyCron and block other crawlers

User-agent: EasyCron
Allow: /

User-agent: *
Disallow: /

Things to know

  • Each host needs its own file. Rules on www.example.com do not apply to shop.example.com.
  • A crawler obeys only the most specific group that names it. Once you add a User-agent: EasyCron group, EasyCron ignores your User-agent: * rules, so repeat any that should still apply.
  • The user agent name is not case sensitive. We take EasyCron from EasyCron's user agent; check EasyCron's own documentation if it publishes a different robots.txt name.
  • Crawlers cache robots.txt, so changes can take up to a day to apply. Disallow stops crawling but does not remove pages already collected or indexed.

Limits of robots.txt

  1. EasyCron may not follow the rule. robots.txt is a request that nothing enforces, and we have not confirmed that EasyCron follows it. Check your logs after adding a rule.
  2. The user agent could be fake. robots.txt matches the name a request claims. Anyone can send EasyCron's user agent, and a scraper using it is not bound by EasyCron's robots.txt policy. Only checking the source network tells a real EasyCron from a fake one.

Treat robots.txt as a statement of your policy, and enforce it where requests arrive.

Who should care about EasyCron

Publishers

Allow EasyCron if it is a service you use, and keep its visits out of page views and ad requests either way.

Transfon Security for publishers

Media buyers and advertisers

EasyCron is not a person. Exclude it from campaign and conversion data so reports reflect real visitors.

Transfon Security for advertisers

E-commerce

Allow EasyCron only if it works for your store, and keep it away from cart and checkout.

Transfon Security for e-commerce

SaaS and APIs

If EasyCron is a service you use, allow it on the endpoints it needs and block it elsewhere.

Transfon Security for SaaS and APIs

Block EasyCron with Transfon Security

robots.txt is a request, not an enforcement. Transfon Security shows EasyCron 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

Control EasyCron on your site

  • See every EasyCron visit and the pages it reads
  • Spot bots that fake trusted crawler names
  • Block, allow or rate limit EasyCron with one rule
  • Works with or without robots.txt support

Frequently asked questions

What is EasyCron?

EasyCron is a bot in the webhook senders category, operated by EasyCron. EasyCron is an online cron job service. Users can schedule an HTTP request to be made at a specific date and time.

Does EasyCron respect robots.txt?

We have not confirmed whether EasyCron 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.

How do I block EasyCron?

Add "User-agent: EasyCron" followed by "Disallow: /" to the robots.txt file at the root of your site. To enforce it, block requests whose user agent contains "EasyCron/" at your WAF. In Transfon Security that is one User Agent block rule.

Is robots.txt enough to block EasyCron?

No. robots.txt is voluntary, so EasyCron may not follow it, and anyone can send EasyCron's user agent, so a fake EasyCron ignores your rule. Enforce the rule where requests arrive, at your WAF, and check the source network.

Should I block EasyCron?

Webhook senders call your endpoints to deliver events from payment, messaging and SaaS platforms. Blocking them breaks integrations. Allow them on the webhook paths they need and nowhere else.

Related bots

All webhook senders · Full bot directory

See Which Bots Visit Your Site

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.

Stay ahead of the publishing curve

Privacy, security, monetization, and performance insights. A few emails a month, no spam.

By subscribing you agree to our privacy policy.