Public Bodies Would Shift to .gov Domains

Summary#

HB 707 would add a section to the Code of Virginia; it does not create a new agency. It has passed the House of Delegates, but the supplied material does not show that it has become law. Its apparent goal is to make public bodies use consistent website and employee-email domains.

  • Most public bodies would be barred from maintaining an official public website on a domain other than .gov, .edu, or .museum. The bill also says non-.gov domains may be kept only to redirect people to an official .gov site, leaving the treatment of .edu and .museum domains unclear.
  • Public bodies would have to use .gov domains for email addresses they provide to employees.
  • The Virginia Information Technologies Agency (VITA) must issue implementation guidelines, including guidance on transition periods, redirect standards, and procedures for exception requests or waivers. VITA must also work toward uniform compliance while allowing practical flexibility.
  • The definition covers state and local government bodies and some organizations supported mainly by public funds. It excludes, among others, institutions of higher education, state museums, state hospitals, and several named state authorities.
  • The bill would take effect July 1, 2029, if enacted.

What it means for you#

  • Public bodies: They would need to use .gov employee-email addresses and meet the website-domain rules. VITA’s guidelines are expected to address transitions, redirects, and exception requests or waivers.
  • Employees: Email addresses provided by their public body would have to use a .gov domain.
  • People using public websites: The bill would not require a change to website content or public services. It may affect the address people use to reach a public body’s official website.
  • Current law: The supplied material does not include the existing Code provisions, so I cannot verify which bodies already face domain requirements or what requirements are new.

Money#

The bill requires public bodies to use specified domains, but no cost estimate is available in the supplied material.

  • Public bodies may need to change website or employee-email domains. The bill gives no estimate of transition, staffing, or technology costs.
  • VITA must issue guidelines and work toward uniform compliance, but the bill gives no cost or staffing estimate for that work.

What is unclear#

  • The website rules appear to conflict: one part allows official websites on .edu or .museum domains, while another says non-.gov domains, including those domains, may be kept only to redirect people to a .gov site.
  • The bill does not set out when existing websites and email systems must transition. It directs VITA to issue guidelines about a “reasonable” transition period.
  • VITA must provide procedures for exception requests or waivers, but the bill does not say who may qualify, who decides, or what standards apply.
  • The bill does not explain how it applies to public bodies that share websites or email systems, or how compliance will be enforced.
  • The bill does not specify costs or how any transition would be funded.

Case for#

  • A possible argument for the bill is that a common .gov destination could make it clearer which websites and employee email addresses belong to public bodies.
  • VITA’s role could support consistent implementation across state and local bodies while allowing for practical flexibility.
  • The planned guidance on transitions and redirects could help bodies move to the required domains without abruptly cutting off existing website addresses.

Case against#

  • The conflicting website provisions leave public bodies unsure whether .edu and .museum sites can remain official sites or must only redirect to .gov sites.
  • One concern is that changing websites and employee email addresses could cost public bodies money and disrupt access; the bill provides no cost estimate or detailed transition rules.
  • The bill covers many types of public bodies but excludes several named institutions and authorities. That could lead to different domain rules for people using different public services.
  • The bill leaves important choices to future VITA guidance, while giving few details about exceptions, waivers, or how compliance will be checked.