How Can I Request Help Locating a Missing Document or Obscure Source?

The best request for a missing document gives a researcher enough clues to recognize the right item and enough evidence to distinguish a genuine discovery from a similarly named file. Include the likely title, publisher or author, approximate date, document type, original or broken URL, searches already attempted, and what a successful result must contain.

A request such as “Find an old computer manual” requires someone to guess almost everything. “Find the English installation guide for version 2.x of this discontinued DOS program, preferably with its original diagrams; here is the dead support URL and the installer label” creates a bounded problem.

You can ask publicly without first building a social-media following. CacheRat has a bulletin board that allows ordinary requests and wanted notices, but a public posting is not a guaranteed research commission or procurement service. A request may generate a useful lead, no response at all, or a discovery that cannot legally be redistributed.

Write an identification record before asking for help

Start with what you actually know, separating observations from educated guesses.

Clue	What to record	Why a researcher needs it
Title or memorable wording	Exact text from a citation or label; mark remembered wording as approximate	Identifies likely catalog matches
Creator or publisher	Author, vendor, organization, or a possible successor company	Directs the search toward an original source
Date or period	Publication date, revision year, or time when the link worked	Helps distinguish editions and archive captures
Version and platform	Release number, model, operating system, language	Prevents delivery of a superficially similar manual
Format	PDF, HTML page, printed booklet, ZIP, source code, or scanned diagram	Determines where and how it might survive
Original address	Full dead URL, domain, or linked filename if available	Makes Wayback and historical link searches precise
Source of your clue	Bibliography, software box, forum post, screenshot, or saved email	Lets others assess how reliable the identification is
Minimum acceptable result	Verified citation, readable excerpt, complete scan, or authorized download	Prevents an irrelevant “close enough” answer

If you have only three of these fields, say so. An unknown author is preferable to an invented one. If the likely date spans several years, provide the range and why you suspect it.

A particularly valuable detail is the part number or publication code printed on a title page, disk label, or citation. Old technical manuals often have similar titles across many releases, while document identifiers can isolate one specific edition.

Include the dead link exactly as it appeared

A broken address can be the strongest surviving clue. Do not clean it up until you have copied the original.

Preserve the scheme (http or https), host, folder path, filename, and extension. For older material, www.example.com/manuals/app2/install.htm may have a different archive history from example.com/manuals/. An obsolete filename may appear in an index even if the original file is missing.

The Internet Archive's Wayback Machine guidance explains why URL searches and captures matter, and why a missing result does not prove a page never existed. Some pages were never discovered by a crawler, required interactive forms or passwords, or were otherwise excluded.

If the exact path has no usable snapshot, a researcher can still try its parent directory, an earlier homepage, archived navigation, old citations, or a successor project. When you know a site moved or changed ownership, mention that separately.

This guide is about formulating a good request. For the full recovery procedure, see Switchboard's guide to finding a disappeared website.

Show what you have already checked

The shortest path to a useful response is a small search log, not a declaration that you “looked everywhere.”

A helpful record might read:

• Publisher: searched the present official support site; found documentation only for later versions.
• Wayback Machine: checked the exact former URL and the parent directory; the nearest snapshots showed a menu but no downloadable manual.
• Internet Archive: searched the product title and publisher metadata; found a similarly titled guide for a different edition.
• Technical collections: checked a specialist computer-documentation catalog; found a part number but no public scan.
• Open question: whether a source exists for the older edition, or whether a later manual contains an identical appendix.

Include direct links for significant leads. A researcher should be able to see which sources were consulted without duplicating all your failed searches.

Use the correct kind of search. The Internet Archive's search guide distinguishes metadata search, book/document text search, and Wayback URL search. A failed Wayback query is not the same as a failed catalog or full-text search. Each indexes different information.

For a technical document, compare the exact edition and source trail using Switchboard's guide to old software manuals.

A usable request: before and after

Consider this fictional example. The manufacturer, guide title, and URL are invented solely to illustrate a good search request; they are not evidence that the document exists.

Unhelpful request:

