Plumbline / CT / contractor

Printed from Plumbline, a free public-record license check. This page: https://contractors.agentlookups.ai/ct/contractor/546338-jerry-s-cleaning-serv · Statuses change; check the live page before you rely on this sheet.

JERRY'S CLEANING SERV

CT license 546338 (HIC) · Waterbury

License Expired as of 2026-08-10
Source status: "INACTIVE" per Connecticut Department of Consumer Protection (DCP). The badge summarizes the sourced record below; the record and the issuing agency's live page are what count.
This is JERRY'S CLEANING SERV's own professional license record, as published by the Connecticut Department of Consumer Protection (DCP). It is not a background check, and it is not a consumer report. Do not use it for any FCRA purpose: not for employment, tenant, credit, or insurance screening. We show only this one occupational-license record and its official source; we do not aggregate other records about this person and we make no characterization of them.

The Connecticut Department of Consumer Protection (DCP) snapshot dated 2026-08-10 shows license 546338 (HIC) with status "INACTIVE", expired 2026-03-31. The issuing agency's live page is authoritative for today.

What this status means

The Connecticut Department of Consumer Protection (DCP) snapshot from 2026-08-10 does not show this license as active and in good standing. That is what the record said on that date. It is not a judgment about the person or the business. Before you act on it:

Hiring soon? The full checklist: How do I check if a contractor is legit?

What the record shows

Status
INACTIVE (in plain terms: inactive)
Expires
2026-03-31
Issued
1999-12-01

Source: Connecticut Department of Consumer Protection (DCP), snapshot 2026-08-10. The issuing agency's live page is authoritative for today: official CT lookup.

For developers and AI agents: source snapshot file sha256:4245a5465de81dc3890c6b5acece7b7cca50699a5d029639d5566106f85d603d (row 44404). This is the archived source file we read this record from, and the row within it; the file hash is shared by every record in the same fetch, so it identifies the snapshot, not the individual record.

What we did not check