Domain Verification

Prove that the site is yours using HTTP well-known or DNS TXT.

Reading time
5 min reading
Updating
Mar 2026

Why Verification?

Verification is mandatory to prevent tracking someone else's site and collecting data. You can create a site registration, but regular scheduler cycles will not start until verified_at is full.

DNS TXT Method

  1. Open your DNS management panel

    Go to the DNS registration screen of your domain provider.

  2. Insert TXT record

    Use _dk-uptime.subdomain as host. Enter the token displayed in the verification screen in the Anchor panel as the value.

  3. Start control on the panel

    Trigger DNS verification on the Verification screen. If the system finds a match, the site is verified.
DNS TXT
Genre: TXT Name: _dk-uptime Value: abc123xyz789token # Alternative legacy format is also accepted: Value: kernel-uptime=abc123xyz789token

DNS propagation can take time.

With many providers the registration appears within a few minutes; with some networks it may take longer. If the panel does not find a match on the first check, you can try again later.

HTTP Well-Known Method

HTTP verification relies on serving a plain text file containing a token from the path /.well-known/dk-uptime-verify.

HTTP FILE
# File path /.well-known/dk-uptime-verify # File content abc123xyz789token

If you are using WordPress, the plugin will serve this file automatically when the Ownership Connect flow is complete. There is no need to manually enter the verification token; the token linked to your Anchor account is automatically managed by the plugin.

Verification may drop if the file is removed.

If the file is no longer accessible during the weekly revalidation, the system will clear the verified_at field and prompt you to revalidate the site.

Periodic Revalidation

The uptime:re-verify command in Scheduler runs once a week, Monday at 02:00. This retests all verified sites; if the match is lost, verified_at is null.

This command also synchronizes the verification token on the site with the user's account token. If the account token has changed, the new token should be served instead of the old content.

Next Steps