Browser Secrets Unveiled!

by Chetan Gupta, NII Consulting

Everyday millions of people surf the web using popular web browsers such as Microsoft Internet Explorer (IE) or any one from the Firefox/Mozilla/Netscape family. A very important step in computer forensics is investigating the web usage of the suspect. This information is useful in everything from examining company policy violation to detecting corporate espionage. Examining a suspect’s web browsing history could provide critical clues to solving the case.

Each of these browsers saves the web browsing activity in their own unique formats. The Internet activity data related to a specific browser could be found in different locations according to the Operating System used by the suspect. In this article, we look at the various tools and techniques available for investigating one of the most widely used browsers: Internet Explorer.

Investigating Microsoft’s Internet Explorer (IE)

IE has been the default browser for Windows OS since Windows 95. IE has evolved to closely interact with the OS which opens various avenues for the forensics investigation. Even if the suspect deletes the history or clears the cache, the information can still be recovered to a great extent.

IE has three separate logging facilities that can be used to reconstruct the suspect’s web browsing activities. The logged information includes

1. History of visited URLs

The browser history creates an audit trail that shows the user’s browsing patterns on the web. In Windows XP, the files are stored in the following locations:

  • C:Documents and Settingsprofile_nameLocal SettingsHistoryHistory.IE5index.dat
  • C:Documents and Settingsprofile_nameLocal SettingsHistoryHistory.IE5MSHist01XXXXXXXXXXXXXXXXindex.dat. The MSHist files are of two types:
    1. Daily MSHist files (ie, MSHist011998100819981009index.dat — one day between yyyymmddyyyymmdd dates)
    2. Weekly MSHist files (ie, MSHist011998092819981005index.dat — one week between yyyymmddyyyymmdd dates)

2. Cookies

Cookies are small text files that the suspect’s browser accepted while browsing the web. The information held in these files can be invaluable to forensics. In Windows XP, the files are stored in the following location:
C:Documents and Settingsprofile_nameCookiesindex.dat
This audit trail in the index.dat is useful in locating cookies that are intentionally misnamed or obfuscated.

3. Temporary Internet Files

The Temporary Internet Files folder contains a copy of the files that constituted the web pages the suspect visited. The next time the web page is requested, only the sections of the page that have changed would be downloaded. In the cache directory, an index.dat maps the pages on the websites to files and directories in the cache. In Windows XP, the files are stored in the following locations:

  • C:Documents and Settingsprofile_nameLocal SettingsTemporary Internet FilesContent.IE5index.dat
  • C:Documents and Settingsprofile_nameUserDataindex.dat

The index.dat in the UserData folder holds information about automatic Windows accesses to the Internet such as Windows updates. Each of these facilities contains an important file called index.dat which is primarily a catalog file for the saved information. The index.dat files can catalog the URLs visited, the cookies accepted by the browser and locally cached files linked to the visited URLs.

Reconstructing IE History

The first place an investigator would start his investigation is by reviewing the URL history of the browser used by the suspect. The history files are located in the C:Documents and Settingsprofile_nameLocal SettingsHistoryHistory.IE5 directory. The directory History.IE5 when viewed in the browser shows the following files:

The index.dat file shown above contains the history information for the date of last access. There are different directories starting with MSHist01 followed by a string of numbers. This string of numbers actually represents the dates for which the file holds the history information. For example, the number 2005020320050210 means that the file holds the history information for the period between 2005-02-03 and 2005-02-10. Each MSHist01XXXXXXXXXXXXXXXX directory contains an index.dat file which contains history records for a specific period.

There are two ways of accessing the information contained in the history files:

  1. The easiest way to see the contents of browser history is by opening the IE browser and pressing Ctrl+H or select View tab -> Explorer Bar -> History
  2. Using a tool such as Pasco or any commercial tool such as Encase

Tool: Pasco

Pasco is an open source Web Browsing Investigation tool. Pasco examines the index.dat files which are populated when a suspect browses the Internet.

Here is a sample output in Excel format generated by running Pasco on the index.dat file:

Reconstructing Browser Cache

To speed up browsing of the Internet, IE caches most of the pages you visit on your hard drive. This is good news for Forensics investigators! In order to avoid confusion and collisions among the similarly named files (eg. index.html), Microsoft uses a naming system which allows the files to be stored in different randomly named directories and the catalog in the index.dat file allows the mapping between the filename and the associated directory where it can be found. Here is a sample output in excel format generated by running Pasco on the index.dat file

Let us look at a sample output from the index.dat file obtained by running the following command at the command prompt: C:Documents and SettingsCnXLocal SettingsTemporary Internet FilesContent.IE5 -> pasco.exe index.dat -> c:pasco_output.doc
We will have a look at the first entry and try to interpret it.

History File: index.dat

