Domainyze reads expiry dates from the public registry record. That record is accurate most of the time and lags reality some of the time, and on a handful of extensions it is genuinely hard to read. Here is why, and which source to trust when they disagree.
The short answer
Your registrar's control panel is authoritative for domains you own. It is where the renewal actually happens, and it is updated first. Domainyze reads the public record, which is downstream of it.
1. Propagation delay
Domain data is not centralised. A renewal updates your registrar's records, then syncs to the registry, then reaches the public WHOIS and RDAP servers. That path commonly takes several hours and can take a full day, so a domain you renewed this morning may still show the old date this afternoon. Some servers also cache responses, which adds to it.
This is the answer in the large majority of cases. If you have just renewed, wait a day before assuming an error.
2. Bulk renewals and manual adjustments
A bulk renewal across many domains, or a manual adjustment your registrar makes after a billing problem, can take noticeably longer to reach the public record than a single ordinary renewal.
3. Grace periods make "expired" ambiguous
The registry sets the official expiry date, but registrars add their own grace period on top of it, commonly 30 to 45 days, during which you can still renew normally. A domain can therefore be past its published expiry date and completely fine. Domainyze reports the stage as well as the date for exactly this reason — see the complete lifecycle guide.
4. Some extensions publish less, or publish it differently
This is where most of the remaining discrepancies live, and it is concentrated in country-code extensions.
- Different formats. Expiry dates appear as
YYYY-MM-DD,DD-MM-YYYY,MM/DD/YYYYand others. Domainyze normalises the formats it knows and will leave a date blank rather than publish a guess. - Different fields. Some registries publish an update date but no explicit expiry date at all. There is nothing to parse in that case, and the domain will show no expiry.
- Different disclosure rules. Several registries publish substantially less data than a gTLD does, on privacy grounds.
- RDAP gaps. Not every registry runs RDAP, and some that do omit expiry from it. Domainyze falls back to WHOIS for those, which is slower and more heavily rate-limited.
Supported TLDs and extensions covers what to expect per extension family, and How we calculate expiration dates covers how the date is derived once it has been read.
What to do about a discrepancy
- Check your registrar. Treat that date as correct for renewal purposes.
- Wait 24 to 48 hours if you have recently renewed or transferred.
- Refresh the domain from its page in Domainyze to force a fresh lookup.
- Contact support if it persists, with the domain name and the date your registrar shows. A parsing problem on a specific extension is fixed centrally, so one report improves every domain on that extension.