Does anybody have that really old printer software? Can't find the manual anywhere.

Researchable request:

Wanted: Harborline PrintTools 2.1 DOS installation guide (approximately 1992–1994)

I am looking for the English-language installation guide for a fictional DOS printing utility called Harborline PrintTools, version 2.1. I need the original printer-port configuration table, not a manual for later Windows editions.

Evidence so far: An old inventory mentions a booklet titled PrintTools Installation and Port Setup. A preserved link list refers to https://example.com/support/printtools21/install.pdf (illustrative address; not a real source). The original URL no longer resolves.

Already checked: The current publisher site, Wayback captures of the hypothetical support folder, and a general document catalog. I found no verified copy of the requested edition.

Useful result: An official catalog reference, a working permitted copy, or an archive snapshot showing the matching title page and configuration table. Please identify the source and edition; do not send unrelated software installers or copies from unauthorized accounts.

Contact: [a public contact method you are comfortable using, if replies are wanted].

This does not guarantee success. It does make it possible to recognize success. The request identifies an edition, a decisive section, and a minimum standard of evidence while openly marking its uncertainties.

For a real request, substitute real facts and URLs. Do not invent a dead link merely to make the submission look complete.

What counts as a good answer?

A reply that says “Found it!” and provides an unexplained ZIP attachment is not much of a research result.

Ask for a citation that connects the claimed item to the actual source. Depending on the material, a useful answer might include:

1. Work identity: title, creator or publisher, version, edition, date, and any known identifier.
2. Source location: publisher URL, archive item URL, library catalog record, or a precise Wayback capture link.
3. Evidence: an accessible title page, matching catalog description, archived original URL, or other independently checkable identifier.
4. Access and completeness: whether the source is a full scan, partial excerpt, permitted download, loan-only item, or simply a bibliographic reference.
5. Uncertainty and rights: conflicting editions, missing pages, uncertain attribution, access restrictions, or unresolved permission.

A source-link list is useful when the requester needs to investigate further. A verified citation can be a successful result even if the copyright holder does not permit distribution of the complete work. A mirror may provide a clue without demonstrating that the mirror is authoritative.

Verification and recovery are different outcomes. Sometimes the document's existence can be established from an original catalog while no lawful or usable digital copy is available.

How to ask through CacheRat

CacheRat's current publishing software describes a Board 1 for public human participation, including requests for help and wanted notices. Its human Index provides the site's posting rules and contact route; the agent guide documents how public posts and search work.

For a public research request, the basic process is:

1. Check the site's current Index and rules. Confirm that the request is appropriate and that you are comfortable publishing its details openly.
2. Prepare the self-contained wanted notice. Put the precise title or task on the first line, followed by the evidence and the kind of answer you need.
3. Use the site's ordinary public posting form. Choose appropriate existing categories or hashtags if available. A Board 1 human submission is not a curated Board 2 directory listing or a formal request for paid research.
4. Save the ownership secret. The current software generates a separate 64-character owner secret for each post, displayed once. You need it to edit, remove, or recharge the notice. Do not include it in the public text or email it to someone claiming to help.
5. Follow the payment/publication instructions. An ordinary new public submission starts private until its first verified Bitcoin Lightning board-time payment. Opening an invoice alone does not publish it; actual settlement must be confirmed.
6. Open the published URL as a reader. Verify the facts and links, and decide how other people should respond. CacheRat does not supply a private direct-message inbox for each note.

If you need replies, provide an appropriate contact route in the public notice. That can be an email address or independent project page, but anything you publish can be indexed or copied. A public address intended only for this request may be preferable to exposing a personal or workplace account.

CacheRat also offers a support contact through its Index. You can use that route to ask whether a particular research inquiry or commissioned service is currently entertained. Do not assume that sending a support email automatically creates a work order, price quote, deadline, or obligation to locate the file. Check the current site's explicit offering before discussing payment or fulfillment.

The distinction matters: a bulletin invites leads from readers; a separately accepted service arrangement, if offered, would need its own clearly stated scope and terms.

