Aged domain vs expired domains: the disambiguation SEO buyers need before acquisition

What is the difference between an aged domain and an expired domain

An aged domain is a registration with an old creation date. An expired domain is a registration past its renewal date.

Aged describes how long the name has existed. Expired describes its current lifecycle status. The two attributes are independent, so a single domain can be aged, expired, both, or neither.

The popular comparison pages present aged and expired as mutually exclusive opposites. The registry status model and ICANN policy show them as two separate axes that intersect. That intersecting framing is what a buyer needs to read inventory accurately.

Aged is a property of the name; expired is a property of the registration.

The age of a domain belongs to the name itself and persists through ownership changes, registrar transfers, and lapses. The expired status belongs to the current registration and resolves the moment the name renews or drops.

A buyer who reads a listing labelled aged learns the name is old. A buyer who reads a listing labelled expired learns the registration lapsed. The two labels answer different questions, and a precise acquisition decision reads both.

The mutually-exclusive framing on comparison pages is the source of buyer confusion.

The high-ranking comparison articles define aged as continuously registered and expired as lapsed, which forces the reader to pick one label per domain.

That framing fails the moment an expired domain is re-registered, because the re-registered name is both old and recently lapsed.

The accurate model keeps the axes apart and lets them intersect, which is how marketplace inventory and the registry status record represent the same domains.

What aged means as a domain attribute

An aged domain has an original creation date recorded in WHOIS or RDAP that places the name beyond a 1-year threshold, regardless of current registration status.

The creation date is set at first registration. It persists across every renewal, transfer, and lapse. It resets only when the registry executes a formal deletion and the name returns to the available pool.

Domain age is the elapsed time between that creation date and today.

Domain age is read from the creation-date field, not the registration-date field.

WHOIS output labels the relevant value Creation Date and RDAP returns it in the registration event of the JSON record.

A re-registered domain shows a fresh registration date alongside the preserved creation date, and the age calculation reads the older creation field. The companion Aged Domain Fundamentals hub anchors the field-by-field method across the wider sub-hub.

Reading the wrong field understates a re-registered domain’s true age.

No single age threshold defines aged across the industry.

ICANN sets no minimum age for the aged label. The threshold each source applies tracks its use case:

• Cold-email infrastructure providers treat 2 to 4 weeks as sufficient for sender reputation.
• Premium aged-domain indexes filter at 5 or more years.
• SEO acquisition desks work from a 1-year inclusive baseline.

The threshold a buyer applies depends on the use case. That is why the term reads loosely across sources. It is also why a marketplace records the exact creation date instead of a bare aged tag.

What expired domains are as a registration status

An expired domain has passed its renewal date and entered the ICANN Expired Registration Recovery Policy lifecycle.

The policy, effective 31 August 2013, sets three post-expiration phases before the name drops back to the registry pool:

• Auto-renew grace window of up to 45 days.
• Redemption Grace Period of 30 days.
• Pending delete of 5 days.

Expired is a status that the registration moves through, not a permanent property of the name.

ICANN ERRP governs the post-expiration phases for all gTLD registrars.

ICANN ERRP applies under the Registrar Accreditation Agreement, so the phases hold across .com, .net, .org, and the wider gTLD set. The auto-renew grace window grants the original registrant renewal at standard pricing.

The 30-day Redemption Grace Period grants recovery at an elevated fee. The 5-day pending delete locks the name before the drop.

The lifecycle disambiguation in Expired vs deleted vs dropped: domain lifecycle disambiguation across 5 RFC 3915 states maps each phase to its registry status code.

EPP status codes mark each expiration phase for automated reading.

Registry status codes label the lifecycle phase in machine-readable form:

• autoRenewPeriod marks the grace window.
• redemptionPeriod marks the recovery window.
• pendingDelete marks the final 5-day lock.
• available marks a name absent from the zone with no active status.

These codes let a screen classify expiration status without prose interpretation. That machine-readable read is the foundation the sub-category model in this article builds on.

Where aged and expired overlap

Aged and expired overlap because an expired domain that is re-registered after it drops becomes an aged domain.

The creation date carries forward, the historical backlinks remain pointed at the name, and the indexed history persists in the archive. The re-registered name is both old by creation date and recently lapsed by registration history.

The overlap is where marketplace inventory concentrates. It is also where the mutually-exclusive framing breaks down.

Re-registration preserves the creation date and the inherited link equity.

When a name drops and a new registrant takes possession, the registry assigns a fresh registration date and preserves the original creation date in the record and in WHOIS history archives.

The backlinks that pointed at the old pages remain in place, and the indexed history stays retrievable.

The re-registered domain inherits an aged profile through that continuity of creation date and link graph, which is the mechanism the marketplace prices.

The aged label on most inventory describes domains that already expired once.

The premise that aged means unbroken registration excludes the bulk of aged inventory available to buyers. Curated aged listings, pre-release auctions, and drop-catch supply draw heavily from names that lapsed and re-entered circulation.

An aged listing therefore reports creation-date age and inherited authority, and a separate registration-history read reports whether a lapse occurred.

The decision in Expired vs new registration for SEO turns on that same inherited-authority versus fresh-start trade-off.

How domain age differs from registration continuity

Domain age and registration continuity are two separate attributes a buyer reads independently. Domain age counts years since the creation date and is immutable. Registration continuity counts the gaps between renewals and records every lapse.

