Domain expiry checker

A domain expiry checker should not assume the renewal term

Domain registrations are often renewed in familiar intervals, but that is not evidence for a particular deadline. This checker reads the current RDAP record and accepts only an exact expiration event. The result shows the source timestamp, the dated lookup and the time between them. If the registry omits expiration, the page says so instead of adding a year to registration or guessing from a registrar convention.

Multiple expiration events or an unsupported timestamp are also visible states. The source entries remain in the receipt, but the page withholds a single deadline. “Last changed,” transfer and database-update events never substitute for expiration simply because they are recent.

Expiration does not mean immediate availability

A past or approaching expiration event is not a promise that anyone can register the name on that date. Renewal, auto-renew grace, redemption, registry holds and deletion can all sit between an expiration timestamp and public release. Registry policy and registrar account state also change what the current registrant can do. The registrar link is therefore a verification step, not a purchase guarantee.

The same boundary matters when evaluating a name that appears unused. The domain name finder asks a different question—whether the mapped registry currently returns a domain record. Neither an expiry date nor a not-found response reserves a domain or determines its price.

How the RDAP receipt stays auditable

The browser downloads IANA's DNS RDAP bootstrap, constructs the registry URL from that directory and refuses to follow the result to an unlisted origin. A successful response must identify the domain that was entered, use a supported JSON content type and remain within a bounded response size. The receipt preserves the registry event text rather than presenting a reformatted date as if it were the source.

Some domain endings have no browser-usable HTTPS RDAP mapping, and some mapped registries return a valid record with no expiration event. Those are different limitations. The first is labeled unsupported; the second is labeled missing evidence. A rate limit, unsafe redirect, malformed object and no record each keep their own receipt as well.

The expiry check leaves CreatorValet out of the request path

Calculation and receipt formatting stay in this tab. After you click the button, a browser worker asks IANA which HTTPS RDAP service covers the ending and then requests the public domain object from that listed origin. No CreatorValet server handles or saves the name. Keep the copied JSON with a renewal note when the evidence needs an audit trail, and use the registrar account for any account-specific renewal status.

Use the domain age checker when you need elapsed whole UTC days from an unambiguous registry lifecycle event. Registration evidence and expiration evidence remain separate claims even when the same RDAP record contains both.