Finding Aged ccTLDs: Where the Inventory Actually Lives and How to Source a Country-Code Domain Worth Buying in 2026

· Last reviewed · 18 min read

An aged ccTLD is a country-code domain such as .co.uk, .de, or .com.au that was registered years ago and already carries a backlink history earned inside its market. The reason to want one is settled: the extension sends Google a geo-targeting signal, and the inherited links supply the in-country authority a fresh registration lacks. The open question is where that inventory lives.

This is a harder question for a ccTLD than for a .com, and the sourcing guides never admit it. They point a buyer at the big drop-list aggregators and the registrar auctions, which run on generic-domain supply. Country-code names release through their own national registries, on their own mechanics, and a large share of them never appears in the firehose those guides recommend.

This guide maps every real sourcing channel, scores each on country-code coverage, and walks the acquisition step by step. SEO Domains operates the curated marketplace where aged and expired country-code domains are screened across their profiles before listing, so a buyer sourcing a .co.uk, .de, or .com.au starts from a vetted in-country authority asset instead of a raw drop list.

Where aged ccTLD inventory lives, and why it is harder than finding a .com

Aged ccTLD inventory lives across six channels: drop-list aggregators, paid filter tools, registrar auctions, aftermarket marketplaces, domainer forums, and the national registries themselves. Finding a country-code name is harder than finding a .com because a large share of ccTLD supply releases through registry-run mechanics that the generic drop-list tools do not fully index, so the channels that work for .com leave a buyer half-blind on a .de or a .co.uk.

The supply problem behind the search

A search for an aged .com lands on a mature, transparent market. Generic top-level domains flow through ICANN-accredited registrars, the expiry-to-deletion path is uniform, and aggregators index it daily. A buyer types a keyword into a drop-list tool and reads thousands of candidates with backlink data attached.

A country-code domain breaks four of those assumptions at once. Each ccTLD is delegated by IANA to a national registry that sets its own rules. A registry can publish a drop or release feed, or withhold it. A registry can require a local presence even to hold the name, and that gate also affects who can take it on transfer. The result is a fragmented market where the channel that surfaces a .com candidate shows nothing for the .nl equivalent.

What this guide answers, and where it sits in the cluster

This is the sourcing page in the country-code domain hub. The case for using an aged ccTLD, the geo-signal, the cold-start problem, and the eligibility traps, is made on the Local SEO & ccTLDs pillar. This page assumes that decision is made and answers the next question: given a target country, where does the buyable inventory sit, how is each channel different for a ccTLD, and how is a candidate screened before money changes hands. The per-country playbooks are linked from the closing section.

The domain lifecycle: when an aged ccTLD becomes buyable

A registered domain becomes available again only at specific points in its lifecycle. After the registration lapses it passes through a grace period, a redemption window, and a pending-delete phase before it drops back to the available pool or goes to auction. For an aged ccTLD the named stages are the same in shape, but the duration and the release mechanism are set by the national registry, not by a single global standard.

The stages where inventory appears

The generic lifecycle, defined by ICANN for gTLDs, gives the reference vocabulary. A name expires, sits in an auto-renew grace period, then enters the Redemption Grace Period where the prior owner can still reclaim it, then a pending-delete phase, and finally drops. Aged-domain inventory becomes buyable at two points: while it is auctioned by the registrar before deletion, and at the drop itself when it returns to the available pool.

Expiry

The registration ends. A registrar then runs an expired-domain auction during the days that follow, the earliest point a buyer can bid. Source: ICANN expired-registration lifecycle.

Grace / Auto-renew

A short auto-renew grace window where the original holder can still renew at cost. The name is not yet freely available.

Redemption (RGP)

The Redemption Grace Period. The prior owner can recover the name for a fee. A buyer cannot take it here. Source: ICANN RGP definition.

Pending Delete

A locked phase, on gTLDs five days, with no renewal and no registration. This is the window drop-catch services target. Source: ICANN pending-delete stage.

Drop / Release

The name returns to the available pool or to a registry release auction. On a ccTLD the timing and method are set by the national registry, not the gTLD clock.

