Forensic disk images
Full-disk and partition images from the acquisition tools your lab already runs.
Bloodhound ingests disk images, mobile extractions and logical collections, then parses, correlates and timelines the artifacts inside them so investigators can find what matters fast.
Bloodhound reads open and standard formats rather than locking your evidence behind a proprietary container. Originals are opened read-only and never modified, and all analysis runs against verified working copies.
Full-disk and partition images from the acquisition tools your lab already runs.
Handset evidence from backup, filesystem and logical acquisition workflows, encrypted backups included.
Scoped collections from consent searches, remote triage and enterprise DFIR work.
File carving recovers files. What an examiner usually needs is the record inside the file: the single message, the deleted call, the location fix that puts a handset on a particular street at 02:14.
SMS, MMS, RCS, iMessage and third-party app messaging, with threads, attachments, read state and participants intact.
Call logs with direction and duration, contact records, and the account identifiers that resolve several aliases back to one person.
GPS fixes, cell and Wi-Fi derived positions, significant locations, geotagged media, app-level location caches.
History, downloads, cookies, cache, search terms and bookmarks across the major browsers.
Images and video with EXIF, device attribution, capture times and edit history preserved.
SQLite, plist, protobuf, Realm and LevelDB stores parsed down to records, write-ahead logs and journals included.
Freelist, WAL and journal recovery, plus unallocated and slack-space carving. Recovered records are labelled as recovered, never mixed in with live data.
Account activity, installed applications, device configuration, power and connection events.
Every extracted record keeps its provenance: source item, file path, byte offset, and the version of the parser that produced it. When a finding is questioned two years later, that is what you go back to.
Every parsed artifact contributes events to a single chronology covering every device in the case. Filesystem timestamps, message sends, location fixes, app launches, power events and network connections all land on the same axis, normalised to one timezone, with the source attributed on each row.
Resolve people, numbers, accounts and devices into entities, then map how they connect. Weighted edges carry frequency and direction, and the cluster view tends to be where the intermediary nobody saved as a contact turns up.
Plot every position-bearing artifact on one map, reconstruct tracks, detect dwell locations, or scope a geofence around a time window to see which devices were inside it.
Import NSRL and agency hash sets to flag known material and suppress known-good system files. Fuzzy hashing catches near-duplicates that a byte-exact match misses.
Case status, custody integrity, parser progress and key findings in a single view. Integrity anomalies surface here first, which is considerably better than surfacing in a courtroom.
Navigate filesystems at speed, with preview, metadata inspection, hex view, and a jump straight to the parsed records that came out of any given file.
Threaded conversation view across channels and apps, with participant resolution and deleted records marked in sequence rather than listed separately.
Grid and detail review with duplicate collapsing, hash-set status, EXIF and device attribution, and category tagging for disclosure.
Keyword lists, regular expressions and entity search across every parsed record and the raw file content, with provenance retained on each hit.
Flag an event, a record, a file or a map track into a structured findings list that feeds the report builder directly.
The evidence inventory, hash manifest, methodology statement and custody appendix are all generated from the case itself rather than retyped from it, which removes an entire category of transcription error from the most scrutinised document you produce.
Evaluations run on your hardware, with your reference images, inside your network.