What a caller-name database dip can tell you about your outbound numbers — and the three ways it can quietly mislead you.

CNAM Lookup: How to Check the Name Your Number Displays

A CNAM lookup queries a caller-name database for the name string — up to 15 characters — associated with a phone number. Outbound teams run lookups in two directions: before a campaign, to confirm what name a caller ID carries, and across a whole number inventory, to catch records that are missing, stale, or wrong. This guide covers what a lookup actually returns, the free and near-free ways to run one, how bulk audits work, and the display realities — on cell phones especially — that decide how much any single answer means. If you want the foundations first, start with the what is CNAM explainer.

What a CNAM Lookup Actually Returns

In the US, the caller’s name is not transmitted with the call. As telecom-infrastructure vendor TelcoBridges explains it, the recipient’s carrier is responsible for name display: it performs a real-time database query — the “CNAM dip” — on the calling number before the phone rings, over legacy SS7 signaling or a modern API, completing in milliseconds. When you run a CNAM lookup, you are performing that same dip yourself and reading the answer.

Three properties of the system shape everything else on this page:

• There is no single national CNAM registry. Caller-name data lives in multiple independent Line Information Databases (LIDBs) and third-party CNAM providers. The name displayed for the same number can differ depending on which database the terminating carrier queries — so one lookup shows you one database’s answer, not the answer.
• Records are 15 characters, take it or leave it. Industry glossaries note CNAM strings are capped at 15 characters and must contain at least one non-numeric character; longer business names get truncated and are often forced to uppercase. “Bridgewater Consulting Group” becomes something like “BRIDGEWATER CON” — worth knowing before you blame the database.
• The recipient’s carrier pays for the dip — and behaves accordingly. Industry references put wholesale dip fees on the order of $0.002–$0.006 per lookup, roughly $200–$600 per 100,000 calls. Because dips cost money, carriers cache results, dip selectively, or skip the dip entirely. A correct record does not obligate anyone to fetch it.

Hold onto that last point: a CNAM lookup tells you what a database says, not what a given recipient’s screen will show.

Free CNAM Lookup Methods

The manual dip. The oldest method is still the most direct: call a phone that actually displays CNAM — a traditional landline, or a VoIP line with inbound caller-name display enabled — from the number you’re checking, and read the screen. It costs nothing and shows you a real dip result. Its limit is the same as any single lookup: you’re seeing whichever database that line’s provider queries.

What a manual dip is not: calling your own cell. Ringing your own mobile phone tells you very little about CNAM, because — per industry explainers, and consistent with how the carriers package their products — the major US wireless carriers generally rely on their analytics and app layer for name and label display rather than traditional CNAM dips. More on this below, because it’s the single most misunderstood thing about caller-name display.

Free web checkers — verify before you rely. Free CNAM lookup pages exist, but the category churns; tools disappear, and some long-running ones have shut down entirely. Our caller ID test guide maintains a verified list of working free checkers — for names and for spam labels — and is the better starting point than a search-engine roulette spin.

What happened to OpenCNAM. For years the reflex answer to “free CNAM lookup API” was OpenCNAM. It no longer operates independently: as of July 2026, opencnam.com redirects to Neustar’s (TransUnion) Caller Name Services — an enterprise, quote-based product. If your notes still say OpenCNAM, update them.

One non-method, for the record. The Free Caller Registry — the joint portal from First Orion, Hiya, and TNS — is free and worth using, but it is a spam-analytics registration tool, not a CNAM service. Its own documentation states that neither the providers nor their carrier partners use registration data to deliver caller ID name. Registering there does not set, correct, or look up CNAM.

Published Per-Query Pricing

When you outgrow spot checks, the API route is cheap and scriptable. These are the published figures, from each vendor’s pricing page as of July 2026:

At those rates, checking ten numbers costs pennies either way; the pricing only starts to matter at inventory scale — which is the next section.

Bulk CNAM Lookup: Auditing a Number Inventory

Outbound teams don’t dial from one number. A team running managed caller ID pools — Enzo seats carry 35 numbers each on Starter and 100 on Standard — has an inventory, and inventories drift: numbers get provisioned, swapped, and retired, and the name records attached to them don’t always keep up. A bulk CNAM audit answers a simple operational question: what name is every number in my pool actually carrying right now?

