DAASINQ & eDAASINQ — DAAS Inquiry (Complete Reference)

The Defense Automatic Addressing System Inquiry tools — DAASINQ and its enhanced successor eDAASINQ — are the web-based windows into the reference data that moves DoD logistics. They are operated by DLA Transaction Services, the Defense Logistics Agency field activity that runs the Defense Automatic Addressing System (DAAS) itself. Where DAAS edits, validates, addresses, and routes the daily torrent of MILSTRIP, MILSTRAP, and DLMS transactions between trading partners, DAASINQ lets a human being look up the addressing and routing data behind that movement: a Department of Defense Activity Address Code (DoDAAC) and its addresses, a Routing Identifier Code (RIC) and the activity it points to, and the source-of-supply mapping a requisition will follow. This page is the canonical reference for what the inquiry tools are, where they came from, how to reach them, and how to use them.

What it is

DAASINQ and eDAASINQ are read-only inquiry applications that query the authoritative reference tables maintained by the Defense Automatic Addressing System. They do not originate, modify, or route transactions — that is the job of DAAS. Instead, they let a logistician, supply technician, or transportation specialist answer a small set of high-frequency questions with authority:

• Who is this DoDAAC? Resolve a six-character DoD Activity Address Code to its activity name, owning service or agency, major command, and the addresses the DoD Activity Address Directory (DoDAAD) holds for it.
• What is this Routing Identifier Code? Resolve a three-character RIC to the activity it identifies — typically an inventory control point, supply source, or processing point — and the routing data associated with it.
• Where will this route? Confirm the source of supply and routing path a transaction will take, given the codes it cites.

The published inquiry menu is broader than the DoDAAC/RIC core. DAASINQ provides lookups on the DoD Activity Address Code (DoDAAC), DoDAAC by Communications Routing Identifier (COMMRI), DoDAAC by Billing RI, Routing Identifier Code (RIC), COMMRI, Military Assistance Program Address Code (MAPAC), National Item Identification Number (NIIN), and Zip Code. The enhanced eDAASINQ adds Distribution Codes and provides multi-record query and download capability that the basic tool does not.

The distinction between the two names is generational and operational. DAASINQ is the original, public inquiry interface: open to all users, one code per query, no downloads. eDAASINQ — the "enhanced" DAASINQ — is the modernized, PKI-enabled successor that adds query types (Distribution Codes), multi-record queries, and downloads, and is reached only after an approved System Access Request. Both read the same underlying DAAS tables; the data is identical because the source is identical. Current DLA Transaction Services documentation generally points credentialed users to eDAASINQ.

Because the inquiry tools reflect the live authoritative tables, they are the fastest trustworthy way to confirm that a code is active and current — a determination that drives whether a requisition will be accepted, rerouted, or rejected downstream.

Why it exists

DoD logistics runs on a federated set of supply, maintenance, transportation, and finance systems that must exchange standardized transactions with each other constantly. For those transactions to reach the right place, every activity needs a stable identity (a DoDAAC), every routing destination needs a stable identifier (a RIC), and the mapping between them needs a single authoritative keeper. DAAS is that keeper and router; the DoDAAD and RIC tables are the authoritative data.

The problem the inquiry tools solve is verification before transmission. A requisition that cites a deactivated DoDAAC, a stale RIC, or a source of supply that has migrated to another manager will be rerouted or rejected by DAAS — generating status codes, delays, and rework. Rather than discover that after the fact, a logistician can look up the codes in eDAASINQ first and confirm the addressing data is current. The inquiry capability exists so that the people who build, troubleshoot, and reconcile logistics transactions can see the same reference data the routing engine uses, without needing direct access to the production routing system.

This is also why the tools are deliberately read-only. The authoritative data is updated through governed processes — DoDAAD changes flow through component-designated Central Service Points under DLM 4000.25, Volume 6 — not through an ad-hoc inquiry screen. DAASINQ exposes the result of those governed updates for inspection; it does not let an inquiry user edit them.

History and lineage