Figure 1. The release points in a domain lifecycle, cited to the ICANN expired-registration stages. A ccTLD follows the same shape but on registry-defined timing, which is why a single global drop calendar does not cover every country code.

The six sourcing channels, and what each is good for

There are six places aged domain inventory is sourced: drop-list aggregators, paid filter tools, registrar auctions, aftermarket marketplaces, domainer forums, and national registry releases. Each was built for a different job. For a country-code name, the strength a channel has on a .com does not transfer cleanly, so the right channel depends on which country code is being chased.

The aggregators: the free firehose

Drop-list aggregators index expiring and dropped names daily and attach metrics like backlink counts, age, and archived history. ExpiredDomains.net is the canonical free example, publishing lists across 676 TLDs by its own count, and it is the first place practitioners look. The strength is breadth and zero cost. The weakness is that it is unfiltered raw supply, so the buyer carries the entire diligence burden, and its country-code coverage is only as deep as each registry allows it to be.

The filter tools: spam screening on top of the feed

Paid tools such as SpamZilla layer detection metrics onto the same drop feed, pulling spam scores, index status, and third-party authority data so a buyer can cut junk before bidding. The value is the filter the free lists lack. The constraint is that these are subscription products weighted toward generic domains, and a buyer still has to win and transfer the name through another venue.

Registrar auctions: scale, on generic-domain terms

Registrar-run auction platforms at venues like GoDaddy and Dynadot auction expiring names with backlink and traffic data attached, and they hold the largest volume of buyable inventory. The catch for a country-code buyer is coverage: a registrar only auctions the ccTLDs it resells, so the .com.au or .nl supply on a given platform reflects that registrar’s portfolio, not the whole market.

Aftermarket marketplaces and forums: where ccTLD trades concentrate

Aftermarket marketplaces and the domainer forums are the one place country-code aftermarket activity genuinely clusters. Marketplaces list premium and brandable ccTLDs for sale, and forums such as DNForum and NamePros host peer-to-peer ccTLD trades, including a dedicated country-code market board. The benefit is direct access to ccTLD sellers. The exposure is that forum trades are unscreened and trust-dependent, and marketplace pricing tracks brandability instead of earned authority.

The national registries: the source the others skip

The last channel is the registry itself. Nominet for .uk, DENIC for .de, auDA for .au, and SIDN for .nl each control how their names expire and release, and a registry can publish its own release or auction process. This is the channel the generic guides omit, and it is where a country-code name surfaces first, before any aggregator indexes it.

Why ccTLD drops do not all flow into the big aggregators

The big drop-list aggregators index a ccTLD only when its registry exposes the data they need. National registries set their own expiry, deletion, and release mechanics, and a national registry can decline to publish a public drop feed or route releases through its own auction instead of the open pool. So a country-code name can expire, release, and be re-registered without ever appearing in the firehose a .com buyer relies on, which is the structural reason a registry-aware search beats a tool-only one.

The data-availability gap

An aggregator can only list what it can read. For generic domains, the deletion and drop data is standardised and accessible, so coverage is near-complete. A national registry decides independently whether to publish equivalent data. Where it does, the ccTLD shows up in the aggregators. Where it does not, the name is invisible to a tool-only search even though it is genuinely available through the registry.

Registry-run release instead of an open drop

A registry can decline to return an expired name to a first-come pool at all. It runs its own release auction or a controlled re-delegation instead, so the name never hits the open drop the catch services target. A buyer watching only the generic drop calendar will miss inventory that the registry released on a different track entirely.

What this means for the search strategy

The practical takeaway is that a country-code search runs on two tracks at once. The aggregators and registrar auctions cover the ccTLDs whose registries feed them, and they are the right starting point for those codes. For the rest, the search has to reach the registry process directly, or a curated source that already aggregates across both tracks. A single tool is structurally incomplete for country-code supply, and treating it as complete is the single biggest reason a buyer concludes inventory does not exist when it does.

A channel-by-channel sourcing matrix for aged ccTLDs

