Why it happens first
Because it changes what the next screen can say. Instead of “add a TXT record somewhere”, it can say “in Cloudflare, go to DNS → Records, and this usually publishes in about a minute” — your panel’s own field names, and a number that came from your own zone. It is also the honest answer to the question anyone has before trusting a new tool with anything: do you actually know my DNS?What it finds
Who answers for the name
The nameservers your domain is delegated to. This is a fact about the domain, not about you —
the same answer everyone gets.
Which provider that is
Read from the nameserver names. Cloudflare, Route 53, GoDaddy, Namecheap, Google Domains,
Vercel — and other, which is a real answer, not a failure.
How long publishing takes
Two numbers, from two different places, and they answer different questions.
The two waits, and why both are shown
The second one is the wait people mistake for a broken record. You can see the record in your panel,
you can even see it with
dig against your own nameservers, and the rest of the world still says it
is not there — because it is repeating an answer it cached before you created it.
It tells you what it changed about your input
Type it however you have it:HTTPS://WWW.Acme.com/pricing, a trailing dot, capitals, an
internationalised name. ownsi normalises it to acme.com and says so, rather than quietly
reading a different name than the one you typed.
If you type something nobody can own — co.uk, github.io — it says that too, and suggests the
name in front of it.
When it cannot answer
Three different problems, and they are worth telling apart:
That last one is never dressed up as a problem with your domain. ownsi keeps the three
apart everywhere, not only here.