DomRecovery - Resurrect Websites from Wayback Machine
- Thread starter jimbobo2779
- Start date
- Jun 9, 2020
- 6,650
- 3,276
Interested. Can you send me the coupon?
- Sep 17, 2008
- 6,092
- 2,837
All requested coupon codes have been sent out. Sorry for the delay.
Thanks guys.
Thanks guys.
madeleineduncan
BANNED
- Mar 6, 2023
- 74
- 16
Any coupon
- Sep 17, 2008
- 6,092
- 2,837
- Sep 17, 2008
- 6,092
- 2,837
Currently it is a Windows software. I have a whole new version ready for release, the new release will be out next month and then we will be working towards adding online recoveries.
- Sep 17, 2008
- 6,092
- 2,837
DomRecovery v2 Available Now
All existing owners of DomRecovery get this latest, all new version of DomRecovery v2 now at no extra chargeCheck out the launch video below and see it in action
Get your copy of DomRecovery now to get started right away.
- Sep 17, 2008
- 6,092
- 2,837
Use an old website as the starting point, not the finished product.
You don't have to choose between rebuilding an expired domain from a blank page and putting its old website back online unchanged.
My GordonWi.com rebuild walkthrough shows another approach: use the archive as reference, then create a fresh site with original content and a new design.
The workflow looks like this:
1. Inspect the domain's Wayback history and choose a useful snapshot. Check internal pages as well as the homepage.
2. Use DomRecovery to download the available archived pages and assets into a local folder. It can only recover what the archive has captured.
3. Give an AI coding agent that folder as reference, with a separate empty folder for the new website. Use the old URLs, navigation and subject coverage to help plan the new build.
4. Review the new content, facts, links and mobile layout before publishing the finished site.
DomRecovery handles the recovery. The AI-assisted redesign is a separate stage.
For this workflow, create new copy and visuals rather than republishing someone else's archived material. Only reuse material you own or have permission to publish.
The guide includes the folder setup, rebuilding instructions and an old-versus-new comparison:
See the full DomRecovery and AI rebuilding walkthrough
Already using DHG Pro? DomRecovery is included in your package.
You don't have to choose between rebuilding an expired domain from a blank page and putting its old website back online unchanged.
My GordonWi.com rebuild walkthrough shows another approach: use the archive as reference, then create a fresh site with original content and a new design.
The workflow looks like this:
1. Inspect the domain's Wayback history and choose a useful snapshot. Check internal pages as well as the homepage.
2. Use DomRecovery to download the available archived pages and assets into a local folder. It can only recover what the archive has captured.
3. Give an AI coding agent that folder as reference, with a separate empty folder for the new website. Use the old URLs, navigation and subject coverage to help plan the new build.
4. Review the new content, facts, links and mobile layout before publishing the finished site.
DomRecovery handles the recovery. The AI-assisted redesign is a separate stage.
For this workflow, create new copy and visuals rather than republishing someone else's archived material. Only reuse material you own or have permission to publish.
The guide includes the folder setup, rebuilding instructions and an old-versus-new comparison:
See the full DomRecovery and AI rebuilding walkthrough
Already using DHG Pro? DomRecovery is included in your package.
- Sep 17, 2008
- 6,092
- 2,837
The recovery is only the beginning.
Here's DomRecovery in a real project: recovering the archived site for GordonWi.com, then using that material as the reference for a fresh, AI-assisted rebuild.
Rather than another screenshot of the finished site, you can watch the process:
The distinction matters: DomRecovery recovers the available archived pages and assets; the AI-assisted redesign is a separate step. You can inspect the recovered site locally, understand its old structure and decide what a useful new version should contain.
For anyone who hasn't tried V2, the changes aren't just cosmetic. The multi-threaded engine downloads pages and assets in parallel, while the live dashboard shows what's happening. Retries and resume support help with interruptions, and the recovered output has its internal paths rewritten and Wayback toolbar removed.
That's the standalone lifetime licence - no monthly subscription and no bill for each additional site you recover.
Take a look at DomRecovery V2 and get lifetime access →
Already on DHG Pro? DomRecovery is included, so check your existing access before buying it separately.
Recovery depends on what Wayback captured. For a new public site, use original content or material you own or have permission to publish.
Here's DomRecovery in a real project: recovering the archived site for GordonWi.com, then using that material as the reference for a fresh, AI-assisted rebuild.
Rather than another screenshot of the finished site, you can watch the process:
The distinction matters: DomRecovery recovers the available archived pages and assets; the AI-assisted redesign is a separate step. You can inspect the recovered site locally, understand its old structure and decide what a useful new version should contain.
For anyone who hasn't tried V2, the changes aren't just cosmetic. The multi-threaded engine downloads pages and assets in parallel, while the live dashboard shows what's happening. Retries and resume support help with interruptions, and the recovered output has its internal paths rewritten and Wayback toolbar removed.
$97 once. Unlimited recoveries. Future updates included.
That's the standalone lifetime licence - no monthly subscription and no bill for each additional site you recover.
Take a look at DomRecovery V2 and get lifetime access →
Already on DHG Pro? DomRecovery is included, so check your existing access before buying it separately.
Recovery depends on what Wayback captured. For a new public site, use original content or material you own or have permission to publish.
- Sep 17, 2008
- 6,092
- 2,837
Suppose an old hosting account has been deleted, the website files have gone with it, and the backup you thought existed turns out not to be much of a backup.
Before rewriting every page from memory, check whether the Wayback Machine captured your site.
DomRecovery isn't only for expired-domain projects.
It can also help recover your own lost website. Give it a useful Wayback snapshot and it works through the available archived pages and assets, saving a local copy with rewritten internal paths and the archive toolbar removed.
Here's the important distinction:
For a brochure site or content project, recovering the available pages, navigation and design assets can give you a much better starting point than a blank folder. Inspect the local copy, repair anything missing and decide whether to restore it or use it as the reference for a fresh rebuild.
Recovery depends on what Wayback saved, so check a few internal pages as well as the homepage before choosing your snapshot.
See how DomRecovery turns an archive snapshot into a local website →
And once it's back, take a proper backup. Archive recovery is a fallback, not a backup plan.
Before rewriting every page from memory, check whether the Wayback Machine captured your site.
DomRecovery isn't only for expired-domain projects.
It can also help recover your own lost website. Give it a useful Wayback snapshot and it works through the available archived pages and assets, saving a local copy with rewritten internal paths and the archive toolbar removed.
Here's the important distinction:
| What you need back | What archive recovery can provide |
|---|---|
| Old pages and their content | Local copies of the public pages that were captured. |
| Images and styling | The supporting files available in the archive. |
| WordPress admin, database or customer orders | These need an actual backup. Public archived pages don't restore the backend. |
For a brochure site or content project, recovering the available pages, navigation and design assets can give you a much better starting point than a blank folder. Inspect the local copy, repair anything missing and decide whether to restore it or use it as the reference for a fresh rebuild.
Recovery depends on what Wayback saved, so check a few internal pages as well as the homepage before choosing your snapshot.
See how DomRecovery turns an archive snapshot into a local website →
And once it's back, take a proper backup. Archive recovery is a fallback, not a backup plan.
- Sep 17, 2008
- 6,092
- 2,837
Recover as many websites as you want.
One payment. $97. No per-site fee.
One payment. $97. No per-site fee.
If you work with expired domains regularly, paying every time you want to recover another archived website doesn't make much sense.
The standalone DomRecovery licence is $97 once.
There isn't a monthly subscription.
There isn't a recovery allowance.
There isn't another charge when you move on to the next domain.
You can recover unlimited sites with the licence.
V2 was rebuilt around making the recovery itself much easier to manage. Pages and assets can be downloaded concurrently, there's a live view of the recovery in progress, interrupted jobs can be resumed, and failed items can be retried.
The finished output is saved locally, with internal links and asset paths rewritten so you can actually inspect what was recovered rather than browsing everything through Wayback.
What DomRecovery is good at
✔ Recovering the public pages and assets Wayback actually captured
✔ Reconstructing internal links for local browsing
✔ Giving you reference material for rebuilding an expired domain
✔ Recovering archived copies of your own lost sites
What it cannot magically recover
✘ Files that were never archived
✘ A WordPress database or admin area from public Wayback pages
✘ Missing server-side code that the archive never received
Get the standalone DomRecovery lifetime licence for $97 →
DHG Pro users: don't buy it again. DomRecovery is already included with your Pro access.
- Sep 17, 2008
- 6,092
- 2,837
A failed download isn't always a missing file.
If a recovery finishes with a few missing images or pages, it's worth looking at why before writing the whole thing off. A file that was never archived and a request that temporarily failed are different problems, even though both can leave a gap in the recovered site.
DomRecovery V2 gives you a live view of the recovery, including pages, assets and failures, so you can see what needs attention. Retries help with temporary errors, while resume support lets you continue an interrupted job without starting the whole recovery again. That makes it easier to work through a difficult recovery rather than just being left with a folder of files and no clear idea of what happened.
There are limits, though. If Wayback never captured an image, retrying that same missing capture won't produce it. Public archived pages also aren't a backup of your database or server-side code. I'd check the recovered site locally, follow the main navigation and open a selection of internal pages before deciding what needs repairing or replacing. For an original rebuild, the recovered structure can still be useful even where some assets are missing.
The standalone licence is $97 once, with unlimited recoveries, so there isn't another recovery fee every time you move on to a different site. You can see DomRecovery V2 and get access here. DHG Pro users already have it included, so check your existing access before buying separately. Only republish recovered material you own or have permission to use.
If a recovery finishes with a few missing images or pages, it's worth looking at why before writing the whole thing off. A file that was never archived and a request that temporarily failed are different problems, even though both can leave a gap in the recovered site.
DomRecovery V2 gives you a live view of the recovery, including pages, assets and failures, so you can see what needs attention. Retries help with temporary errors, while resume support lets you continue an interrupted job without starting the whole recovery again. That makes it easier to work through a difficult recovery rather than just being left with a folder of files and no clear idea of what happened.
There are limits, though. If Wayback never captured an image, retrying that same missing capture won't produce it. Public archived pages also aren't a backup of your database or server-side code. I'd check the recovered site locally, follow the main navigation and open a selection of internal pages before deciding what needs repairing or replacing. For an original rebuild, the recovered structure can still be useful even where some assets are missing.
The standalone licence is $97 once, with unlimited recoveries, so there isn't another recovery fee every time you move on to a different site. You can see DomRecovery V2 and get access here. DHG Pro users already have it included, so check your existing access before buying separately. Only republish recovered material you own or have permission to use.
- Sep 17, 2008
- 6,092
- 2,837
There is a discount coupon for BHW users. The link in the first post has teh coupon inserted into the form but the discounted price isn't shown till you click through to the payment processor.
- Sep 17, 2008
- 6,092
- 2,837
Before redesigning an old site, look at the pages behind the homepage.
Suppose you're rebuilding a gardening domain and some of its surviving links point to an old rose-pruning guide. A smart new homepage doesn't replace that guide for someone following one of those links. Before changing the whole structure, I'd want to know what was at that address and whether the new site should cover the same subject.
This is another useful job for DomRecovery. Recover the available archived site, browse it locally and use the old navigation and page paths to understand how it was organised. Compare that with your backlink research and you can start planning the pages that deserve attention, rather than designing the homepage first and worrying about everything else afterwards.
If a historical URL still makes sense, you can keep that path and write a new, useful page for it. If the equivalent content belongs at a different address, map the old URL to that page with a permanent redirect. Where there isn't a relevant replacement, a proper 404 or 410 is better than sending every old address to an unrelated homepage. Those are decisions to make in the rebuild, not something to leave to chance when uploading the files.
I've covered the wider process in my archive-to-rebuild walkthrough. DomRecovery supplies the recovered reference material; you decide what belongs on the new site and create original content for it. Standalone DomRecovery access is here, and it's already included for DHG Pro customers.
Suppose you're rebuilding a gardening domain and some of its surviving links point to an old rose-pruning guide. A smart new homepage doesn't replace that guide for someone following one of those links. Before changing the whole structure, I'd want to know what was at that address and whether the new site should cover the same subject.
This is another useful job for DomRecovery. Recover the available archived site, browse it locally and use the old navigation and page paths to understand how it was organised. Compare that with your backlink research and you can start planning the pages that deserve attention, rather than designing the homepage first and worrying about everything else afterwards.
If a historical URL still makes sense, you can keep that path and write a new, useful page for it. If the equivalent content belongs at a different address, map the old URL to that page with a permanent redirect. Where there isn't a relevant replacement, a proper 404 or 410 is better than sending every old address to an unrelated homepage. Those are decisions to make in the rebuild, not something to leave to chance when uploading the files.
I've covered the wider process in my archive-to-rebuild walkthrough. DomRecovery supplies the recovered reference material; you decide what belongs on the new site and create original content for it. Standalone DomRecovery access is here, and it's already included for DHG Pro customers.
- Sep 17, 2008
- 6,092
- 2,837
If you can tell me how you would look if 1+b were the size of a chicken
- Sep 17, 2008
- 6,092
- 2,837
Recover the website, then bring it up to date.
An archived site can contain much more than the articles you wanted back. There may be an old phone number in the header, a contact form pointing at a long-gone service or an offer that expired years ago. Those details are easy to miss when the homepage looks right and you're keen to get the site online.
DomRecovery gives you a local copy of the available archived pages and assets to work through before publishing. You can inspect the recovered site, edit what needs changing and decide whether to restore your own material or use it as reference for a fresh build. Here's my V2 walkthrough showing the recovery itself:
Once you've got the files, I'd start with the information visitors might act on: contact details, prices, opening hours, forms and links to other services. Then check the recurring bits such as headers and footers, because one outdated detail there can appear across the whole site. For a new project, don't carry over the previous owner's staff details, testimonials or business claims as though they describe you.
That's a much more manageable starting point than reconstructing everything from memory or saving archived pages individually. DomRecovery collects the available content into a browsable local site, rewrites internal paths and removes the Wayback toolbar. You still review the output, and recovery depends on what the archive captured.
Standalone access is $97 once, with unlimited recoveries and future updates included. Get DomRecovery here, or use your existing access if you're on DHG Pro. Only publish recovered material you own or have permission to use.
An archived site can contain much more than the articles you wanted back. There may be an old phone number in the header, a contact form pointing at a long-gone service or an offer that expired years ago. Those details are easy to miss when the homepage looks right and you're keen to get the site online.
DomRecovery gives you a local copy of the available archived pages and assets to work through before publishing. You can inspect the recovered site, edit what needs changing and decide whether to restore your own material or use it as reference for a fresh build. Here's my V2 walkthrough showing the recovery itself:
Once you've got the files, I'd start with the information visitors might act on: contact details, prices, opening hours, forms and links to other services. Then check the recurring bits such as headers and footers, because one outdated detail there can appear across the whole site. For a new project, don't carry over the previous owner's staff details, testimonials or business claims as though they describe you.
That's a much more manageable starting point than reconstructing everything from memory or saving archived pages individually. DomRecovery collects the available content into a browsable local site, rewrites internal paths and removes the Wayback toolbar. You still review the output, and recovery depends on what the archive captured.
Standalone access is $97 once, with unlimited recoveries and future updates included. Get DomRecovery here, or use your existing access if you're on DHG Pro. Only publish recovered material you own or have permission to use.
