Verify Domain

Note: Unverified domains are automatically deleted after 48 hours. Verified domains that lose verification are kept for 45 days before deletion.

When you set up a domain for your account, you need to verify it before you can use it. All you need to do is adding a given token to your DNS entries.

Copy token

When clicking on the details of your domain, you see a block labeled "Domain Verification".

The subdomain is always _p25-verify, so your full domain would be _p25-verify.example.com. The token is always prefixed with p25-verification= and the full entry is p25-verification={token}.

You need to create a TXT record for the new subdomain, containing the prefix and the token, as presented on the p25.dev domain details page.

Checks

Our backend periodically checks the verification status of your domain. In the domain details page, under "Domain Verification", you find a timestamp with the last checked time.

If your domain was not validated yet, you can trigger a manual verification. You should only do this after you added the record to DNS.

Verification fails

There are a number of reasons why you might assume a verification failure, even though there's none.

DNS is a laggy system. Changes are usually not broadcasted immediately. Sometimes it takes up to 1 day until your new record is visible globally.

DNS has the concept of a TTL. DNS entries are cached for the given time in seconds. Sometimes all you can do is wait for the cache to expire. That's why we recommend setting a short TTL of 300 seconds for you DNS records first, and increase this duration if you know you are running stable.

If you waited enough time, and you are sure all caches are expired, there are two failure cases left:

  1. A simple copy-paste mistake. Make sure that no end of the values got truncated.
  2. Double-TLD-issue: Some registrars have confusing UIs. It happens that instead of the subdomain _p25-verify.example.com you accidentally created the subdomain _p25-verify.example.com.example.com.

If you happen to have dig installed, you can verify that your TXT record was properly added with dig TXT _p25-verify.example.com. You should see a response containing your token "p25-verification={token}". Note that what you see with dig can differ from what p25.dev sees, due to the discussed caching issues.

All fails? Email support, and we will investigate the issue together with you.