Plumbline / CT / contractor

Printed from Plumbline, a free public-record license check. This page: https://contractors.agentlookups.ai/ct/contractor/652809-nicholas-p-dzenutis · Statuses change; check the live page before you rely on this sheet.

NICHOLAS P DZENUTIS

CT license 652809 (HIC) · NEW HARTFORD

License Expired as of 2026-09-22
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 NICHOLAS P DZENUTIS'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-09-22 shows license 652809 (HIC) with status "INACTIVE", expired 2022-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-09-22 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
2022-03-31
Issued
2018-09-17

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

For developers and AI agents: source snapshot file sha256:0e9d84a1c5e40df69772dbc1a4812c807260279e7a4f90618d6c632006d8955b (row 13979). 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