Is Cronjob.de a crawler?

No. We do not follow links or read pages for indexing. We call exactly the address a customer entered with us, at the times they set – usually a script such as wp-cron.php or an export file.

Why does Cronjob.de call my site?

Because someone – usually you, your agency or your developer – created a cron job for this address with us. Your web space probably has no cron of its own, and we take over triggering the scheduled tasks.

How can I tell which cron job it is?

Every call sends http://cronjob.de/?id= followed by a number as the referer. That number is the cron job on our side. Tell us the number if you have questions or want the calls to stop.

Cronjob.de in your server logs

Calls with the identifier below come from Cronjob.de. We call addresses on behalf of our customers on their schedule – for example so that a website's scheduled tasks also run at night. This page explains how to recognise us, how to allow us and how to have calls stopped.

Recognise
Allow
IP addresses
Stop
Questions

How to recognise our calls

Identifier (user agent)

Cronjob.de (+https://www.cronjob.de/bot)

The identifier always starts with Cronjob.de and stays the same even when we swap servers. Check the beginning, not the whole line.

Referer

http://cronjob.de/?id=1234567

The number is the cron job on our side. It helps if you contact us about a particular call.

Allowing our calls – best via the user agent

If a firewall, a security plugin or a protection service blocks our calls (usually error 403), the scheduled task does not run. Then allow us by the identifier: it is part of every call – scheduled calls just like the Run now button – and unlike IP addresses it does not change when we swap servers. That is the most reliable way to let us through.

Cloudflare

Under Security → WAF, create a custom rule with the action “Skip” that checks only the identifier:

(starts_with(http.user_agent, "Cronjob.de"))

If “Bot Fight Mode” is switched on, no rule can bypass it – the only fix is to switch it off.

Apache (.htaccess)

SetEnvIfNoCase User-Agent "^Cronjob\.de" cronjob_de
<RequireAny>
    Require env cronjob_de
    Require ip 192.0.2.10
</RequireAny>

Hosts and security plugins (Wordfence and others)

Ask your host for an exception for the user agent Cronjob.de, or add it as an allowed bot in the plugin. Alternatively, exclude the cron job's file (such as wp-cron.php) from scanning.

Only if there is no other way: our IP addresses

Our calls currently come from these addresses. Important: servers may be added or replaced without notice – so we advise against IP-only allowlisting. If only an IP-based rule is possible, please re-check this list from time to time. The current version is always available as a text file: ips.txt or machine-readable as ips.json

IPv4

94.130.182.11
94.130.186.237
159.69.100.137
88.99.37.158
95.216.197.33
116.203.93.182
195.201.42.154
65.21.158.228
167.233.179.75

IPv6

2a01:4f8:1c0c:4205::1
2a01:4f8:1c0c:46ef::1
2a01:4f9:c010:34ef::1
2a01:4f8:1c17:52dd::1
2a01:4f8:c2c:81f7::1
2a01:4f8:1c1b:971d::1
2a01:4f9:c012:bdb1::1

All servers are located in the European Union.

Having calls stopped

You do not want us to call your site? The quickest way is for whoever created the cron job to switch it off in their account. If you do not know who that is, write to us with the number from the referer and the address being called – we will look into it and stop the cron job. Until then you can block our calls on your server by the user agent Cronjob.de.

robots.txt

We follow rules in your robots.txt that name Cronjob.de explicitly. We read the file at most once a day; affected cron jobs are paused and the account holder is informed. So it takes effect with up to a day's delay – for an immediate stop, block the user agent or write to us.

User-agent: Cronjob.de
Disallow: /

Rules for all bots (User-agent: *) do not apply to us: we are not a crawler, we only call the one address someone entered for exactly this purpose – often the site owner, who wants to keep search engines out of an admin area but not their own cron job.

An address that keeps answering “not found” (404) is paused automatically after a week anyway.

Common questions

Is Cronjob.de a crawler?: No. We do not follow links or read pages for indexing. We call exactly the address a customer entered with us, at the times they set – usually a script such as wp-cron.php or an export file.
Why does Cronjob.de call my site?: Because someone – usually you, your agency or your developer – created a cron job for this address with us. Your web space probably has no cron of its own, and we take over triggering the scheduled tasks.
How can I tell which cron job it is?: Every call sends http://cronjob.de/?id= followed by a number as the referer. That number is the cron job on our side. Tell us the number if you have questions or want the calls to stop.

More about call errors: Cron job not running? Troubleshooting