Plumbline / CT / contractor

Printed from Plumbline, a free public-record license check. This page: https://contractors.agentlookups.ai/ct/contractor/HTG.0007201-S3-72-degrees-ac-heat · Statuses change; check the live page before you rely on this sheet.

72 DEGREES A/C HEAT

CT license HTG.0007201-S3 (HEATING, PIPING & COOLING LIMITED CONTRACTOR) · BALTIC

License Inactive or Expired as of 2026-08-25
Source status: "EXPIRED APPLICATION" per Connecticut eLicense (trades). The badge summarizes the sourced record below; the record and the issuing agency's live page are what count.
This is 72 DEGREES A/C HEAT's own professional license record, as published by the Connecticut eLicense (trades). 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 eLicense (trades) snapshot dated 2026-08-25 shows license HTG.0007201-S3 (HEATING, PIPING & COOLING LIMITED CONTRACTOR) with status "EXPIRED APPLICATION". The issuing agency's live page is authoritative for today.

What this status means

The Connecticut eLicense (trades) snapshot from 2026-08-25 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
EXPIRED APPLICATION (in plain terms: inactive)

Source: Connecticut eLicense (trades), snapshot 2026-08-25. The issuing agency's live page is authoritative for today: official CT lookup.

For developers and AI agents: source snapshot file sha256:9c2984d0f6fd0b3858a076b4c0ac9f022c3dd2a37e2311a0a22e5784a704d744 (row 12427). 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