Free Domain Age Checker

What a domain age checker actually reads

Domain age is not computed or estimated. It is a single field in the registry's own record, returned by RDAP as an event with the action registration. Everything else on this page, including the age in years, is arithmetic on that date.

A real record looks like this. These are the events for google.com, read live:

Three dates, three different questions. Most tools show all three and label them badly, which is where the misreadings start.

Domain age is not a Google ranking factor

This is worth stating plainly because nearly every other domain age checker implies the opposite. Google's public position, repeated for years by their Search Advocates, is that the age of a domain is not a ranking signal. What correlates with rankings is everything an old domain tends to have accumulated: links, content, brand searches, and history. A domain registered in 2004 and parked until last week carries none of that.

So use this tool to answer "when was this registered", not "will this rank". If you are buying an aged domain expecting an SEO head start, the registration date is close to the least informative thing you can look at.

Where domain age genuinely is used as a signal is abuse scoring. Email filters, payment-fraud models, and security tooling weight newly registered domains heavily, because a domain created three days ago is statistically far more likely to be disposable. That is a real and defensible use. Ranking is not.

The age resets, and RDAP will not tell you

The single most common error in reading a registration date is assuming it covers the whole life of the name. It does not. If a domain expires, drops, and is registered again by someone else, the registry writes a new registration date and the previous history disappears from RDAP entirely.

So a 2019 date can mean either "created in 2019" or "existed since 1998, dropped in 2018, picked up in 2019". RDAP cannot distinguish them, and neither can any tool built on it. If that difference matters, and for a domain purchase it usually does, you need archive history or a paid historical WHOIS aggregator, not an age checker.

For scale, the oldest .com registrations are genuinely ancient and still readable this way: symbolics.com returns 1985-03-15, the first .com ever registered, with ibm.com at 1986-03-19 and hp.com at 1986-03-03.

Some domains have no age at all

If this tool returns nothing for a domain that obviously exists, the cause is almost always the TLD rather than the domain. RDAP is mandatory for gTLD registries under ICANN contract, but country-code TLDs are outside that regime, and 238 of the 1,438 delegated TLDs publish no RDAP service whatsoever. .io, .co and .me are all in that group: a lookup for github.io, google.co or about.me returns a flat 404, so there is no registration date to show.

That is the same limitation behind the DNS fallback on our domain availability checker, and it has no workaround short of a registry-specific query or a paid aggregator. A missing age on a .io is not a bug and not evidence the domain is new.

Expiration is not when the domain becomes available

The expiration date is where most people misjudge timing. A domain does not become registrable the day it expires. It moves through a fixed sequence first, and for gTLDs the shape of it is consistent:

So an expiration date is the earliest possible start of a roughly 75-day countdown, not a date to put in your calendar. During all of it the domain reports as registered.

"Last changed" does not mean the site changed

The last changed event is the registry record's timestamp, and the things that move it are registrar transfers, contact or nameserver changes at the registry, registrar lock changes, and DNSSEC re-signing.

The things that do not move it include every content change, every A or AAAA record edit inside a zone you already control, and every certificate renewal. A domain can be rebuilt from scratch without the registry timestamp shifting at all. If you want to know when DNS last changed, look at the SOA serial, not this field.

Reading this tool honestly

• A recent date is meaningful. Days-old domains are a genuine abuse signal.
• An old date is weak evidence. It says the current registration is old, nothing about content, ownership continuity, or reputation.
• A missing date usually means the TLD, not the domain.
• Expiration is a countdown start, not a release date.

If you want the rest of the registry record rather than just the dates, the WHOIS lookup returns registrar, nameservers, and status codes for the same domain, and the status codes are what tell you whether a domain is locked, expired, or on its way out.

Checking domain age from code

The whole lookup is one request, and the date is one field:

curl -s -H "accept: application/rdap+json" https://rdap.org/domain/example.com \
  | jq -r '.events[] | select(.eventAction=="registration") | .eventDate'

Our hosted version is documented at the domain age API reference, returns the parsed age alongside the raw dates, and needs no key. Two things to plan for if you are batching: RDAP endpoints rate-limit anonymous clients hard, and the registration event is genuinely absent for some registries, so treat a missing date as a normal outcome rather than an error.

If you are running a SaaS

Domain age shows up in product work more often than people expect: scoring signups, weighting abuse heuristics, or deciding whether a customer's domain looks disposable before you issue a certificate for it.

Domainee is a custom domains API for SaaS with a native MCP server — 50 domains and 100 GB free. If you are letting customers attach their own domains, it handles DNS verification and certificate provisioning for multi-tenant custom domains, and the age check above is a reasonable input to whether you want to onboard a given domain at all.