A 12-year-old domain with three lapses is still 12 years old, and its continuity record carries three breaks. Continuity, not raw age, predicts how cleanly inherited authority transfers.

Continuity is the deciding variable, not the age figure on its own.

Industry analysis from Investors Club and Search Logistics lands on the same conclusion: age alone is not the asset, continuity is.

A name that held its registration unbroken preserved its backlink profile and indexed standing more reliably than a name that lapsed and was re-registered. The age figure sets the ceiling on inherited authority.

The continuity record reports how much of that ceiling transferred in practice, which is the reason a screen reads both fields and not the aged tag alone.

A lapse triggers re-evaluation of inherited signals without resetting domain age.

A registration gap does not reset the creation date or erase the backlinks. It re-opens the context the name is read against when a new owner rebuilds. The signals persist; their interpretation is reassessed on re-registration.

The question of whether a drop resets the practical SEO standing is the subject of its own guide in this sub-hub. The distinction between the immutable age field and the mutable continuity record is the foundation that guide builds on.

The 5 sub-categories the two axes produce

Combining domain age with registration status produces 5 sub-categories: currently-active aged, aged in grace, aged in redemption, aged in pending delete, and aged-and-dropped.

Each sub-category maps to a distinct EPP status code, a distinct acquisition channel, and a distinct due-diligence priority. That mapping is the practical payoff of keeping the axes separate.

The EPP status code identifies which sub-category a domain occupies.

A status of ok with a creation date beyond the threshold identifies currently-active aged inventory. The autoRenewPeriod, redemptionPeriod, and pendingDelete codes identify the three expiration phases in sequence.

An available state with a recent expiry identifies aged-and-dropped supply. The status code therefore does the classification work, turning the aged-versus-expired question into a precise lookup instead of a judgment call.

Recovery rights and acquisition channel follow from the sub-category.

During grace and redemption, only the original registrant can recover the name, so buyer acquisition opens at pending delete through pre-release auction and drop-catch.

Currently-active aged inventory transfers through direct sale and brokerage at the current owner’s discretion. Aged-and-dropped inventory routes through drop-catch or standard re-registration.

The sub-category fixes the channel, the pricing band, and the due-diligence depth in a single read.

Two factors a buyer can determine settle the sub-category.

Two factors a buyer can determine before purchase settle the sub-category:

• Whether the registration is past its renewal date.
• Where a lapsed name sits in the post-expiration lifecycle.

A buyer who reads those two factors against the quadrant in Figure 5 lands on the named category, the EPP status code, and the open acquisition channel. The mutually-exclusive labels the comparison pages force never enter the read.

The criteria a buyer applies are the registration status and the lifecycle phase, not the aged tag. The sub-category model therefore returns a definition instead of a verdict on quality.

Why the distinction matters for SEO buyers

The distinction matters because the aged-versus-expired category sets the acquisition channel, the pricing band, the recovery-rights position, and the due-diligence depth.

A buyer who reads aged as a guarantee of unbroken history overpays for a lapsed name. A buyer who reads expired as a guarantee of low quality skips a strong inherited profile.

The correct read prices the name on its real attributes.

The benefits a buyer is acquiring sit in the inherited backlink profile and the indexed topical record, not in the label printed on the listing.

The factors worth weighing before a bid run across three reads, taken using a WHOIS or RDAP check alongside a backlink audit:

• Registration continuity across the renewal history.
• Topical alignment between the prior topic and the build.
• Prior penalty exposure on the inherited profile.

Buyers who consider only the headline aged tag find names that lapsed presented as continuously held. The cross-check against the registration history separates the real inheritance from the marketing claim.

Inherited backlinks persist across a lapse, and context is what gets re-evaluated.

The backlinks pointed at an aged name stay in the link graph through a registration gap. A re-registered domain that rebuilds on the prior topic preserves the relevance those links were earned against.

A re-registered domain repurposed onto an unrelated topic breaks that relevance, and the inherited value attached to the old pages degrades as those pages return errors.

The inheritance is real and conditional, and the condition is topical alignment, not the aged label.

The catalogue screen resolves the inherited-authority question before purchase.

An aged or expired name carries inherited signals worth verifying:

• The backlink profile.
• The registration-history continuity.
• The indexed topical record.
• Any prior penalty exposure.

Reading these by hand across raw drop lists is the work the curated channel removes.

The SEO Domains 7-vector inheritance screen reads the registration history, the link profile, and the topical record at inventory ingestion. The listing reports the real sub-category and the verified inheritance instead of a bare aged or expired tag.

The risk of an unverified inherited profile resolves to a pre-screened catalogue listing.

How the catalogue classifies aged and expired inventory

The catalogue classifies every listing by the intersection of creation-date age and registration status, then verifies the inherited profile across a 7-vector screen.

The buyer reads the real sub-category, the registration history, and the inherited authority instead of a marketing label. The aged-versus-expired distinction stops being a guess and becomes a recorded field on each listing.

The sub-category and the inheritance screen ship with every listing.

A SEO Domains listing reports the creation-date age, the registration-status sub-category, the continuity record, and the screened inheritance together.

The buyer reviews a vetted entry instead of running a parallel WHOIS, RDAP, and backlink audit across raw drop lists.

The curated channel is the tool that delivers pre-sorted inventory, so the aged-versus-expired question is answered at the listing layer before a single bid.