The Defense Automatic Addressing System is one of the longest-running pieces of DoD logistics infrastructure, and the inquiry tools inherit its lineage.

• DAAS origins. DAAS traces to the Defense Automatic Addressing System Office (DAASO), established in January 1966 to automatically address and route military supply transactions in place of manual MILSTRIP addressing. The activity has long been associated with Wright-Patterson Air Force Base in the Dayton, Ohio area.

• DAASC era (from 1989). Renamed the Defense Automatic Addressing System Center (DAASC) in a 1989 DLA reorganization, the organization operated DAAS as the central message switch for DoD logistics traffic and built the family of web tools — including DAASINQ — that exposed DAAS reference data to users over the web as the internet era arrived.
• Redesignation to DLA Transaction Services (2010). As part of DLA's consolidation of information operations, DAASC was redesignated DLA Transaction Services in 2010 and folded into the DLA Information Operations structure. The mission — addressing and routing DoD logistics transactions — carried over intact; the name on the door changed.

• eDAASINQ. The "enhanced" DAASINQ followed as the web interface was modernized, broadening query options and updating the presentation while keeping the same authoritative data underneath. The hosting, the gateway URLs, and the authentication path have all shifted across these reorganizations and across DoD's broader migration of applications behind CAC-gated portals and into cloud hosting — which is the practical reason old bookmarks to the inquiry tools frequently break.

The throughline: the data and the mission are stable across decades; the brand name, the front-end, and the access URL are not. When in doubt, reach the current tool through the DLA Transaction Services applications gateway rather than a saved link.

How it works

To use the inquiry tools well, it helps to understand the system behind them.

DAAS, the routing engine

DAAS is a message-switching system. A trading-partner system (a service supply system, a transportation system, a finance system, a procurement system) sends a logistics transaction — a MILSTRIP requisition, a MILSTRAP inventory transaction, a MILSBILLS billing transaction, or its DLMS equivalent — to DAAS. DAAS performs several functions on that transaction:

1. Edit and validate the transaction against business rules and reference data.
2. Address it — determine the correct destination from the codes it carries.
3. Route it to the destination trading partner, translating between MILS legacy formats and DLMS as needed.
4. Re-address it automatically when the cited routing data is out of date (for example, when a source of supply has migrated to a new manager), so the transaction still reaches the right place.

The reference data DAAS uses

DAAS's addressing decisions depend on authoritative reference tables, the most relevant of which to the inquiry tools are:

• The DoD Activity Address Directory (DoDAAD), keyed by DoDAAC, which carries each activity's name, type-of-address-code (TAC) address sets, and routing/owner attributes.
• The Routing Identifier Code (RIC) tables, keyed by RIC, which identify activities and the source-of-supply / processing-point relationships used to route transactions.

The inquiry layer

DAASINQ and eDAASINQ sit on top of those tables as a query interface. When you enter a DoDAAC or RIC, the tool reads the current authoritative record and returns it. There is no separate "DAASINQ database" that can drift from DAAS — the inquiry reflects the same data the router uses, which is what makes it trustworthy for verification.

Public access

The basic DAASINQ tool is genuinely public: it is open to all users and requires no login, CAC, or password. It is the no-credential way to resolve a single DoDAAC, RIC, COMMRI, MAPAC, NIIN, or Zip Code against the authoritative DoDAAD and RIC reference data — one code at a time, with no download capability. This reflects the public-reference nature of much DoDAAD and RIC data: the codes themselves are reference data, not sensitive material, so basic resolution is offered openly.

The public DAASINQ path is the right tool for quick, anonymous code resolution. The complete inquiry capability — additional query types such as Distribution Codes, multi-record queries, and downloads — lives in the authenticated eDAASINQ described below.

Authenticated access

Behind CAC/PKI authentication via the DLA Transaction Services portal, eDAASINQ exposes the enhanced capability set that the public tool does not: it carries all of the basic DAASINQ query types (DoDAAC, DoDAAC by COMMRI, DoDAAC by Billing RI, RIC, COMMRI, MAPAC, NIIN, Zip Code) and adds Distribution Codes, multi-record queries, and download capability. Authenticated access is the intended path for logisticians who need to pull or export routing data as part of their daily work, and it is the path current documentation points credentialed users to.