The six channels differ on four axes that decide whether a channel is right for a given country code: how well it covers ccTLDs, whether it screens for quality, whether it handles transfer eligibility, and its price model. The matrix below scores each channel on those axes so a buyer can match the channel to the country code and the level of diligence support required.

ChannelccTLD coverageQuality screeningEligibility handledPrice model
Drop-list aggregator (ExpiredDomains.net)Partial, registry-dependentNone, raw metrics onlyNoFree
Paid filter tool (SpamZilla)Generic-weightedSpam and index screenNoSubscription
Registrar auction (GoDaddy, Dynadot)Limited to resold ccTLDsBacklink and traffic dataPartial, registrar policyAuction bid
Aftermarket marketplace (Atom, eBay)Premium and brandable ccTLDsListing-level, variesNoBuy-now or offer
Domainer forum (DNForum, NamePros)Strong, ccTLD-specific boardsNone, peer trust onlyNoNegotiated
National registry releaseAuthoritative, single codeNone, source of recordYes, registry enforcesRelease fee or auction
Curated marketplace (SEO Domains)Aged ccTLDs across marketsProfile screened before listingSurfaced before purchaseListed price
Figure 2. The sourcing channels scored on country-code coverage, screening, eligibility handling, and price model. No single self-serve tool covers all four axes for a ccTLD, which is the gap a curated, screened source is built to close.

Read down the screening column and the pattern is plain. The free and forum channels carry the widest country-code supply and the least diligence, the paid tools add a filter but on generic-weighted data, and the registry is authoritative for one code at a time. A curated marketplace is the one row that pairs aged country-code coverage with a profile screened before listing, which is the trade a buyer is making when choosing between doing the diligence themselves and starting from vetted inventory.

How to source an aged ccTLD, step by step

Sourcing an aged ccTLD runs in six steps: define the country and niche, pick the channel that covers that code, pull candidates, screen each on its in-country profile, confirm transfer eligibility, then acquire. At each step the done-right move and the mistake that wastes the effort sit side by side. The sequence below is the working method; the screening detail expands in the next section.

  1. Define the target country and niche first

    The country code and the topic decide the value, so they come before the search. The done-right move is to fix the market, .uk for a UK service business, .de for Germany, then look for names whose history matches that niche, because in-niche links carry more relevance than raw count.

    The mistake: shopping by metric across any country code. A high authority score on the wrong country code or an unrelated niche is geo-irrelevant authority, and it does the local campaign no good.

  2. Pick the channel that covers that country code

    Match the channel to the code using the matrix above. The done-right move is to start where that ccTLD has real supply, the aggregators and registrar auctions for codes they index, the registry process and ccTLD forum boards for the rest, and a curated source that spans both.

    The mistake: running one generic drop tool and concluding the inventory does not exist. A tool-only search is blind to registry-released country-code names, which is where a real share of the supply sits.

  3. Pull the candidate list

    Gather names with their raw metrics from the chosen channel. The done-right move is to filter the pull on the signals that matter for a local play first: age, referring domains, and whether the link sources sit inside the target country.

    The mistake: treating the channel’s headline metric as the verdict. Backlink counts and inflated authority scores on a raw list are a starting filter, not a diligence pass, and a name that looks strong on the list can be toxic underneath.

  4. Screen each candidate on its in-country profile

    Read the real backlink profile, the registration history, and the archive. The done-right move is to confirm the links were earned inside the target market and that the history is clean, using the checklist in the next section. Read the registration history through RDAP, the current standard for that lookup.

    The mistake: skipping the spam screen because the headline metric looked good. A previously spammed or off-country ccTLD passes a metric check and fails the campaign.

  5. Confirm transfer eligibility before you commit

    A country code can gate who is allowed to hold it. The done-right move is to verify the registry’s eligibility rule for that ccTLD, a local presence, a local address, or none, before bidding, because that rule decides whether the acquisition can complete at all.

    The mistake: winning the name, then discovering a local-presence requirement blocks the transfer. The eligibility check belongs before the bid, not after it, which is the trap the next section details.

  6. Acquire, transfer, and verify

    Complete the purchase, move the name to the holding registrar, and confirm the profile survived the transfer. The done-right move is to acquire from a source where the screening is already done and the eligibility is surfaced, then verify the registration and links post-transfer. Screened aged ccTLDs are listed for this on the SEO Domains marketplace.

    The mistake: closing on an unscreened forum or auction name with no recourse if the profile turns out toxic or the eligibility fails. An unvetted acquisition leaves the diligence and the risk entirely on the buyer.

