WHOIS History Services Compared: The Major Domain History Archives, Side by Side, and How to Pick the Right One

What is a WHOIS history service, and why a domain’s past matters

A WHOIS history service is a commercial database that captures and stores WHOIS registration snapshots over time, so the record a registry published on a past date can be retrieved after the live record has changed. It answers who owned a domain before, across each ownership change, where a live WHOIS or RDAP query answers only who owns it now.

The difference between a live lookup and a history archive

A live WHOIS or RDAP query returns the present state of a domain: the current registrant fields the registry exposes, the registrar, the status codes, and the dates. It is a snapshot of today, and it overwrites itself the moment the registration changes. The mechanics of that live query are covered in WHOIS: protocol and how to read the data.

A history service runs that same query on a schedule, stores each result as a dated record, and keeps the old snapshots when the live one moves on. The archive is the byproduct of doing the lookup repeatedly for years and never throwing the older copies away.

Why a domain’s registration past carries weight

A domain inherits its history. An aged name that passed cleanly through one long-term owner reads differently from one that churned through four registrants and two dropped registrations in three years. The first pattern signals continuity, the second signals a name that was flipped, parked, or abandoned, and that distinction shapes what the domain is worth and how safe it is to build on.

The record also dates the entity. A first-registration date establishes genuine age, and ownership continuity confirms the name was used by a real operator, not recycled through a spam cycle. Reading that record is the first diligence step on any acquisition, a point the closing section returns to.

Why the archive start year is the first criterion: GDPR and the RDAP switch

The difference that outweighs every other between WHOIS history services is how far back the archive reaches, because two regulatory events split the data into eras. GDPR redacted gTLD registrant identities from 25 May 2018, and RDAP replaced WHOIS as the ICANN standard on 28 January 2025. An archive that started before 2018 holds owner names that no live lookup will ever show again.

The GDPR redaction line of 2018

The General Data Protection Regulation took effect on 25 May 2018. To comply, ICANN had adopted the Temporary Specification for gTLD Registration Data on 17 May 2018, which required registrars to redact the registrant name, email, and contact details from public gTLD WHOIS output. From that point, a live lookup on a privacy-affected gTLD domain returns redacted contact fields in place of a named owner.

That single change is what makes a pre-2018 archive valuable. WhoisXML API states plainly that its history records from before 2018 are available without privacy redactions, which means an archive that was capturing snapshots in 2015 holds named-owner records that a live query in 2026 cannot reproduce. The archive froze the data before the redaction rule erased it from the public view.

The RDAP switch of January 2025

The second era boundary is the protocol change. RDAP, the Registration Data Access Protocol, replaced WHOIS as the standard ICANN registration-data service on 28 January 2025, returning the same registration data in a structured JSON format with tiered access. The successor protocol and what it changes are detailed in RDAP: the successor to WHOIS.

For a history archive, the switch matters in two ways. Records collected after that date originate from RDAP, not legacy WHOIS, and DomainTools itself carries a notice flagging the possible deprecation of its WHOIS services after 28 January 2025. The serious archives are migrating their collection to RDAP, and the records on either side of that boundary come from different protocols.

The major WHOIS history services, side by side

Four commercial archives lead the field: DomainTools, WhoisXML API, WhoisFreaks, and Whoxy. They differ on archive start year, the scale of records and domains covered, pre-2018 redaction handling, free access, and price model. Each vendor publishes its own figures and sells only its own product, so the comparison below is assembled from those published numbers, side by side, in one place.

The headline figures, as each vendor publishes them

The four archives split into two camps. DomainTools owns the longest lookback and the investigator reputation, but gates everything behind a subscription. The three API-first vendors compete on scale, freshness, and price, with free tiers that make a single lookup cheap or free.

How to read the scale numbers

The record and domain counts are vendor-reported marketing figures, so they are best treated as order-of-magnitude, not audited fact. A higher record count signals more snapshots captured over time, while a higher domain count signals broader coverage of which names the archive has watched at all. The two move together but are not the same: an archive can hold billions of records on a smaller set of frequently changing domains.

Start year resists that ambiguity, which is one more reason it is the cleanest selection criterion. WhoisFreaks claims records back to 1986 and DomainTools claims tracking since 1995, both of which predate the 2018 redaction line by decades, while Whoxy’s November 2012 start sits comfortably before it as well. WhoisXML API’s roughly 2010 start also clears 2018, so all four hold a pre-redaction era of records, with the earlier two reaching deepest.

Free versus paid, web lookup versus API, and bulk export

Access splits along two axes: free trial versus paid, and single web lookup versus programmatic API. ICANN Lookup and the lightweight free tools handle a one-off current check at no cost. The four archives gate deep history behind credits or a subscription, and the API plus bulk-download tier is what separates a casual check from an investor screening names at volume.

The single-lookup path

For one domain, the friction is low. WhoisXML API grants 500 API credits and a capped web tool that returns the last three records for a quick look. Whoxy hands new users free trial credits and bills per query with no monthly fee, so a single history query costs cents. WhoisFreaks issues free API credits on signup. The free tools at osint.sh and IQWHOIS return a basic history with no account at all.

The trade is depth. A free or capped lookup typically surfaces recent records, not the full pre-2018 archive, so a one-off check confirms broad ownership shape without the deep lookback the paid tiers unlock.

The volume path: API and bulk download

