PRIVACY

Privacy and logging

The toolbox processes the destination and test options you submit so the requested diagnostic can run. As with most web services, the hosting platform may record your IP address, browser details, requested URL, timestamp, response status and security events in access or error logs.

Rate limiting

The included application creates short-lived rate-limit counters derived from the connecting IP address. These counters are stored in the server temporary directory and are used to protect the public service from excessive requests.

Diagnostic targets

Do not submit confidential internal hostnames, private information or personal data. Public installations block internal address ranges, but the target itself may still appear in server logs or third-party API requests.

Third-party data services

BGP, RPKI, routing, ASN, geolocation and blocklist functions use RIPEstat. DNSSEC uses a validating public DNS service. Reverse WHOIS is optional and, when configured, sends the search value to the selected data provider. Those providers process requests under their own terms and privacy notices.

Historical monitoring

Only administrator-configured targets are stored in the monitoring database. Stored fields include target, status, duration, error and check time. Public visitors cannot add monitoring targets through the website.

Website analytics

When enabled by the site administrator, Google Analytics may collect usage information such as pages viewed, approximate location, device information and referral source. The live analytics measurement ID is stored in the protected local configuration file rather than in the public project configuration.