The audit catches four kinds of problems worth finding before your prospects do:

1. Missing records — numbers that return nothing, which typically display as a bare number or a city/state string.
2. Stale or previous-owner names — recycled numbers can carry the prior holder’s name until someone updates the record.
3. Bad truncation — a 15-character cut that turned your brand into alphabet soup.
4. Mismatches across databases — the same number returning different names from different sources, which means recipients see different things depending on their carrier.

Mechanically, bulk lookup is unglamorous: export the inventory to CSV, iterate it through a per-query lookup API, and diff the results against what the records should say. No vendor-published dedicated bulk-CNAM product was documented as of July 2026 — the working pattern is the same per-dip APIs at volume, and Telnyx notes contract pricing for volume commitments. At published per-query rates, a 1,000-number audit runs about $3 on Telnyx or $10 on Twilio — cheap enough to schedule, not just run once. Because the databases are independent, a thorough audit checks more than one source before calling a record clean.

The Wireless Display Reality

Here is the limit that reframes everything above: a clean CNAM record mostly matters where CNAM is actually displayed — and on US mobile phones, it generally isn’t the layer doing the work.

Industry explainers note that many carriers, wireless carriers especially, historically did not dip traditional CNAM at all, showing only the number or labels from their own analytics. The carriers’ own product pages tell the same story from the retail side. Verizon’s Call Filter FAQs list caller-name display as a paid feature of Call Filter Plus — $3.99 per month per line, or $10.99 per month for three or more lines, as of July 2026. T-Mobile’s network-level display runs through Scam Shield, and AT&T’s through ActiveArmor — the analytics apps that apply labels like “Scam Likely” and “Spam Risk,” which is a scoring system entirely separate from the CNAM databases.

Two practical consequences for outbound teams:

• A clean lookup result is not a display promise. Your record can be correct in every database and a cell-phone recipient may still see just a number — or a name sourced from an analytics app, contact-sharing data, or nothing at all.
• A CNAM lookup is not a spam check. Name databases and reputation analytics don’t consult each other. A number can return a flawless name and still ring phones wearing a label. What recipients see on each network is a separate investigation — that’s caller ID reputation work, with its own monitoring loop.

None of this makes CNAM hygiene pointless: landlines and many VoIP systems still dip and display it, some wireless paths surface it through paid features, and a wrong name anywhere is worse than a right one. It just means a lookup is one instrument on the panel, not the whole dashboard.

When the Lookup Shows the Wrong Name

You can’t edit CNAM databases directly. The record is set through the carrier or VoIP provider that owns the number: your provider publishes the outbound name into the caller-name databases, and the databases serve it to whoever dips. Telnyx, as a published example, lists outbound CNAM listing free on its numbers. After a change, provider explainers put typical propagation at 24–72 hours across database providers — and carrier caches can lag behind that, so re-run your lookup a few days out before concluding the fix failed. No originating provider can force a terminating carrier to dip the database or honor the record; you control what the databases say, not what any screen shows.

The step-by-step process — choosing the 15-character string, submitting through your provider, and verifying propagation — is covered in the CNAM registration guide.

And if the lookup comes back correct but recipients report warnings on your calls, stop working the name problem — that’s a reputation problem, and it routes through registration, behavior, and remediation channels instead.

Where This Fits in an Outbound Operation

A CNAM lookup is a five-second check that keeps a slow-moving layer of your caller ID stack honest: run it when you provision numbers, after any name change, and on a schedule across the full pool. Enzo handles the pool side of that equation as part of the product — every seat includes managed caller IDs, 35 on Starter and 100 on Standard, provisioned by Enzo with optional CNAM, monitored for reputation, and rotated or swapped when a number’s health dips — so name records and number health are maintained upstream of your campaigns rather than on a spreadsheet you have to remember. Want to see how managed caller IDs work in practice? Book a free discovery call — 20 minutes, straight answers.

Company names are trademarks of their owners; pricing and product details as of July 2026 — verify with each provider.