The notiduck bot

notiduck is an uptime and website health monitor. Someone added your site to their notiduck account, usually its owner or the agency that runs it. We do not crawl the web and we do not discover sites on our own: we only check URLs a person asked us to watch.

Every request we send carries this User-Agent:

Mozilla/5.0 (compatible; notiduck/1.0; +https://notiduck.com/bot)

From every checking location:

• The monitored URL itself, following up to 10 redirects, to measure response time and status.

From one location only:

• The www or non-www variant of the same host, to check that one redirects to the other.
• Your TLS certificate, read during the connection, to warn before it expires.
• The page HTML, /robots.txt, your sitemap (or /sitemap.xml) and the response headers, for SEO and security-header checks.
• A Lighthouse audit about every 4 hours, which loads the page in headless Chrome from Gravelines. Those requests carry Lighthouse's standard User-Agent, which contains Chrome-Lighthouse.

Domain expiry is looked up at your domain's registry (RDAP or whois), not on your server, at most once an hour per domain. We never submit forms, log in, or follow links beyond the ones above.

Every 5 minutes. In each 5-minute cycle every location sends one request to the URL, and one location also runs the checks listed above. Lighthouse audits run about every 4 hours.

Uptime checks do not follow robots.txt rules, like other uptime monitors: the URL was added by someone who wants it watched. If you are not that person and want it to stop, see below.

Requests can also arrive over IPv6 from the same machines.

A blocked request (for example a 403 from a bot-protection service) looks like an outage to us, so the person monitoring your site will get a "down" alert. To prevent that, allow the User-Agent above or the IP addresses in the table.

Write to agne@gijahub.com with the URL or domain, and we will stop checking it. More about how we handle data is on our security page.