Privacy

No cookies. We use data to run Lancert and understand visits to this website.

Last updated: 26 October 2026

Data used by the service

We store your hostname, private IP address, API username, a hash of your API key, and registration dates and status. We also keep dates and counts of DNS challenge updates.

We count DNS queries and successful challenge updates for each registration. We also keep response times and the User-Agent strings sent by client software with successful updates.

We keep technical logs to help run and protect the service. For DNS challenge update requests, we log a hash of your IP address. We also use this hash to limit the number of requests from the same IP address.

Public information

Your hostname, target private IP address, and active DNS challenge values are public DNS records.

The status page shows usage counts by private IP address, network range, and client software.

Certificates from public certificate authorities usually appear in public Certificate Transparency logs. We use SSLMate Cert Spotter to read these records and count certificates.

Website statistics

We use Umami, hosted at analytics.lucor.dev, to measure visits to lancert.dev, including the documentation and status page. It collects pages visited, where visits come from, browser and operating system details, device type, screen size, language, and approximate location.

Umami processes your IP address and browser information to count visits and estimate location. It does not store IP addresses in its analytics records. It does not use cookies. See Umami’s documentation for more details.

How long we keep data

Registration data and service statistics are not deleted automatically. Disabling a registration does not delete its data. DNS challenge values stay in memory for up to 15 minutes and are cleared when the service restarts.

Other services

The API reference loads Scalar from jsDelivr (cdn.jsdelivr.net). Your browser sends your IP address and request details to jsDelivr when it loads this script.