How to get access

There are two access paths, depending on which tool you need.

For basic DAASINQ (public): no credential is required. Reach the public DAASINQ inquiry through the DLA Transaction Services site and resolve a single code directly — no CAC, login, or account request.

For eDAASINQ (enhanced): access is provisioned, not just authenticated. The pattern is:

1. Hold a valid CAC / PKI certificate. This is the baseline credential for the PKI-enabled application.
2. Submit a System Access Request (SAR) to DLA Transaction Services, identifying eDAASINQ as the system you need and providing justification. eDAASINQ is not reachable on CAC alone — the SAR must be approved first.
3. Reach eDAASINQ through the Transaction Services portal once the SAR is approved, and authenticate with your CAC/PKI certificate.

For activities that need to change the underlying data rather than query it — for example, to create or update a DoDAAC — the path is different: changes flow through your component's designated DoDAAD Central Service Point, not through the inquiry tool. The inquiry tool is for verification; the Central Service Point process is for maintenance.

Complete task reference

The inquiry tools support a handful of high-frequency tasks. The canonical step-by-step workflows for each are presented on this page as structured HowTo procedures; the prose below frames when and why you would run each one.

Looking up a DoDAAC

The most common task. You have a six-character DoDAAC — pulled from a requisition, a shipment, a billing record, or a document register — and you need to know what activity it belongs to and where it ships, bills, or mails. The DoDAAC inquiry resolves the code against the DoDAAD and returns the activity name, owning service or agency, major command, and the TAC address sets. This is how you confirm a code is active, catch a transposed character, or identify the activity behind an unfamiliar code on a transaction.

Resolving a Routing Identifier Code

You have a three-character RIC and need to know which activity it identifies and whether a transaction citing it will route where you expect. The RIC inquiry returns the activity and its associated routing / source-of-supply data, which you then cross-check against the source of supply on the item record (for example, via WebFLIS) to confirm the requisition will reach the correct manager.

Diagnosing a DAAS reroute

When a transaction's status indicates DAAS re-addressed it, the inquiry tools are the diagnostic instrument. Look up the cited DoDAAC and RIC, compare them against the current authoritative values, and the stale field usually becomes obvious — DAAS rerouted because the cited destination was no longer current. This closes the loop between an unexpected status code and its reference-data root cause.

Reference tables

The inquiry tools surface a few code families a logistician should recognize on sight. The table below summarizes the principal identifiers DAASINQ / eDAASINQ resolve and where each is governed.

DAAS also routes transactions that cite many other MILSTRIP/DLMS code families (Document Identifier Codes, Advice Codes, status codes), but those are properties of the transactions DAAS routes rather than reference data the inquiry tools resolve. See the related references at the foot of this page.

Common gotchas and advanced tips

• An old DAASINQ bookmark is your enemy. The inquiry tools have moved hosts and gateways repeatedly across the DAASC-to-DLA-Transaction-Services transition and DoD's cloud/CAC migrations. A saved direct URL is the single most common reason people think "DAASINQ is down." Reach it through the current DLA Transaction Services gateway.
• DAASINQ shows you the current truth, not history. The inquiry reflects whatever the authoritative table holds right now. If a DoDAAC was active last week and now resolves as inactive, the inquiry will show inactive — it is not a point-in-time archive. For historical routing questions, you need the transaction's own status trail, not the inquiry.
• A reroute is usually a data problem, not a DAAS problem. When DAAS re-addresses a transaction, the instinct is to blame the router. Far more often the cited DoDAAC or RIC is stale and DAAS did exactly the right thing. Verify the codes before escalating.
• Confirm "active," not just "exists." A code can exist in the directory and still be inactive or in a status that affects routing. Read the status/ownership attributes the inquiry returns, not just the name.
• The inquiry is read-only — fixes go through the Central Service Point. If you discover a wrong address or an outdated DoDAAC in the inquiry, you cannot correct it there. Route the correction through your component's DoDAAD Central Service Point.
• Cross-check the RIC against the item's source of supply. A RIC that resolves cleanly still needs to match the current source of supply on the item record. Pair an eDAASINQ RIC lookup with a WebFLIS item-record check when a requisition's routing is in question.

