Skip to main content
ownsi proves that you control a domain’s DNS. You add one TXT record, we read DNS from three public resolvers, and you get one of three answers — proved, not yet, or here is exactly what is wrong with the record you created. That third answer is the product. Most verification flows tell you “not verified” and leave you to guess. ownsi names the reason: the panel appended your domain to the host, the value came back with quotes around it, the resolvers are still holding a cached “does not exist” for four more minutes.

Quickstart

The whole thing, start to finish. About three minutes of work and some waiting.

Diagnosing a Failure

You added the record and nothing happened. Start here.

Proof Scope

What the attestation claims, what it does not, and why it never expires.

DNS Verification

Which resolvers decide, and why a negative always comes with a reason.

​
What you get

A dated attestation: “on 15 June, this account demonstrated control of acme.com’s DNS zone.”

It is about a moment

A fact about the day it was granted, not a claim about today. That is what makes it something you can show someone.

It never decays

Once granted it is never revoked and never re-checked. Delete the TXT record afterwards if you like — the proof does not depend on it.

Nothing is locked behind it

No feature switches on. The attestation is the product, and you decide who sees it.

​
The three answers

Every check ends in exactly one of these, and the third is not a worse version of the second. The gap between the second and the third is the whole point. Telling someone to fix a record that is already correct is the failure this product exists to avoid.
ownsi has an API, and it is not open yet. The routes that belong to an account answer only the app’s own session, and there are no public keys. It is documented in full anyway, because the shape it will have when it opens is the shape it has now.