Plumbline / MA / contractor

Printed from Plumbline, a free public-record license check. This page: https://contractors.agentlookups.ai/ma/contractor/CC-016325-bryan-butler · Statuses change; check the live page before you rely on this sheet.

BRYAN BUTLER

MA license CC-016325 (Security Systems - Cert. of Clearance)

License Inactive or Expired as of 2026-08-22
Source status: "Inactive" per Massachusetts Division of Occupational Licensure (OPSI trades). The badge summarizes the sourced record below; the record and the issuing agency's live page are what count.
This is BRYAN BUTLER's own professional license record, as published by the Massachusetts Division of Occupational Licensure (OPSI 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 Massachusetts Division of Occupational Licensure (OPSI trades) snapshot dated 2026-08-22 shows license CC-016325 (Security Systems - Cert. of Clearance) with status "Inactive". The issuing agency's live page is authoritative for today.

What this status means

The Massachusetts Division of Occupational Licensure (OPSI trades) snapshot from 2026-08-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)

Source: Massachusetts Division of Occupational Licensure (OPSI trades), snapshot 2026-08-22. The issuing agency's live page is authoritative for today: official MA lookup.

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