Microsoft Exchange stores mailbox data in EDB files managed by the Extensible Storage Engine. These databases hold messages, folders, and indexing, while transaction logs track changes. Knowing how EDB files differ from Outlook PST stores helps make sense of email evidence during digital investigations.

Multiple Choice

Which file extension is used to store Exchange mailbox databases?

Exchange stores its mailbox data in a database file created by the Extensible Storage Engine, and that file uses the .edb extension. This .edb file contains the actual mailbox data, including messages, folders, and indexing, and is managed by the server along with its transaction logs. The other extensions represent different mail systems or local client stores: .pst is a personal storage file used by Outlook on the client side, not the server mailbox store; .mbox is used by various Unix/macOS mail applications; .dbx comes from Outlook Express. Therefore, the .edb file is the correct designation for Exchange mailbox databases.

An Exchange mailbox database is stored in a file with the .edb extension. That small suffix points to a substantial store of information: email messages, folders, calendar items, contacts, and other mailbox content managed by Microsoft Exchange. For digital investigators, recognizing the file is useful—but understanding how it fits into the server’s storage system matters just as much.

Exchange database files are built with the Extensible Storage Engine, or ESE, a database technology designed to manage large sets of structured data. An EDB file is not simply a pile of message documents. It organizes records and supporting information so Exchange can retrieve and update mailbox content. Think of it as a carefully indexed archive, rather than a folder full of separate email files.

What an EDB file contains

An Exchange database may hold data for many mailboxes. Inside it, messages are stored alongside folders, attachments, calendar entries, contacts, and other mailbox items. The database also maintains structures that help the server locate and manage that information.

This has an important forensic consequence: an EDB file can contain more than what a user sees in a mail application. Deleted items, remnants of older data, and records connected to mailbox activity may remain in the file, depending on how Exchange has handled them and whether the space has since been reused. A message missing from a visible folder, for instance, may still leave traces in database pages or related logs.

That doesn’t mean every deleted message can be recovered. Results depend on many factors, including the Exchange version, database activity, retention settings, and the time elapsed since deletion. Still, the EDB is often a key source when investigating mailbox content or reconstructing events.

The database doesn’t work alone

Exchange manages EDB databases with transaction logs. These log files record changes made to the database, such as the arrival of a message or a change to a mailbox item. In broad terms, the EDB holds the database’s structured state, while transaction logs capture changes that may not yet have been written into the main database file.

This relationship matters during analysis. Logs can help explain what happened around a particular time, and they may contain changes relevant to database recovery. But an investigator should not treat a log as a simple, readable diary. Its contents are structured and tied to the database system. Handling the EDB without its associated logs—or mixing files from different points in time—can complicate interpretation.

A useful comparison is a notebook and a stack of change slips. The notebook represents the database; the slips record updates that still need to be incorporated or accounted for. The analogy isn’t perfect, but it captures why collecting the surrounding files can matter as much as collecting the main EDB.

EDB is not the same as PST

The .pst extension is also associated with Outlook, which can make the two formats easy to confuse. A PST file is generally a personal storage file used by Outlook on a computer. It can contain email and other Outlook items, but it is not the standard server mailbox database used by Exchange.

That distinction can help an investigator understand where a file came from. A PST may have been created for local storage, export, archiving, or transfer. An EDB, by contrast, is associated with an Exchange database and may serve many mailboxes. The file extension is a clue, not proof of origin: names can be changed, files can be copied, and a single extension never tells the whole story. Context and validation still matter.

Two other extensions sometimes enter the conversation. .mbox is a mailbox format used by a range of Unix and macOS email programs; it commonly stores messages in a text-oriented file structure. .dbx is associated with Outlook Express, an older Microsoft email client. Neither is the standard extension for an Exchange mailbox database.

These formats reflect different software histories and storage designs. It’s a little like seeing different kinds of containers in a warehouse: they may all hold mail, but they were built for different systems and don’t open in the same way.

Why the extension matters in an investigation

File identification is one of the first steps in digital forensics. When an investigator finds a large file named with an EDB extension, that information can guide the next steps: confirm the file type, preserve the original, identify related logs, and determine which Exchange version or database environment may be involved.

The extension alone should not be treated as conclusive evidence. A file could be renamed, damaged, or incomplete. Investigators commonly inspect file signatures and metadata, compare the file with known formats, and record its location and surrounding directory structure. If the file came from a server, the server’s configuration and related evidence may help establish which database it belongs to.

Preservation is equally important. A forensic copy should be made and verified before analysis begins, with the original kept unchanged whenever possible. Hash values can help show that a collected copy has not changed during handling. Documentation should record where the file was found, how it was acquired, which related files were present, and any tools or conversion steps used.

This may sound procedural, but it has a human side. Email evidence can affect people’s reputations, employment, and privacy. A careful record of how data was handled helps others assess the findings and reduces the risk of drawing conclusions from a partial or altered collection.

Reading mailbox evidence with care

An EDB file can provide valuable information, but it does not tell a complete story by itself. A message’s presence may show that it was stored in a mailbox; it does not automatically establish who read it, who sent it, or whether the displayed content was understood in a particular way. Investigators need to consider timestamps, account activity, server logs, device artifacts, and other sources where available.

Time interpretation deserves special care. Email systems may record different kinds of timestamps, and time zones or clock settings can affect how events appear. A message date shown in a client may not answer every question about when data was created, delivered, moved, or deleted. Correlating records from multiple sources can help clarify the sequence.

There are also practical limits. Large databases may take time to inspect, and damaged files may require specialized recovery methods. Some material may be encrypted, incomplete, or unavailable because logs have rolled over or database space has been reused. A sound report should distinguish what the evidence shows from what remains uncertain.

A small extension with a big role

The .edb extension identifies the database format commonly used for Exchange mailbox data. It separates that server-side store from Outlook’s PST files, MBOX mailboxes used by other email applications, and the older DBX format associated with Outlook Express.

For investigators, that distinction is more than a naming detail. It helps guide collection, preservation, and analysis—and it points toward the related logs and system context that may be needed to understand mailbox activity. The extension is the first clue. The careful work begins with confirming what the file is, preserving it properly, and interpreting its contents in context.