When to use this vs. alternatives

DAASINQ / eDAASINQ is the right tool when your question is about the addressing and routing reference data — "who is this DoDAAC," "what does this RIC point to," "why did DAAS route this here." It is the wrong tool for several adjacent questions, which have their own systems:

• To look up an item's catalog data (NSN management data, source of supply on the record, unit of issue, codes), use WebFLIS or PUB LOG / FED LOG, not DAASINQ. DAASINQ resolves the routing identity; WebFLIS resolves the item.
• To create or change a DoDAAC, work through your component's DoDAAD Central Service Point under DLM 4000.25, Volume 6 — not the inquiry tool.
• To submit, track, or cancel a requisition, use your component's requisitioning system of record and standard MILSTRIP status, or the relevant procurement front end such as DLA DIBBS for solicitations. DAASINQ only verifies the reference data behind routing.
• To research inventory/accountability transactions, MILSTRAP procedures and your accountable property system apply.

In short: reach for DAASINQ / eDAASINQ to verify where and to whom, and reach for the catalog, requisitioning, and accountability systems to act on the item itself.

Training and authoritative references

The inquiry tools themselves are simple enough that most users learn them by doing, but the reference data and routing concepts behind them are governed by formal standards. The authoritative sources are the Defense Logistics Management Standards manual set — principally DLM 4000.25 for the DLMS transactions DAAS routes and DLM 4000.25, Volume 6 for the DoD Activity Address Directory procedures that define DoDAACs, RICs, and TAC addressing — maintained by the Defense Logistics Management Standards Office. The materiel-management context that drives why sources of supply migrate (and therefore why DAAS reroutes) is set in DoD Manual 4140.01. Approved DLMS Changes (ADCs) published by DLMSO document the ongoing evolution of the DoDAAD and DAAS routing rules and are the best primary source for recent changes. Links to each are in the references list on this page.

Interesting context

DAAS is one of those pieces of defense infrastructure that almost no one outside logistics has heard of, yet it touches an enormous share of DoD's daily materiel movement. DLA has described DAAS as processing on the order of tens of millions of logistics transactions per day across hundreds of thousands of registered DoDAACs and tens of thousands of electronic trading partners — nearly every standard supply transaction that crosses between two DoD systems passes through it to be addressed and routed. It predates the public internet by decades — born of the need to automate the manual addressing of punched-card and teletype MILSTRIP traffic — and has quietly survived every subsequent technology wave, from teletype to value-added networks to web services to cloud.

The name lineage tells a small institutional story of its own. For a long generation it was DAASC — the Defense Automatic Addressing System Center — a named center with its own identity in the Dayton, Ohio logistics community. The redesignation to the more functional DLA Transaction Services reflected DLA's broader consolidation of information operations into a single enterprise structure: the center became a service. The "e" prefixed onto eDAASINQ marks the same modernization impulse that swept DoD web applications in the 2000s, when "enhanced" and "e-" front ends proliferated as legacy mainframe inquiries were given web faces. Underneath all of it, the job has never changed: take a transaction, figure out where it goes, and send it there — reliably, tens of millions of times a day.

Page metadata

This page has been source-verified against public DLA Transaction Services, DAU, and DLM 4000.25 Vol 6 / ADC sources. The access split (public basic DAASINQ vs. PKI/SAR-gated eDAASINQ), the DAASINQ/eDAASINQ inquiry menus, the DAASO/DAASC/DLA Transaction Services lineage and organizational placement, the DoDAAD TAC definitions, and the DAAS volume framing are all confirmed in-line. The one item that remains an unsourced internal detail — whether the inquiry reads live production tables or a synced replica — does not affect the user-facing guidance. Corrections and access-path updates can be submitted through the site's correction path.