Why Domain Intelligence APIs Need an “Unknown” State

https://hackernoon.imgix.net/images/BgSOT4HXGUMJRyVMdyvXM1Nf5UR2-2i83fyt.png
Disclosure: I’m Esteve Castells, the maker of DomScan.

Domain intelligence often enters an application as a simple question. Is this domain available? Does this DNS record exist? Is an email security control configured? Did a public identity signal appear on the website?

The easiest response model is a boolean. It is also frequently the wrong one.

Checks against public internet evidence can time out, return incomplete data, hit access restrictions, or encounter an unsupported input. If an application converts every inconclusive result into false, it creates confident answers that the evidence never supported.

The boolean trap

Imagine a domain availability check that returns no conclusive result. Mapping that response to available: false makes the domain look registered. Mapping it to available: true is worse because a user may act on it. The honest answer is that availability could not be determined from the evidence available at that time.

The same...

Copyright of this story solely belongs to hackernoon.com. To see the full text click HERE

Read more