Bill Commons

VA HB 743

Status unknown

Va. Telephone Privacy Protection Act; voice service providers, caller identification authentication.

Virginia · 2026 Regular Session · lower

Quick answers

Did VA HB 743 pass?

The current status of VA HB 743 is not known from the official record. Latest recorded action (2026-02-18): Left in Committee Communications, Technology and Innovation

What is VA HB 743 about?

Virginia Telephone Privacy Protection Act; voice service providers; duty of care; caller identification authentication; civil penalties. Provides that a voice service provider, defined in the bill, owes an affirmative duty of care to take reasonable and effective measures to prevent the origination, transmission, and completion of unlawful calls. The bill requires voice service providers to implement caller identification authentication technology consistent with the Secure Telephone Identity Revisited and Secure Handling of Asserted information using toKENs (STIR/SHAKEN) authentication framework, defined in the bill, in all internet protocol network segments under its control and shall implement functionally equivalent authentication, verification, or mitigation measures in non-internet protocol network segments to the extent technically feasible. The bill provides that a violation of its provisions constitutes a prohibited practice under the Virginia Consumer Protection Act.

Who sponsors VA HB 743?

Wren M. Williams is the primary sponsor of VA HB 743.

Description

Virginia Telephone Privacy Protection Act; voice service providers; duty of care; caller identification authentication; civil penalties. Provides that a voice service provider, defined in the bill, owes an affirmative duty of care to take reasonable and effective measures to prevent the origination, transmission, and completion of unlawful calls. The bill requires voice service providers to implement caller identification authentication technology consistent with the Secure Telephone Identity Revisited and Secure Handling of Asserted information using toKENs (STIR/SHAKEN) authentication framework, defined in the bill, in all internet protocol network segments under its control and shall implement functionally equivalent authentication, verification, or mitigation measures in non-internet protocol network segments to the extent technically feasible. The bill provides that a violation of its provisions constitutes a prohibited practice under the Virginia Consumer Protection Act.

Introduced
2026-01-13
Latest action
2026-02-18 — Left in Committee Communications, Technology and Innovation
Bill type
bill
Last updated

Sponsors

  • Wren M. Williamsprimary

Committees

Not provided by source.

Action timeline

  1. 2026-01-13

    Prefiled and ordered printed; Offered 01-14-2026 26105128D

    filing,introduction

  2. 2026-01-13

    Referred to Committee on Communications, Technology and Innovation

    referral-committee

  3. 2026-01-29

    Assigned HST sub: Communications

    referral-committee

  4. 2026-02-09

    Subcommittee recommends striking from the docket (8-Y 0-N 1-A)

  5. 2026-02-18

    Left in Committee Communications, Technology and Innovation

Versions

Documents

Votes

  • Subcommittee recommends striking from the docket

    2026-02-09 · pass · 8-0

    Member-level votes (10)
    • Timothy P. Griffin: not voting
    • Jackie H. Glass: yes
    • Alfonso H. Lopez: yes
    • Irene Shin: yes
    • Holly M. Seibold: yes
    • Michelle Lopes Maldonado: yes
    • Lily V. Franklin: yes
    • Garrett McGuire: abstain
    • H. Otto Wachsmann, Jr.: yes
    • Justin Pence: yes

Related bills

No related bills recorded for this bill.

Official source

Attribution

Data from openstates_bulk_csv, retrieved 2026-07-24T05:35:59.552682Z

Inspect retained evidence for changes recorded after evidence tracking began:

Use this data

Every field on this page is available from the free public API — no key or licence required. Fetch this bill as JSON: GET /api/v1/bills?jurisdiction=VA&identifier=HB 743. See the API docs or the MCP server for AI assistants.

Known limitations

  • Sponsor party and chamber affiliation are not yet captured by this API.
  • Committee referrals are not yet captured.

See the methodology page for data sources and limitations.