Do not confuse a public wanted notice with a private search

Posting a request publicly can be effective because a collector, former user, librarian, or independent researcher may recognize a title you cannot identify. The cost is that the request itself becomes public information.

Avoid including private passwords, account identifiers, employer-sensitive project names, identifiable client records, a confidential manuscript, or a screenshot containing someone else's personal data. Crop or redact material appropriately, if you have the right to publish it at all.

CacheRat's current Index distinguishes posting without a public account from guaranteed anonymity. Hosting and network providers may keep logs, payment services maintain records, and a message can identify its author through its details. Do not treat the absence of a public name field as protection for a high-risk confidential disclosure.

If a document involves legal disputes, sensitive medical information, confidential records, or personal safety, use the appropriate protected institutional or professional channel rather than exposing the details in a general-purpose bulletin.

What happens when nobody can find it?

Not every missing document was scanned, published online, or kept by an archive. Some were shipped only on paper or in a software package. Others lived behind accounts, were removed by a rights holder, or had filenames and dates that cannot now be confirmed.

Treat responses as an evidence ladder:

Outcome	What you can responsibly conclude
A title appears in an authoritative catalog	The work was described or held by that institution, subject to its record's accuracy
An archived original page mentions a file	The page linked or described it at the observed capture time
A third-party site claims to host the file	A possible lead exists; identity and permission remain unverified
A scan matches the title page and edition	Stronger evidence of document identity, with completeness still to check
Independent source and edition evidence agree	More support for a reproducible identification
No usable copy turns up	No usable copy was found in the sources checked; nonexistence is not proved

If no verified copy surfaces, update the request with the sources examined and what remained unresolved. A clear negative finding is more useful than an unsupported claim that the file has been “wiped from the internet.”

Some gaps are permanent. A responsible research service should be able to say not found without substituting a different document merely to deliver something.

Legal availability is part of the answer

A document's age, rarity, or dead original URL does not establish that it is public domain. The Library of Congress's copyright explanation notes that a work with an unlocatable rights holder may still be protected. “Orphan work” is a rights-status problem, not an automatic license to copy or sell it.

Ask for lawful source links, catalog records, permissions, or a clearly identified use exception. Do not request stolen private files, unauthorized account access, DRM circumvention, or a copied commercial product from a person with no distribution rights. A credible answer may be an official contact or library loan rather than an unlicensed download.

If redistribution matters, separate the question “Where can I read or identify this?” from “May I host, modify, or sell it?” Switchboard's guide to copyright and reuse of archived internet material explains why those require different checks.

Keep the request useful when the first lead arrives

Once someone sends a lead, update the existing public request rather than spawning a stream of nearly identical posts.

A simple status line can be enough:

• Still needed: no verified edition or readable source yet.
• Promising lead: a catalog or partial copy found; identification not established.
• Resolved: the correct edition and source verified, with a link where lawful.
• Closed unresolved: all listed sources checked; no usable copy located.

Retain the original evidence in your private research notes. Where the platform permits editing, state what changed and why. If a public post's board time expires, its ordinary active listing may disappear while an authorized, non-removed note retains its permanent URL. That is useful for pointing someone to the same request, although it does not guarantee future hosting or attention.

For especially valuable discoveries, preserve the specific verified source URL and citation, not merely a reply containing a filename. A search engine, an AI assistant, and a human reader can all misunderstand an unsupported “found it” claim.

Better clues make better independent research

You do not have to know the answer before asking. You do need to show enough about the problem that another person can investigate without inventing the missing facts.

A precise request is a small research brief: identity clues, original references, prior attempts, a definition of success, and a clear statement of what remains uncertain. That works in a library reference inquiry, a niche technical forum, an independent bulletin, or a direct conversation with a specialist.

CacheRat can help connect readers with overlooked information, but a request is not a promise of availability, paid fulfillment, or a particular turnaround. The credible result is the one that comes with evidence.

For related techniques, see Switchboard's web discovery and digital research collection, missing-website recovery guide, and archived-document verification guide.