🤖 Overview

DnyzBot is a web crawler operated by Dnyz, a company specializing in website monitoring, uptime tracking, and performance analytics. First documented in public web server logs around 2020, this bot is designed to periodically scan target websites to verify availability, measure response times, and detect content changes. The data collected feeds into Dnyz’s monitoring dashboard, alerting subscribers when a site becomes unreachable or deviates from expected behavior. Unlike search engine crawlers that index content for discovery, DnyzBot focuses solely on operational health metrics and does not store page text for public search.

🌐 Technical Behavior

DnyzBot performs headless HTTP requests to a list of user‑specified URLs, typically at intervals configurable by the subscriber (e.g., every 5, 15, or 60 minutes). Each request retrieves the full HTTP response head and body, measuring TTFB (Time to First Byte), status codes, and total load time. The crawler supports both HTTP/1.1 and HTTP/2 protocols and sends standard headers including Accept, Accept-Encoding, and User-Agent. IP addresses used by DnyzBot are drawn from a pool of datacenter ranges, primarily in North America and Europe; specific netblocks are not publicly published but can be obtained from the company upon request. The bot does not follow HTML hyperlinks—it only fetches the exact URLs provided by the account holder. Retry logic is implemented: if a request fails due to a 5xx status or timeout, the bot will retry up to three times before reporting an outage.

📋 robots.txt Compliance

According to Dnyz’s official documentation, DnyzBot fully respects the robots.txt file and will refrain from crawling any URL path explicitly disallowed. The bot also honors Crawl-Delay directives when present, pausing between requests as specified. This compliance is verified by routine testing across monitored sites; no known instances of ignoring disallow rules have been reported in security advisories or community forums.

🔍 Detection Indicators

The primary detection method is the User-Agent string: Mozilla/5.0 (compatible; DnyzBot/1.0; +https://dnyz.com/bot). Some versions may omit the Mozilla prefix and appear as simply DnyzBot/1.0. A secondary identifier is the Via header set to 1.1 dnyz-monitor, though this is not guaranteed. Behavioral fingerprints include periodic, single‑page requests from a fixed set of IPs with consistent intervals and no deep crawling of linked resources.

📊 Data Usage

Collected data is used exclusively for website monitoring and performance analytics as part of the Dnyz subscription service. Metrics such as uptime percentage, response time trends, and SSL certificate expiration dates are displayed on client dashboards and can trigger email or SMS alerts. Dnyz does not resell or share raw response data, nor does it use the content for AI training or language model improvement.

⚙️ Rate Limiting Policy

DnyzBot is rate‑limited because its recurring, automated probes can generate a steady stream of requests that, if unchecked, could overwhelm under‑provisioned origin servers. Administrators are advised to apply threshold‑based blocking (e.g., deny if more than 100 requests per minute from a single DnyzBot IP) to protect against unintentional load, while still allowing legitimate monitoring checks to pass.

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the bots listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.