CT UCC Filings - Secured Lien & Debtor Search
Pricing
from $0.06 / 1,000 ct ucc debtor records
CT UCC Filings - Secured Lien & Debtor Search
Connecticut UCC financing-statement index (public open data, 846k debtor records): the public record of secured claims on a business or person - both debtor and secured party with names and addresses, the filing type, the lien class (OFS / MUNICIPAL / IRS / LABOR) and the acceptance and lapse dates.
Pricing
from $0.06 / 1,000 ct ucc debtor records
Rating
0.0
(0)
Developer
Wenhao Yang
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Share
When a lender takes a security interest in a business - equipment financing, inventory, receivables - it files a UCC financing statement with the Connecticut Secretary of the State. Those filings are public, and they are published as open data. This actor turns that index into a charged-per-record search, filter and aggregate tool: find a debtor by name, find everything a given lender has filed, pull the filings on a single statement, or aggregate the register.
Built for: lenders and credit analysts checking who else has a claim on a debtor, M&A and asset-based diligence, judgment and tax-lien recovery work, and anyone who wants the public lien record on a Connecticut business without paging a state portal one name at a time.
What it covers
846,538 debtor records - the state's UCC filing index, across 437,080 financing statements (a filing names as many debtors as it likes - one statement in this corpus carries 492 separate debtor rows - so one filing can return more than one row).
Both sides of the transaction, not just one name:
- the debtor - an organization (name) or a natural person (prefix / first / middle / last / suffix), with its street, city, state and zip to address 2
- the secured party - the lender, lessor or tax authority holding the claim, with its own full name parts and address
- the filing type - 29 values:
ORIG FIN STMT(519,137),AMENDMENT(306,985),RELEASE ORIG(6,850),CONTINUATION,ASSIGNMENT,TERMINATION,VESSEL LIEN,AIRCRAFT LIEN,JUDGMENT LIEN - the lien class - 15 values:
OFS(503,677),MUNICIPAL(220,461),IRS(81,204),LABOR(21,828),DEPT REV SERVS,TRANS UTILITY,PUBLIC-FINANCE,VESSEL - the lien status -
Active(844,000) /Released(2,361) /Terminated(177) - both the acceptance date and the lapse date, plus the record volume, start page and page count
The fine print that matters
A filing number is not a debtor. The number identifies the statement; the index lists every debtor named on it, so filingNo can legitimately return more than one record - and the rows differ by debtor, not by duplication, so nothing is merged away.
The register carries two filings numbers, and they mean different things: the original filing number, and the subsequent filing number. They are identical on the 523,821 filings that were never amended and differ on the 322,705 that were - so an amendment sits on the same statement but not on the same column, and both are returned.
A debtor is either an organization or a natural person, never both, and the two sides are populated very differently: 569,318 rows carry a debtor business name against 273,859 with a debtor surname, while the secured-party side is overwhelmingly organizational (843,927 business names against 8,296 surnames). Every record keeps both key sets (empty-filled), so the output shape never shifts, and a name search matches either form rather than assuming one.
This is a historical archive, not a rolling window - acceptance dates run from 1888 to today. A date filter is honoured exactly as given, with no floor silently applied.
One column needs reading carefully. 112,182 records (13.2%) carry 9999-12-31 in the lapse date - the publisher's way of writing "no lapse date of record", not a filing that outlives its collateral by eight millennia. Those are cleared on output and excluded from every lapse filter, so a "liens expiring before 2030" query returns liens that really do expire, not a wall of perpetual filings. The lapse column holds genuine dates out to 2056, and a further two rows carry a plainly bogus 2201 that is cleared the same way, so no lapse filter ever returns a date past the sentinel. 90,837 filings carry a lapse date inside the next twelve months.
Typical questions
- "Every UCC filing naming a given Connecticut business."
- "Everything a given lender has a secured claim on in Connecticut."
- "The debtors on one financing statement."
- "IRS or municipal liens filed against a business."
- "Filings accepting to lapse in a window - the liens about to expire."
- "Aggregate the index by lien class, filing type or debtor state."
Inputs
| Input | What it does |
|---|---|
mode | rows (default) / aggregate |
debtor | debtor name substring - organization or any person name part |
securedParty | secured-party name substring - organization or any person name part |
debtorName | organization-name column only |
filingNo / subsequentNo | exact filing numbers |
filingType / lienType / lienStatus | original/amendment/release; OFS/IRS/municipal; active/released/terminated |
city / state | debtor location |
acceptedFrom / acceptedTo | acceptance-date window |
lapseFrom / lapseTo | lapse-date window |
groupBy | aggregate over lien class / filing type / status / debtor state / secured-party state |
maxResults | cap records (default 50) |
Default run = the 50 most recent debtor records - fast for the daily auto-test. For a targeted query add a filter; for a broad view use aggregate.
Low cost
From $0.00006 per record Pay-per-event: you are charged per record delivered, and nothing for the query. Cost scales with what you pull, not with the size of the index, and each record is metered individually - a full named-debtor pull costs a fraction of a cent.