Forensic ArtifactWindows: Browser

Edge / IE WebCacheV01.dat

Legacy Edge and Internet Explorer store web cache, history, cookies, and download records in a single ESE database. Modern Edge (Chromium) uses Chrome-style artifacts.

Legacy Edge and Internet Explorer store browsing history, cached content, cookies, and download records in a single Extensible Storage Engine (ESE) database — WebCacheV01.dat. This monolithic artifact survives browser history clearing, contains URL access timestamps with second-level precision, and records web activity from Windows system components that use WinINet/WinHTTP.

What Is WebCacheV01.dat?

WebCacheV01.dat is an ESE database used by Internet Explorer 10+, Legacy Edge (EdgeHTML), and Windows system components to store web cache metadata, browsing history, cookies, and download records. It uses the same database engine as Active Directory (ntds.dit), SRUM (SRUM.db), and Exchange Server. The database is locked by taskhostw.exe on a live system.

Unlike modern Chromium-based Edge (which uses Chrome-style SQLite databases), the legacy web cache stores everything in a single ESE database with multiple container tables. Each container has a ContainerId mapping to a specific data type. The database also stores cache entries for Windows components that use WinINet or WinHTTP: Windows Update, Office activation, Cortana, and Store apps all write entries, making it a surprisingly broad artifact.

Key Insight

WebCacheV01.dat records data from IE, Legacy Edge, AND Windows system components that use WinINet/WinHTTP. Entries may reveal Windows Update checks, Office activation calls, and Store app downloads — even if the user never opened a browser.

Location & Format

FilePathNotes
WebCacheV01.datC:\Users\{user}\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.datPrimary ESE database; locked by taskhostw.exe
Transaction logsV01*.log in same directoryESE transaction logs; may contain uncommitted data
Modern EdgeAppData\Local\Microsoft\Edge\User Data\Default\HistoryChromium Edge uses SQLite; completely separate

Container Structure

ContainerContentKey Columns
HistoryURLs with access counts and timestampsUrl, AccessCount, AccessedTime, ModifiedTime
ContentCached web content metadataUrl, Filename, FileSize, AccessedTime
CookiesCookie entries with domain and expiryUrl, CookieName, AccessedTime
iedownloadDownload historyUrl, Filename, AccessedTime
MSHist###Daily history partitionsDate range encoded in container name
Format Note

Timestamps are Windows FILETIME (100-nanosecond intervals since January 1, 1601 UTC). The MSHist container names encode date ranges as MSHist01YYYYMMDDYYYYMMDD, making it easy to identify which partition contains relevant data.

What It Reveals

Forensic Use Cases

1. Corporate Policy Violation

An employee uses IE to access personal webmail to exfiltrate documents as attachments. WebCacheV01.dat records every visit to the webmail domain with exact timestamps. The iedownload container may show files downloaded from the corporate intranet immediately before the webmail visits.

2. Malware Delivery Reconstruction

A drive-by download attack delivered malware through a compromised website. WebCacheV01.dat preserves the full URL chain: the initial page, the injected iframe, the exploit kit landing page, and the payload download URL, each with an independent timestamp.

3. Legacy System Investigation

Many enterprise environments still run IE11 for legacy intranet applications. WebCacheV01.dat is often the only browser artifact available on these systems, making it critical for investigations involving older infrastructure.

4. Windows Component Activity

Beyond browser usage, WebCacheV01.dat reveals when Windows Update checked for patches, when Office made activation calls, and when Store apps were downloaded — establishing whether the system was patched at the time of compromise.

5. History Recovery After Clearing

The user clears browsing history through IE settings. The ESE database marks records as deleted but does not overwrite pages. ESE-aware recovery tools can extract deleted entries from free pages.

Acquisition Methods

Collection Warning

WebCacheV01.dat is locked by taskhostw.exe on a live system. Use VSS, KAPE, or raw-disk copy. Always collect V01*.log transaction logs. Run esentutl /r V01 /d before parsing to replay uncommitted transactions.

