I have multiple devices with near identical Chrome history due to the synchronisation tool, is anyone aware of a way to determine which device the web pages were physically viewed on?
The only way I can think of coming close would be to view last modified timestamps of all the history files from the devices, they should all be fairly close but possibly the device that originally viewed the web page would have a slightly older timestamp, that is assuming the sync isn't instant.
Other variables that make this not a great method is if the chrome account isn't always signed in on all devices so there may be disparity there.
There is a table in the 'History' SQLite database that Chrome stores data in called visit_source.
This table tracks where the page views ("visits") in the History file came from.
The following is from https://
// The enumeration of all possible sources of visits is listed below.
// The source will be propagated along with a URL or a visit item
// and eventually be stored in the history database,
// visit_source table specifically.
// Different from page transition types, they describe the origins of visits.
// (Warning) Please don't change any existing values while it is ok to add
// new values when needed.
enum VisitSource {
SOURCE_SYNCED = 0, // Synchronized from somewhere else.
SOURCE_BROWSED = 1, // User browsed.
SOURCE_EXTENSION = 2, // Added by an extension.
SOURCE_FIREFOX_IMPORTED = 3,
SOURCE_IE_IMPORTED = 4,
SOURCE_SAFARI_IMPORTED = 5,
};
One caveat to this is that Chrome doesn't store values of '1' in this table to be more efficient, as most visits are of this type. That means that on a system that doesn't have any synced or imported visits, the visit_source table will be empty.
Hindsight is an open source Chrome forensics tool (
Apologies for the late reply on this thread - I was searching the board for something else and found it.
The Forensic Browser for SQLite can help you create a nice simple report that decodes this field based on the information above.
All you need to do is add a series of aliases for the different values in the source field from the visit_type table
The following report was created using drag and drop query building with a further column conversion (right click column and select chrome date) for the visit-time column
If anyone would like a fully functional demo if the Forensic Toolkit for SQLite then please visit this link
http//