Figure 3. The six sourcing steps, each pairing the done-right move with the mistake that wastes the effort. Steps four and five, the in-country screen and the eligibility check, are the two where country-code sourcing breaks down, and they are the two a curated source resolves before a name is listed.

Eligibility: the trap that voids a sourcing win

A set of country-code registries gate registration on a local connection, and that gate also governs who can take a name on transfer. A buyer can win an aged ccTLD at auction and still be unable to complete the transfer if the registry requires a local presence, a local address, or a national identifier the buyer does not hold. Checking the eligibility rule for the specific country code before bidding is the step that separates a completed acquisition from a forfeited one.

The registry rules that gate a transfer

Eligibility is set per registry, and the rules range from open to strict. The light end is open: Nominet allowed non-UK registrants to hold .uk names from 2014, so the .uk gate adds no barrier. Others hold a presence test: auDA requires an Australian presence for .com.au, and a range of European and Asian codes require a local address or national identifier. The point for sourcing is that the rule is the registry’s, not the seller’s, and it applies to the aged name on transfer exactly as it does to a fresh registration.

Country codeRegistryEligibility gate on transfer
.co.uk / .ukNominetOpen. Non-UK registrants permitted since 2014.
.deDENICOpen to register; an administrative contact in Germany is required.
.com.auauDAAustralian presence test required to hold the name.
.nlSIDNOpen; a non-resident holder needs an administrative arrangement.
.atnic.atOpen, with limited local-contact conditions.
.caCIRACanadian Presence Requirements apply to the registrant.
Figure 4. Representative eligibility gates by registry. Cite the registry policy for the exact, current rule before bidding; the gate governs an aged-domain transfer as much as a new registration. The per-country guides linked in the closing section detail each one.

The per-country detail belongs in the country guides, not here. What matters for sourcing is the sequence: read the registry rule for the code before the bid, because an eligibility gate discovered after a win turns a sourcing success into a stranded purchase. The full presence-test mechanics for the major markets are covered in Aged .com.au for Australian SEO and Aged .ca for Canadian SEO.

The screening checklist: a vetted ccTLD versus a junk one

An aged ccTLD is worth buying only if its inherited profile holds up to a screen. The checks that decide it are the in-country share of its backlinks, the quality not the count of those links, a clean spam and archive history, geo-relevance of the prior use, and the registry eligibility to transfer. A name that passes is an in-country authority asset. A name that fails any of them is a junk ccTLD bought for a metric, and a metric is exactly what does not survive the campaign.

The signals that separate the two

Screening a country-code name adds a geo-dimension on top of the standard backlink diligence. A .de with strong links from across the world but few from inside Germany sends a weaker local signal than a .de with fewer links concentrated in-market. The metrics that read a profile, referring domains, authority scores, and the trust ratios, are documented in the Domain Authority & Metrics hub, and the acquisition diligence on reading a registration history is in the Expired Domain Fundamentals hub.

CheckJunk ccTLD (liability)Vetted ccTLD (asset)
In-country link shareLinks mostly off-market or irrelevant geographiesA real share of links from inside the target country
Backlink qualitySpam-inflated count, low-trust sourcesEditorially earned links from genuine in-country sites
Spam and history screenPrior spam, unrelated abuse, or a flagged profileClean history, no toxic inheritance, topical continuity
Archive and prior useEmpty or off-country archive, no real local presenceA documented prior business inside the market
Registration history (RDAP)Opaque or patterned, read after purchaseRead through RDAP before purchase, transfer path clear
Transfer eligibilityLocal-presence gate discovered after the bidEligibility confirmed before committing
Figure 5. The screening checklist for an aged ccTLD. The right column converges on one outcome: a country-code domain with in-country earned authority, a clean history, and a clear transfer path. A name that fails the first two rows cannot be salvaged by the price.

