DomRecovery 2026

The pages are still there. Just not in any order.

A web archive holds a site as thousands of separate captures with nothing joining them up. DomRecovery follows the links, pulls down the pages and assets together, and hands you a browsable local copy you can click through before deciding what deserves to go back online.

  • Included with DHG Pro
  • Rebuilt for 2026
  • Pages and assets together
  • Review locally first
Rebuilt for 2026 Multi-threaded recovery The DomRecovery 2026 workspace showing an archive recovery job in progress.

What a recovery run looks like

One snapshot in, a working site out

Point it at the version of the site you want back. DomRecovery then follows the links, fetches the pages and their assets across several workers at once, and rebuilds the folder structure as it goes. Press play to watch the shape of a run.

DomRecovery 2026 web.archive.org/web/20140312/oldsite.example snapshot 12 March 2014
Pages recovered 428 / 428
Assets recovered 1,963 / 1,963

8 workers

  • 01 index.html
  • 02 assets/css/main.css
  • 03 about/index.html
  • 04 assets/img/logo.png
  • 05 blog/index.html
  • 06 assets/js/site.js
  • 07 blog/2013/first-post.html
  • 08 assets/img/hero.jpg

An illustration of the workflow using an invented example site, not a real recovery.

Local output

  • oldsite.example/
  • index.html
  • about/
  • index.html
  • blog/
  • 2012/
  • 2013/
  • 2014/
  • services/
  • assets/
  • css/
  • img/
  • js/

Open it in a browser. Click around. Decide what stays.

The honest answer

What comes back, and what doesn't

Worth knowing before you start, because it decides whether a recovery is the right idea at all. For a content site the answer is usually yes. For a shop or a forum it usually is not.

Recovers

  • Pages and their structure The HTML the archive captured, with the links between pages followed and kept.
  • Stylesheets and layout CSS files where the crawler saved them, so the result looks like the site rather than plain text.
  • Images and media files Whatever assets were captured alongside the pages, pulled down in parallel.
  • Scripts as they were saved Client-side files, exactly as archived. Anything that called a server will not answer.
  • Text, copy and metadata The written content, which is usually the part actually worth recovering.

Does not

  • Databases Never captured. A forum, shop or CMS keeps its content in a database the archive never saw.
  • Anything behind a login Member areas, accounts and paywalled pages were not crawled, so they are not there.
  • Forms and server code Checkouts, search boxes and contact forms need a backend. You get the shape, not the function.
  • Pages the archive missed The Wayback Machine doesn't always have all pages, in these cases the pages may not be recoverable.
  • Your right to publish it The one nothing can supply. Being in an archive says nothing about who owns it.

Before anything else

An archive is a record. It is not a licence.

Finding a site in an archive tells you it existed. It tells you nothing about who owns the words, the photographs, the logo or the code, and it grants you no permission at all. Copyright does not lapse because a domain did.

  • Recover material you own, have licensed, or are otherwise entitled to use.
  • Buying a domain buys the domain. It does not buy the previous owner’s content.
  • Check for personal data before anything goes back online, not after.
  • Trademarks and brand assets stay with their owner regardless of what the archive holds.

Handled properly this is straightforward, and it is the difference between a restoration and a problem. If you are not sure where you stand, that is worth resolving first.

It comes with Pro

One account, the whole research stack

DomRecovery is included with DHG Pro rather than sold separately, which matters because recovery rarely stands on its own. The same subscription finds the names worth rebuilding, tells you whether the history suits your plan, and then puts the site back together.

  • DomRecovery archive rebuilding
  • The full domain discovery suite
  • Easy Expired Domains access
  • DomDetailer credit allocation

Prefer to read first? The written recovery guide walks through planning an archive-led rebuild end to end.

The route

Four steps, and the first one is not technical

The software handles the middle. The decisions at either end, whether you may and what should return, stay with you, which is exactly where they belong.

Read the written guide
  1. 01

    Establish that you may

    Ownership, a licence, or another sound basis. This is genuinely step one, not a box to tick afterwards, because everything downstream depends on it.

  2. 02

    Pick the right moment

    A site has many snapshots and they are not equal. Choose the capture that best represents the version you actually want back.

  3. 03

    Recover, then look properly

    The job runs and hands you a browsable local copy. Click through it like a visitor would. Gaps and oddities show up quickly that way.

  4. 04

    Edit before anything goes live

    Cut what should not return, update what has dated, and put only the approved result through your normal deployment.

See it properly

The rebuilt workflow, end to end

A short walkthrough of the 2026 release: choosing a snapshot, running the job, and opening the recovered project locally to see what actually came back.

Watch on YouTube

Who does this

Four reasons people rebuild a site

Getting your own site back

The backup that turned out not to be running, the host that closed, the migration that went wrong. This is the common one, and the least complicated.

Understanding what you bought

You acquired a domain with history. Seeing the site as it was tells you far more than a metrics panel about whether that history suits your plan.

Rescuing reference material

Guides and documentation that people still search for and still need, brought back where you hold the rights to do it.

Starting a relaunch from something

A recovered structure is a far better starting point than an empty folder, provided you treat it as a draft rather than a finished site.

Reasonable questions

The things people ask first

Including the two that matter most: what actually comes back, and whether you are allowed to use it.

Can it rebuild any archived website?

No, and be wary of anything that claims otherwise. Archive coverage is uneven and a snapshot never contains a database, a login area or any server-side code. What you get back is the captured pages, structure and assets, which for a content site is usually most of what mattered.

Does finding a site in an archive mean I can republish it?

No. An archive is a historical record. It transfers no copyright, no trademark, no ownership and no clearance for personal data. Publishing recovered material without a right to use it is an infringement whether or not the original site is still online.

What happens to forms, shops and member areas?

You recover how they looked, not how they worked. Anything that talked to a server needs rebuilding for real. That is normal, and often a good moment to replace something dated rather than restore it.

Which plan includes DomRecovery?

DomRecovery is included with Domain Hunter Gatherer Pro, alongside the discovery tools, Easy Expired Domains and the Pro DomDetailer credit allocation.

Is the recovery on this page a real job?

No. The console above is an illustration of the workflow using a made-up example site, so you can see the shape of a recovery run before installing anything. The counts and the file names are invented.

Still out there

Somebody archived it. You can put it back together.

DomRecovery comes with DHG Pro, alongside the discovery tools that find the names worth recovering in the first place.