Look up when a domain was first registered, how old it is in years and days, and its registrar, expiry, and status — all from live RDAP registration records.
Pro tip: RDAP only covers TLDs that support it; some country-code domains return no public registration date.
The tool queries RDAP (Registration Data Access Protocol), the modern, structured replacement for WHOIS that registries publish over HTTPS in machine-readable JSON. It reads the creation event for the domain and calculates the elapsed time to today, so the age is based on the official registry record rather than a guess or a scraped page. Because RDAP returns clean, typed fields instead of the free-form text old WHOIS used, the dates and registrar names it reports are far more consistent across providers.
From a single lookup the tool surfaces the registrable domain, the registration (creation) date, the age expressed both in whole years and in total days, the expiry date, the most recent update date, the registrar, and any domain status codes such as clientTransferProhibited. Each of those comes straight from the registry response.
After fetching the creation date, the tool measures the gap between that date and the current moment, then reports it two ways: a rounded number of years for a quick read, and the exact day count for precision. Showing both matters when a domain is only months old, because a value like "0 years" still carries a meaningful day count underneath. The result is a factual age, not a score — there is no judgement attached to whether a given age is good or bad.
Treat the expiry date as a practical reminder: a domain close to expiry can be renewed by its owner, so it is not a sign of abandonment on its own. Use the status codes as a signal too — codes like clientTransferProhibited simply mean a transfer lock is set, which is normal and often a good security practice. When you are comparing several domains, line up their creation dates rather than their ages, because the raw date removes any rounding ambiguity.
The most frequent error is equating registration age with content age. A domain registered in 2009 may have sat parked for a decade, or it may have been dropped and re-registered, which resets its real history even though the latest creation date looks recent. Another mistake is assuming an old domain automatically ranks better; search engines have said domain age in isolation is not a meaningful ranking factor. Always pair the registration date with a look at the site's actual archived content before drawing conclusions.
Input: example.com
Output: Registered 1995-08-14 · 30.9 years (11,294 days) · expires 2026-08-13 · registrar RESERVED-Internet Assigned Numbers Authority · status: client delete prohibited, client transfer prohibited, client update prohibited
Measured 2026-07-17 via rdap.org; the day count rises by one each day, so your run will show a slightly larger figure. The registration is old, but always confirm a site's actual content history separately.
Input: gnu.org
Output: Registered 1995-11-24 · 30.6 years (11,192 days) · expires 2026-11-23 · registrar Gandi SAS · status: client transfer prohibited
Measured 2026-07-17 via rdap.org. The transfer lock shown here is a normal, often beneficial security setting rather than a warning sign.
It uses RDAP, the structured successor to WHOIS, reading the official creation date the registry publishes in JSON.
Both a rounded number of years and the exact total number of days since the registration date, so short-lived domains still show a meaningful value.
Not by itself. Age is at most a minor trust signal; content, links, and relevance matter far more than the registration date.
Some TLDs, such as .ai and .de, do not expose a creation date through RDAP, so the age cannot be calculated even though other fields may appear.
No. A domain can be old but parked, or dropped and re-registered, so always check the site's real content history separately.
They are standard EPP/RDAP status values. For example, clientTransferProhibited means a transfer lock is set — a normal, often beneficial security setting.
RDAP coverage varies by TLD and registrar, so certain fields may simply not be published for every domain.
I document how each check works, where its data comes from, and which parts are only estimates.