File Structure

URL Tue Dec 6 10:09:32 2005 Sat Dec 10 00:32:31 2005 bride06dec[1].gif 0DUDEX0X HTTP/1.1 200 OK Content-Length: 1758 Keep-Alive: timeout=10, max=100 Content-Type: image/gif Content-Language: en-US ~U:cnx


  1. The type is ‘URL’
  2. The URL visited was
  3. The date on which this entry was added to the cache is 6th December 2005 at 10:09:32 am in GMT format (Local time (India) is +5:30 GMT which is 03:39:32PM)
  4. The date on which this entry was last accessed from the cache is 10th December 2005 at 00:32:31 am in GMT format ( Local time (India) is +5:30 GMT which is 06:02:31AM)
  5. The file name is bride06dec[1].gif and the directory name where the file is stored is 0DUDEX0X
  6. The HTTP headers field holds important information about the context in which the file was retrieved.
  7. Using the file and directory fields, the file can be located.
  8. The file bride06dec[1].gif should be available under the directory 0DUDEX0X which is present in the directory “C:/Documents and Settings/CnX/Local Settings/Temporary Internet Files/Content.IE5”. This directory has folders with random obscure names and an index.dat file which we analyzed using the pasco utility.
  9. Using a hex viewer such as Winhex, we can view the index.dat file and at byte offset 0x80 begins a listing of directories on the suspect’s computer that contain the cache files. As we can see, 0DUDEX0X is the second directory present in the listing.
  10. The same procedure can be repeated until all files for a page are located which allows us to reconstruct the page completely that the user visited!

Investigating Cookies

The history file in the C:Documents and Settingsprofile_nameCookies directory is identical in structure to the main index.dat files but instead of URLs, it stores the history of the cookies. Pasco can be used to parse this index.dat file. Often the mere existence of a cookie is enough to show that a user was visiting the site.

To delve deeper into the user activity and look at the information inside an individual cookie, we can use a free tool available from Foundstone called Galleta.

Tool: Galleta (

Galleta is an open source IE Cookie Investigation tool developed by Keith Jones to translate the information inside a cookie.

General Tools

Let us have a peek at some tools which can greatly aid the investigator in reconstructing the web activities of a suspect.

  1. Tool: Web Historian ( Web Historian parses data from nearly any Web browser and comes as a native windows application. It was released by Red Cliff Consulting as a free tool and can parse cached information from a variety of browsers including IE and Mozilla.
  2. Tool: Encase ( Encase is a widely respected commercial tool that has a built-in functionality to examine a user’s Web browsing activity. Encase utilizes a script, referred to as an E-script, to parse the Web browsing information found in the evidence and present it to the investigator.


In this article, we have seen the various logging facilities available in the IE browser to track a suspect’s web usage. Correlating time frames from all three facilities can help the investigator a great deal in identifying and understanding the suspect’s activities on the web. In the second part of this article, we would look in detail at the tools and techniques available for Mozilla/Netscape/ Firefox browser forensics.


  5. Hacking Exposed – Computer Forensics
  6. Real Digital Forensics by Keith J Jones, Richard Bejtlich and Curtis W Rose

Lionel Faleiro

Lionel Faleiro

Cybersecurity Analyst & Trainer at Network Intelligence Inc
Photographer | Ex-Univ Professor | SysAdmin | Trainer, Security Analyst & DFIR Enthusiast |
Lionel Faleiro

Latest posts by Lionel Faleiro (see all)


  1. Very nicely explained, there are other more detailed documents in the ODESSA proyect page at sourceforge that complement very well your explanation.

    Thanks for the article.

  2. Nice work you have done. Last half an hour, I went through your first article and KK’s extortion thro DDoS and your browser article. After going through unveiling browser, I really learnt some good tweaks from this article. Nice work. About this DDoS article, I have to say that, these attacks are very common these days cos no one is really taking precautions before he is targetted. Moreover if that company is running EPortal for stocks or other things, then they should always choose port and open that port only and specifically they should never use 80 and 443… thats wht i think.Regards,
    Krishna Suryanarayanan

  3. In regards to your internet cache investigation, I would like to say that this article is very interesting. I like to add that NetAnalysis is also very good tool.I have personaly used NatAnalysis. Its very handy , easy to use and lots of option to investigate. Even the Hi-Tech Crime Units here in Uk use this tool.


  4. Can i have any information about IE Downloads in Xp.

    Where it stores that data,which index file i can process to get that information like URL,Downloaded path,downloaded file size,State of download etc..

  5. Very good website you have here but I was curious if you knew of any community
    forums that cover the same topics talked about here?
    I’d really love to be a part of community where I can get feed-back from other knowledgeable people that share the same interest.
    If you have any recommendations, please let me know. Thanks!

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.