BINCS Is Gone. Where DLA CAGE Search Actually Lives Now

BINCS — the Business Identification Number Cross-Referencing System — was retired by the Defense Logistics Agency and replaced with a tool called CAGE Search and Inquiry, known as CSI, hosted on the CAGE Public website at cage.dla.mil. If a bookmark, a training slide, or an old procurement guide points to a BINCS address, that link is dead; cage.dla.mil is where the same function lives today.

Where DLA CAGE search lives now, in one sentence

The Defense Logistics Agency's current CAGE search tool is CAGE Search and Inquiry (CSI), and it lives at cage.dla.mil — that single site now covers search, requesting a new CAGE code, and updating an existing one, all in place of the retired BINCS website. Anyone typing "bincs" or "dla cage" into a search bar is almost always looking for that one destination.

What BINCS was, and why it went away

BINCS stood for Business Identification Number Cross-Referencing System, and it was DLA's original public web tool for looking up CAGE code information before a redesign replaced it. According to DLA's own announcement, the agency launched a newly consolidated CAGE website on February 26, 2016, and that new site — CSI — is what replaced BINCS, not a rename or a redirect kept alongside it.

The stated reason for the change was the interface itself: BINCS had aged past the point of being intuitive for a first-time, untrained visitor, and DLA rebuilt the search experience from the ground up rather than patch the old one. CSI was designed with a simplified layout, more search options, and modern on-screen navigation, according to DLA's launch announcement — a straightforward interface upgrade, not a change in what CAGE codes are or how they are assigned.

What replaced it: CAGE Search and Inquiry (CSI)

CSI is DLA's current, publicly available tool for querying the CAGE database, and it is the successor named directly in DLA's own retirement announcement for BINCS. It runs on the CAGE Public website at cage.dla.mil, alongside the request forms and reference material DLA publishes for the CAGE Program overall.

The tool is also cited outside DLA's own site as the official validation destination: a Department of Defense acquisition capability summary on CAGE Search Inquiry names cage.dla.mil directly as where a contracting officer should confirm a CAGE code for an entity that is not required to register in SAM.gov. That is a second, independent confirmation that this is the live, current tool — not a legacy page that happens to still resolve.

It is worth being precise about who runs which system, since the two get conflated constantly. DLA's CAGE Program Office is the sole assigning authority for domestic CAGE codes and the operator of cage.dla.mil; SAM.gov is a separate system run for entity registration, and most U.S. entities receive their CAGE code as a byproduct of registering there rather than by applying to DLA directly. CSI exists as the CAGE Program's own front door for the cases SAM.gov registration does not cover on its own — confirming a code that already exists, or requesting one outside a full SAM.gov registration — not as a competing registration system.

What you can search by on cage.dla.mil

CSI accepts several different starting points for the same underlying CAGE record, which is a real improvement over a single rigid search box. Reference material describing the tool lists CAGE code, Unique Entity Identifier, legal business name, phone number, state, and postal code as valid ways to find an entity in the system. That flexibility matters most when a searcher has a company name but not its code, or a code but no name to confirm it against — either direction works.

DLA's own CAGE Public site, reachable from the same cage.dla.mil address, is also where a company that does not yet have a CAGE code requests one, and where an existing code holder updates the details tied to their registration. Search, request, and update sit under one roof now, which is exactly the consolidation DLA described when it retired BINCS.

Why old BINCS links and bookmarks stopped working

Any link built around the old BINCS domain stopped resolving once DLA decommissioned that site and moved everything to cage.dla.mil, and years later, plenty of outdated material still has not caught up. Embassy handbooks, older registration guides, training decks, and agency PDFs written before the 2016 changeover can still show a BINCS address as if it were current, simply because nobody went back to update them after the migration.

The practical fix is not trying to find a working mirror of the old site — there is not one — but updating the reference to point at cage.dla.mil directly. If a document, bookmark, or internal wiki page at an organization still cites BINCS by name, that is a reliable sign the material predates 2016 and is worth a second look for other outdated details, too, not just the broken link.

What DLA’s tool tells you — and what it does not

DLA's CAGE Search and Inquiry answers a narrower question than a full entity lookup does: it confirms whether a CAGE code exists, which facility it is tied to, and basic contact details on file with the CAGE Program. It is the authoritative source for that specific question, because DLA is the agency that assigns CAGE codes in the first place.

What it is not built to surface is the broader registration picture that lives in SAM.gov's entity data — current registration status, whether an entity carries a federal exclusion flag, or which NAICS codes it registered under. A CAGE code lookup built on that SAM.gov entity data answers those questions instead, working from the same current extract behind this site: 895,429 total entity registrations, 805,298 of them active, and 83 carrying a federal exclusion flag as of the 2026-08-02 data. Checking a code on cage.dla.mil confirms it is real and assigned; checking it against current SAM.gov data confirms whether the entity behind it is presently in good standing. A careful supplier check usually wants both, not just one.

The gap matters in practice, not just in theory. A CAGE code can be validly assigned and still sit behind an entity whose SAM.gov registration has since lapsed or been flagged for exclusion — DLA's assignment record does not change just because a company's standing did. That is exactly the scenario a stale, downloaded CAGE list cannot catch either, since a static file frozen months or years ago has no way to reflect a debarment decided afterward. Confirming a code exists is a one-time fact; confirming an entity is currently safe to do business with is a question that only current data can answer, which is why the two tools are complementary rather than interchangeable.