Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Browser forensics reconstructs what someone searched for, visited, downloaded, and typed, using the SQLite databases, caches, and session files that Chrome, Firefox, Edge, and Safari leave behind.

What Is Browser Forensics?
Almost every investigation reaches the browser eventually. Phishing starts there, data leaves through a webmail upload, a malicious extension harvests session cookies, and an insider researches a competitor three weeks before resigning. Browser forensics is the discipline of reading the files a browser writes to disk and turning them into a defensible account of what the user did and when.
Chrome, Edge, Brave, and Opera all share the same storage layout, which makes one skill set cover most of the estate. Under the user’s profile directory you will find History, a SQLite database whose urls, visits, and downloads tables carry the bulk of the evidence. The visits table is the one that repays attention: it records transition types, so you can distinguish a typed address from a link click, a redirect, or a form submission, and it links visits into chains that reveal how a user reached a page.
Around it sit Login Data for saved credentials, Web Data for autofill entries, Cookies, Favicons, and the Sessions folder holding the tabs that were open when the browser last closed. Cookie values are encrypted with a key held in Local State and protected by the Windows Data Protection API, so they can be decrypted only in the user’s context — which is also why cookie theft malware runs as the user rather than as SYSTEM.
Firefox keeps history in places.sqlite, splitting pages across moz_places and individual visits across moz_historyvisits, with downloads recorded as annotations. Session data lives in sessionstore-backups as mozlz4-compressed JSON, which is a reliable source of recently open tabs and form content. Safari uses History.db plus Downloads.plist, and macOS property lists hold a surprising amount of context including the last session and tab snapshots.
Each family uses a different epoch, and this is where reports go wrong. Chromium counts microseconds since 1 January 1601, Firefox counts microseconds since 1 January 1970, and Safari counts seconds since 1 January 2001. A parser pointed at the wrong column type will produce dates that look plausible and are decades out, so verify a handful of conversions by hand against a known event before relying on a timeline.
Incognito and private windows avoid writing to the history database, but they do not avoid writing at all. Traces turn up in the operating system DNS cache while the machine stays up, in the page file and hibernation file, in memory captured during live acquisition, and in the browser’s own temporary cache entries that are not always cleaned on exit. In corporate environments the proxy, DNS resolver, or secure web gateway log usually settles the question regardless of what the endpoint retains.
Hindsight is the standard open-source parser for Chromium browsers and produces a correlated timeline across history, cookies, cache, and preferences. Autopsy and the major commercial suites cover all four families. Whatever the tool, copy the -wal and -shm files alongside each SQLite database: a browser that was closed uncleanly can hold hours of the most recent activity in the write-ahead log, and a database opened without it will silently omit those rows. Deleted history entries frequently persist in free pages, so recovering deleted SQLite records should be part of the workflow rather than an afterthought.
Remember that the profile on the endpoint may not be the whole story. Signed-in browser profiles synchronise history, bookmarks, and passwords to the vendor’s cloud, so a user who wipes a laptop can restore the evidence on the next device. Where the account belongs to the organisation, that cloud copy is obtainable.
Browser artefacts show activity, not intent, and they show it at the level of a profile rather than a person. A shared machine, an unlocked workstation, or malware operating in the user’s session can all produce the same rows. Corroborate with authentication logs, physical access records, and endpoint telemetry before attributing behaviour to an individual, and set out the limits plainly in the report. At Privia Security, we build browser timelines as part of our digital forensic incident response services, usually alongside email and endpoint evidence rather than on their own.
Often, partly. Clearing history deletes rows from the SQLite database, but the records frequently survive in free pages until the file is vacuumed, and the write-ahead log can hold recent entries. Cache files, favicons, session restore data, and the operating system DNS cache may also retain evidence. A corporate proxy or DNS log is usually the most complete source of all.
It defeats the easy part. Private sessions do not write to the history database, so the usual parsers return nothing, but memory, the page file, and temporary cache entries can still hold URLs and page content. Network-level logging is unaffected, which is why gateway and DNS records are the first place to look when a user is known to browse privately.
Downloads and the visit transition data. The downloads table records the source URL, the local path, and the time, which ties a malicious file on disk to the page that delivered it. Transition types then show whether the user typed the address, clicked a link in an email, or was redirected, which distinguishes a phishing click from deliberate retrieval of a tool.
Yes, whenever one exists. SQLite write-ahead logging means committed changes can sit outside the main database file until a checkpoint. Copying only the database can lose the most recent hours of activity and, worse, produce a timeline that confidently ends before the event you are investigating. Collect the database and its companion files together and hash all three.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.