Finding aged ccTLDs: frequently asked questions

The five questions buyers raise when they search for where to find and buy an aged country-code domain, answered against the sourcing channels and the screening checklist this guide sets out.

Q1Where do you buy an aged ccTLD in practice?

Across six channels: free drop-list aggregators such as ExpiredDomains.net, paid filter tools such as SpamZilla, registrar auctions at GoDaddy and Dynadot, aftermarket marketplaces, domainer forums such as DNForum and NamePros, and the national registries themselves. For a given country code, start where that code has real supply and screening, which is not the first generic tool a buyer reaches for.

Q2Can you find aged ccTLDs on the free expired-domain lists?

Partly. ExpiredDomains.net lists across 676 TLDs by its own count and includes a range of country codes, so a portion of ccTLD supply is there for free. The gap is that its coverage of any country code depends on what that registry publishes, so the free lists are a real starting point for indexed codes and blind to the registry-released names they cannot read.

Q3Why are aged ccTLDs harder to find than aged .com domains?

Because each country code is run by its own national registry with its own expiry and release mechanics. Generic domains follow one standardised, fully indexed lifecycle. A ccTLD can release through a registry auction or a controlled re-delegation that the generic drop tools never see, so a tool-only search misses inventory that genuinely exists.

Q4What do you check before buying an aged ccTLD?

Five things: the in-country share of its backlinks, the quality of those links, a clean spam and archive history, the registration history read through RDAP, and the registry eligibility to transfer. A name can pass a headline authority score and fail every one of these underneath, which is why a metric alone is never the verdict.

Q5Does a country-code eligibility rule block buying an aged name?

It can. A registry that requires a local presence, such as auDA for .com.au or CIRA for .ca, applies that rule to an aged name on transfer, not only to a new registration. A buyer who wins the name without meeting the gate cannot complete the transfer, so the eligibility check belongs before the bid.

Sourcing a screened aged ccTLD: the marketplace and per-country routes

Every channel in this guide resolves to the same decision: do the diligence across a fragmented, registry-dependent market, or start from inventory where the screening and eligibility are already resolved. A curated marketplace is the route that pairs aged country-code coverage with a profile screened before listing. SEO Domains operates that marketplace, and the per-country guides below carry the registry-specific detail for each major market.

Why a screened source closes the sourcing gap

The sourcing problem this guide opened with is fragmentation: six channels, partial country-code coverage, registry-run releases the tools cannot see, eligibility gates that void a win, and no screening on the widest-supply channels. A curated marketplace is the one source that aggregates across the channels and applies the screen before a name is listed, so the buyer inherits the diligence instead of carrying it. That is a product, an aged country-code domain ready to acquire, not a tool, a subscription, or a service.

The per-country sourcing routes

Sourcing splits by country code, because the registry, the eligibility gate, and the in-market link sources differ for each. The country guides carry the registry-specific release and eligibility detail, and the marketplace lists screened inventory for each:

Aligning the chosen ccTLD with the local map listing afterward is the operational next step, covered in GBP and aged ccTLD alignment.

Browse screened aged country-code domains

The legitimate demand behind every search for where to buy an aged ccTLD is access to a country-code name that already carries real in-country authority, with the diligence and eligibility resolved. That is the product. SEO Domains operates the curated marketplace where aged and expired country-code domains are screened across their backlink profiles before they are listed and priced.

Kalin Karakehayov, Chief Executive Officer at SEO Domains

Kalin Karakehayov

Chief Executive Officer @ SEO Domains · Founder

Kalin is the founder of SEO Domains, the world’s largest supplier of aged domain names across every country and niche. A former professional chess player with 18 years in SEO, he sets the company’s standards for sourcing and screening high-authority domains.

He leads SEO at the SEO Domains marketplace, which operates a 220,000+ curated catalogue from $100 entry-level domains through premium acquisitions, screened across the catalogue, with Managed Account expert support for premium-tier clients.

· Last reviewed