Screening names at scale is a different problem. An investor checking a list of dropped domains, or an SEO vetting a backlink-acquisition target set, needs the API to query in bulk and, for offline work, a database download. WhoisXML API publishes quarterly database releases alongside its API. Whoxy’s API returns XML and JSON and prices down to a 1 USD CPM in bulk, the cheapest at volume. WhoisFreaks deduplicates and updates monthly, storing a new record only when the WHOIS data genuinely changed, which keeps the dataset lean.

Freshness varies. A monthly or quarterly update cycle means a recent ownership change can take weeks to appear, so none of these archives is a real-time feed. For the historical question they answer, which is who owned a domain in the past, that lag is irrelevant.

Which WHOIS history service fits which job

The right WHOIS history service follows the job, not a ranking. A domain investor vetting acquisitions, an SEO running due diligence, a brand-protection team, an OSINT investigator, and a person making one free check each have a different ideal tool. Matching the profile to the archive avoids paying for a subscription a single lookup never needed, or trusting a free tool with a decision that warranted the deep archive.

The five buyer profiles

Each profile is defined by depth of lookback, query volume, and budget. The investor and the SEO overlap heavily, since both read history to judge whether a name is safe to build on, and both benefit from the deepest archive that fits the budget.

The criteria that actually decide it

Three questions resolve the choice for almost every profile, in order of weight:

• How far back does the answer need to reach? If the pre-2018 owner is the point, the archive start year is decisive, and DomainTools or WhoisFreaks lead.
• One domain or a list? A single name suits a free or capped tier; a screening list needs the API and bulk pricing, where Whoxy is cheapest at volume.
• Is the record evidence? A legal or brand matter favours the recognised investigator source, which is where DomainTools holds its reputation.

Run those three questions against the comparison in Figure 3 and the answer is rarely ambiguous. The mistake is choosing on the headline record count, which is the one figure that says least about whether the specific record needed is in the archive.

ICANN Lookup and the current-versus-historical mix-up

ICANN Lookup is the official registration-data service, and it ranks for WHOIS history searches, but it returns current data only, with no history. Searchers reach for it expecting a past-ownership answer and find a present-state record. Knowing the line between the authoritative current lookup and a commercial history archive prevents the single likeliest wasted search in this field.

What ICANN Lookup is, and is not

ICANN Lookup, at lookup.icann.org, is the registry-fed service that returns the current registration record for a domain, now drawing on RDAP. It is authoritative, free, and the correct starting point for who holds a domain today, including registrar, status codes, and dates. The status codes it returns, and how to read them, sit alongside the WHOIS protocol in WHOIS: protocol and how to read the data.

What it is not is an archive. It holds no past snapshots, so it cannot answer who owned a domain before the present registrant. A query against it returns one record, the live one, and that is the source of the confusion: a tool ranking for history searches that, by design, has no history to give.

The practical rule is to use ICANN Lookup to confirm the present state and registry status, then move to a history service for anything about the past. The redaction that GDPR introduced applies to that live ICANN record too, which is the deeper reason the pre-2018 commercial archives carry information the official current lookup no longer can. The privacy mechanics behind that redaction are covered in GDPR impact on WHOIS.

How to run a WHOIS history lookup, step by step

A WHOIS history lookup runs in five steps: confirm the current record at the registry, choose an archive on start-year and volume, query the domain, read the ownership-change timeline, and cross-check the findings. Each step has a common misread that turns a clean record into a wrong conclusion, listed alongside it so the procedure produces a defensible answer, not a guess.

The consolidated misreads checklist

The mistakes above collapse into one short reference. Each is a way a correct record produces a wrong conclusion, and each has a fix that comes down to reading more of the archive, or reading it against a second source.

Reading a domain’s WHOIS history before acquiring it

WHOIS history is read, in the end, to answer one question: is this domain safe to own. Ownership continuity, registration churn, and prior-owner red flags decide whether an aged or expired domain is a clean asset or a liability. That diligence is the same screening SEO Domains runs on the curated aged and expired domains in its marketplace, so a listed name arrives already vetted.

What the history tells an acquirer

A WHOIS history read for acquisition looks for three things. Continuity, a name held by one operator over a long span, signals a genuine entity, not a recycled shell. Churn, repeated registrant and registrar changes with registration gaps, signals a name that was flipped or abandoned. Red flags, a switch to privacy right before a drop or a prior owner tied to spam, signal a history to verify before building anything on the name.

None of this is read in isolation. A WHOIS history pairs with the archived content record and the backlink profile, since a clean registration timeline on a domain that once hosted spam is only part of the picture. The metrics that complete that read sit in the Domain Authority & Metrics hub, and the acquisition diligence around expiry and drops sits in the Expired Domain Fundamentals hub.

Where the diligence is already done

The WHOIS history read is the manual version of what a curated marketplace does at scale. Reading registration history, checking ownership continuity, and screening for prior-owner red flags across a catalogue is exactly the work SEO Domains performs before a domain is listed and priced. A buyer sourcing from screened inventory starts from a name whose past has been read, not from an unvetted drop list where the history is the buyer’s own problem to chase.

The honest position on the tools is that they are a means, not the end. A WHOIS history service answers who owned a domain before. The reason that matters is the acquisition decision it feeds, and the cleanest way to act on a clean history is to own the domain openly and build something real on it. That is the product behind every WHOIS history search: access to aged and expired domains whose past has been read.