Stopping requests

Two ways exist, and neither needs an account. One stops a single job. The other keeps the service away from an entire zone.

The stop link

Every request carries a stop URL in its User-Agent and in the X-CronJob-Stop header. Opening it shows what the job targets, how often it runs and how many requests it made in the last day. One button pauses it, and the owner cannot point the same job at the host again.

The link covers one job, because one request is what produced it.

The opt-out record

Blocking every cronjob.dev request to a host is a larger claim, so it takes a stronger proof: a DNS record. Publishing one demonstrates control of the zone.

optout.example.com.  IN TXT  "cronjob.dev"

A record on the registrable domain covers every host under it. For a single subdomain, publish it at optout.api.example.com instead.

The record applies as soon as it resolves. Jobs already pointed at the host pause, and their owners are told why and that the record is not theirs to lift. Removing the record lets those jobs resume by themselves within an hour.

The same shape works at scan.mx and ssltest.com, so one record per service covers all three.

Anything else

Anything else reaches a person from the contact page. Quoting the User-Agent line from the log identifies the job immediately.