If a domain's status or details in Domainyze look stale, or disagree with what your registrar shows, one of the causes below is almost always responsible. They are ordered by how often they turn out to be the answer.
1. The domain has not been checked yet
Domainyze shows what the last check found. How recently that was depends on the domain's state and your plan: a quietly-registered domain on a free plan is checked every twelve hours, while a name in the final approach to a drop on a paid plan is checked every couple of minutes. The full table is in How fast are availability checks?.
The "Last scan" figure on the domain page tells you exactly how old the data is. If you need an answer sooner than the next scheduled check, refresh the domain from its page.
2. Propagation delay: the public record has not caught up
This is the single most common cause of a genuine disagreement with your registrar, and it is worth understanding once.
WHOIS and RDAP data is not held in one central database. It is spread across registrars and registries worldwide. When you renew a domain, change nameservers or update contact details, your registrar updates its own records first, then syncs to the registry for that extension, and only then does the change reach the public servers Domainyze reads. The whole path commonly takes several hours and can take a full day.
Your registrar's control panel is the authoritative source for your own domains. Domainyze reads the public record, which lags it.
3. Caching, at their end and ours
Many public WHOIS and RDAP endpoints cache responses to reduce load, so even a fresh query can return data that was accurate an hour ago. Domainyze queries authoritative sources where it can, but intermediate caching still happens. A manual refresh bypasses our own caching layer and forces a new lookup.
4. WHOIS privacy is masking the record
If the domain uses a privacy service, the public record shows the privacy provider's details rather than the registrant's, by design. If you have just enabled or disabled privacy, the change takes the same propagation time as any other.
5. The extension reports things differently
Registries differ widely in what they publish and how. Some ccTLD registries publish an update date but no clear expiry date, some use unusual date formats, and some publish far less than a gTLD does. Domainyze normalises what it can and leaves a field blank rather than guessing when it cannot.
If an expiry date specifically looks wrong, Why expiration dates can be wrong or delayed goes into that case in detail.
6. The domain is genuinely stuck
A name in pendingDelete can sit in the same state for days while the registry works through its deletion queue. That is not a stale reading; it is the actual state, and the drop forecast is the thing to watch rather than the status field.
When to contact us
If a discrepancy with your registrar persists beyond 48 hours, after a manual refresh, contact support with the domain name and what your registrar shows. A parsing problem on a specific extension is something we fix centrally, so reporting one helps everyone on that extension.