01
Start with the layers
A domain is not a website. It is a durable label inside the Domain Name System. Registration assigns control of that label through a registrar; nameservers publish answers; records direct web, mail, and verification traffic; certificates support encrypted connections. A polished website can sit on fragile configuration, while an inactive name can still be carefully maintained.
The useful habit is to separate those layers. Ask who operates the registration, where the delegation points, which services are declared, and which signals are simply absent. Absence is evidence of non-observation, not proof of nonexistence.
02
Treat age and expiry carefully
Registration dates can suggest continuity, but they do not prove continuous ownership or active use. Expiration dates are operational deadlines, not sale indicators. A name may renew automatically, move between registrars, or be held defensively for years.
The more defensible question is whether the record is internally coherent: stable nameservers, current registration status, valid resolution, and an endpoint that responds.
03
Read DNS as declared intent
A and AAAA records declare web destinations. MX records declare mail routing. TXT records often carry authentication and ownership proofs. CAA records constrain which certificate authorities may issue for the name. DNSSEC adds cryptographic validation to the delegation chain.
Each record answers a narrow question. No single record establishes legitimacy, traffic, identity, or market value. The strongest reading combines signals and links every claim back to the public record.
SOURCES