COMING SOON · Q1 2027 Planned releaseGet notified + 10% launch offer ↗
← Acorn overview

Acorn application guide

Browsing History

Browsing History brings recorded visits, searches and downloads into a reviewable view. Narrow the records by a relevant term or category, then inspect the page title, URL, time and source. The public Lone Wolf example makes that process visible with firearm-marketplace browsing records.

Demonstrated on public training data

Which recorded visits or searches are relevant to the examination?

Start with

  • Browser-history material from a public training scenario, including recorded downloads.

What you can take away

  • Visit and download review records with available path, time and size context.
A category filter shows 65 firearm-marketplace browsing records from 2,613 public Lone Wolf training records. Recorded times, page titles and source URLs stay together, with the selected entry expanded below. View full screen
A category filter shows 65 firearm-marketplace browsing records from 2,613 public Lone Wolf training records. Recorded times, page titles and source URLs stay together, with the selected entry expanded below.

Open the screenshot and choose “View actual size” to read the records at their original resolution.

Source: Digital Corpora’s public Lone Wolf teaching scenario. A browsing record does not establish a purchase, possession, intent or the person using the browser.

A practical starting point

How the workflow fits together.

  1. Find the visits or downloads relevant to the question and identify the browser source from which they were obtained.

  2. Inspect the page title, URL, recorded time and browser source. For a download, also check the destination path and available byte counts. Keep the recorded activity separate from assumptions about what happened next.

  3. Compare a material lead with the corresponding files and other available activity. Note where the evidence cannot establish completion, execution or the person responsible.

Evaluate the workflow

Questions worth bringing to a demonstration.

  • Which original browser record supports the displayed visit or download?
  • Can the example distinguish a recorded download from later installation or execution of the file?
  • What further evidence would be needed before attributing the recorded activity to a particular person?

Start with your requirements

Bring a sample question.

Ask us to demonstrate this workflow with suitable public or constructed material. Do not send confidential evidence in an initial enquiry.

Planned for Q1 2027

Be first to hear. Save 10% at launch.

Request Acorn launch news and details of the planned 10% offer. No deposit or purchase commitment.

Notify me at launch ↗

Launch-update requests go to the SQFR team for review. Final offer terms and product availability are still to be confirmed.

About the screenshots and illustrations

Application screens are selected from the September 2026 Acorn screenshot pack. Captions distinguish native setup views, constructed training records and public-corpus results. They are not private client cases, and a displayed control does not establish that every operation was completed.

Relevant public sources include DeepBlueCLI training event logs and Plaso test data. Check the relevant source terms before redistributing an underlying dataset.

Workspace scenes and sector mascot variants are generated illustrations. They do not show actual police, judicial, military or university deployments or endorsements. The original Squirrel Forensics identity is retained.

Zoom in, then scroll to inspect the detail.

Open full-resolution image ↗

A useful first conversation

Let’s look at your workflow.

Tell us what you examine, where you work and what you need to deliver.

Use the enquiry form to outline your role, intended use and potential order quantity. Do not send case material through a general enquiry.

Your enquiry goes to the SQFR team. Please do not include passwords or case evidence.