CMD / ADMIN
:: Using KAPE
kape.exe --tsource C: --tdest C:\Evidence\KAPE_Output --target WebCache

:: Using VSS to bypass file lock
vssadmin create shadow /for=C:
copy \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy3\Users\jdoe\AppData\Local\Microsoft\Windows\WebCache\* C:\Evidence\WebCache\

:: Repair dirty database before parsing
esentutl /r V01 /d /l C:\Evidence\WebCache\ /s C:\Evidence\WebCache\

Parsing Tools & Analysis

ToolAuthorLicenseNotes
ESEDatabaseViewNirSoftFreewareGUI ESE viewer; browse containers and export to CSV/HTML
libesedbJoachim MetzOpen sourceLinux-native; esedbexport extracts all tables to CSV
BrowsingHistoryViewNirSoftFreewareParses history containers from WebCacheV01.dat
HindsightObsidian ForensicsOpen sourceMulti-browser parser with WebCache support
X-Ways ForensicsX-WaysCommercialNative ESE parsing with WebCache analysis

Retention & Persistence

PropertyDetails
History retentionDefault 20 days for IE; configurable via Group Policy
Cache retentionSpace-limited; oldest entries evicted when size exceeded
Survives history clearingPartially — ESE free pages may retain deleted records
Survives rebootYes — on-disk ESE database
Modern Edge coexistenceWebCacheV01.dat persists alongside Chromium Edge data

Version Differences

BrowserDatabaseFormatNotes
IE 10+WebCacheV01.datESEFull history, cache, cookies, downloads
IE 9 and earlierindex.datBinaryLegacy; separate file per content type
Legacy EdgeWebCacheV01.datESEShares database with IE
Chromium EdgeHistory, CookiesSQLiteChrome-style; completely separate

Anti-Forensics Resilience

ActionEffectRecovery
Clear browsing historyMarks records as deleted in ESEFree-page carving may recover entries
CCleanerClears containers; may compact databaseLimited if compacted; disk-level carving possible
InPrivate browsingSome entries may leak in certain IE versionsCheck containers for InPrivate remnants
Manual deletionRequires stopping taskhostw.exeFile carving; $MFT entry persists

MITRE ATT&CK Detection Mapping

TechniqueNameWebCache Evidence
T1071.001 T1071.001Web ProtocolsHistory for C2 panel or webshell URLs
T1189 T1189Drive-by CompromiseURL chain through exploit kit pages
T1567 T1567Exfiltration Over Web ServiceHistory for cloud storage upload pages
T1070.003 T1070.003Clear Command HistoryCleared history recoverable from free pages

Related Artifacts & Cross-References

ArtifactRelationshipCross-Correlation Value
Chromium Edge HistoryModern Edge data alongside legacy WebCacheBoth may contain data on Win10/11
SRUM.dbBrowser network transfer volumesCorrelates browsing with network usage
DNS CacheResolved domains for visited URLsConfirms activity if history cleared
Typed URLs RegistryNTUSER.DAT\Software\Microsoft\IE\TypedURLsIndependent record of typed URLs
Proxy/Firewall LogsNetwork-level connectionsIndependent confirmation with timestamps

References

  1. NirSoft, “ESEDatabaseView” — nirsoft.net
  2. Joachim Metz, “libesedb” — github.com/libyal/libesedb
  3. SANS Institute, “IE and Edge Forensics” — sans.org
  4. Obsidian Forensics, “Hindsight” — github.com
  5. Microsoft, “ESE Database Engine” — learn.microsoft.com

Mjolnir Security — Digital Forensics & Incident Response

Mjolnir Security provides 24/7 incident response, digital forensics, and expert witness testimony. Our DFIR team specializes in ESE database analysis, browser forensics, and web activity reconstruction.

Digital ForensicsIncident ResponseExpert WitnessBrowser ForensicsESE AnalysisWeb Activity

mjolnirsecurity.com — 24/7: +1 833 403 5875