Skip to content

Commit cf6e133

Browse files
authored
Merge pull request #486 from cisagov/h-m-f-t-patch-5-1
2 parents 6aa5899 + 4651e6b commit cf6e133

File tree

3 files changed

+152
-72
lines changed

3 files changed

+152
-72
lines changed
Lines changed: 146 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,146 @@
1+
<section>
2+
<div class="usa-accordion usa-accordion--bordered">
3+
4+
<h3 class="usa-accordion__heading">
5+
<button type="button" class="usa-accordion__button" aria-expanded="false" aria-controls="exec-branch-federal-agencies">
6+
Federal (executive)
7+
</button>
8+
</h3>
9+
10+
<div id="exec-branch-federal-agencies" class="usa-accordion__content usa-prose">
11+
12+
<p>Domain requests must be authorized by the agency's Chief Information Officer (CIO) or the head of the agency. A request must be submitted by the agency’s <a href="{{ '/help/member-management/' | url }}#understanding-enterprise-mode-roles-and-permissions" class="usa-link">organization admin</a> or another person with request permissions.</p>
13+
14+
<p>See <a href="https://www.whitehouse.gov/wp-content/uploads/2023/02/M-23-10-DOTGOV-Act-Guidance.pdf" class="usa-link usa-link--external" target="_blank" rel="noopener noreferrer">OMB Memorandum M-23-10</a> for more information.</p>
15+
16+
</div>
17+
18+
<h3 class="usa-accordion__heading">
19+
<button type="button" class="usa-accordion__button" aria-expanded="false" aria-controls="legislative-branch-federal-agencies">
20+
Federal (legislative)
21+
</button>
22+
</h3>
23+
24+
<div id="legislative-branch-federal-agencies" class="usa-accordion__content usa-prose">
25+
<h4>U.S. Senate</h4>
26+
27+
<p>Domain requests from the U.S. Senate must be authorized by the Senate Sergeant at Arms. A request must be submitted by the agency’s <a href="{{ '/help/member-management/' | url }}#understanding-enterprise-mode-roles-and-permissions" class="usa-link">organization admin</a> or another person with request permissions.</p>
28+
29+
<h4>U.S. House of Representatives</h4>
30+
31+
<p>Domain requests from the U.S. House of Representatives must be authorized by the House Chief Information Officer. The request must be submitted by the agency’s <a href="{{ '/help/member-management/' | url }}#understanding-enterprise-mode-roles-and-permissions" class="usa-link">organization admin</a> or another person with request permissions.</p>
32+
33+
<h4>Other legislative branch agencies or commissions</h4>
34+
35+
<p>Domain requests from legislative branch agencies must come from the agency’s head or CIO. A request must be submitted by the agency’s <a href="{{ '/help/member-management/' | url }}#understanding-enterprise-mode-roles-and-permissions" class="usa-link">organization admin</a> or another person with request permissions.</p>
36+
37+
<p>Domain requests from legislative commissions must come from the head of the commission, or the head or CIO of the parent agency, if there is one. A request must be submitted by the commission’s <a href="{{ '/help/member-management/' | url }}#understanding-enterprise-mode-roles-and-permissions" class="usa-link">organization admin</a> or another person with request permissions.</p>
38+
</div>
39+
40+
<h3 class="usa-accordion__heading">
41+
<button type="button" class="usa-accordion__button" aria-expanded="false" aria-controls="judicial-branch-federal-agencies">
42+
Federal (judicial)
43+
</button>
44+
</h3>
45+
46+
<div id="judicial-branch-federal-agencies" class="usa-accordion__content usa-prose">
47+
48+
<p>Domain requests for judicial branch agencies, except the U.S. Supreme Court, must be authorized by the director or CIO of the Administrative Office (AO) of the United States Courts.</p>
49+
50+
<p>Domain requests from the U.S. Supreme Court must be authorized by the director of information technology for the U.S. Supreme Court.</p>
51+
52+
<p>A request must be submitted by the agency’s <a href="{{ '/help/member-management/' | url }}#understanding-enterprise-mode-roles-and-permissions" class="usa-link">organization admin</a> or another person with request permissions.</p>
53+
</div>
54+
55+
<h3 class="usa-accordion__heading">
56+
<button type="button" class="usa-accordion__button" aria-expanded="false" aria-controls="states-territories-eligibility">
57+
U.S. states and territories
58+
</button>
59+
</h3>
60+
61+
<div id="states-territories-eligibility" class="usa-accordion__content usa-prose">
62+
<h4>Executive branch</h4>
63+
64+
<p>Domain requests from states and territories must be authorized by someone in a role of significant, executive responsibility within the agency (department secretary, senior technology officer, or equivalent).</p>
65+
66+
<h4>Judicial and legislative branches</h4>
67+
68+
<p>Domain requests from state and territory legislatures and courts must be authorized by an agency’s CIO or someone in a role of significant, executive responsibility within the agency.</p>
69+
70+
</div>
71+
72+
<h3 class="usa-accordion__heading">
73+
<button type="button" class="usa-accordion__button" aria-expanded="false" aria-controls="tribal-governments-eligibility">
74+
Tribal governments
75+
</button>
76+
</h3>
77+
78+
<div id="tribal-governments-eligibility" class="usa-accordion__content usa-prose">
79+
80+
<p>Domain requests from federally recognized tribal governments must be authorized by the tribal leader the <a href="https://www.bia.gov/service/tribal-leaders-directory" class="usa-link usa-link--external" target="_blank" rel="noopener noreferrer">Bureau of Indian Affairs</a> recognizes.</p>
81+
82+
<p>Domain requests from state-recognized tribal governments must be authorized by the tribal leader the individual state recognizes.</p>
83+
84+
</div>
85+
86+
<h3 class="usa-accordion__heading">
87+
<button type="button" class="usa-accordion__button" aria-expanded="false" aria-controls="counties-eligibility">
88+
Counties
89+
</button>
90+
</h3>
91+
92+
<div id="counties-eligibility" class="usa-accordion__content usa-prose">
93+
94+
<p>Domain requests from counties must be authorized by the commission chair or someone in a role of significant, executive responsibility within the county (county judge, county mayor, parish/borough president, senior technology officer, or equivalent). Other county-level offices (county clerk, sheriff, county auditor, comptroller) may qualify, as well, in some instances.</p>
95+
96+
</div>
97+
98+
<h3 class="usa-accordion__heading">
99+
<button type="button" class="usa-accordion__button" aria-expanded="false" aria-controls="cities-eligibility">
100+
Cities
101+
</button>
102+
</h3>
103+
104+
<div id="cities-eligibility" class="usa-accordion__content usa-prose">
105+
106+
<p>Domain requests from cities must be authorized by someone in a role of significant, executive responsibility within the city (mayor, council president, city manager, township/village supervisor, select board chairperson, chief, senior technology officer, or equivalent).</p>
107+
108+
</div>
109+
110+
<h3 class="usa-accordion__heading">
111+
<button type="button" class="usa-accordion__button" aria-expanded="false" aria-controls="special-districts-eligibility">
112+
Special districts
113+
</button>
114+
</h3>
115+
116+
<div id="special-districts-eligibility" class="usa-accordion__content usa-prose">
117+
118+
<p>Domain requests from special districts must be authorized by someone in a role of significant, executive responsibility within the district (CEO, chair, executive director, senior technology officer, or equivalent).</p>
119+
</div>
120+
121+
<h3 class="usa-accordion__heading">
122+
<button type="button" class="usa-accordion__button" aria-expanded="false" aria-controls="school-districts-eligibility">
123+
School districts
124+
</button>
125+
</h3>
126+
127+
<div id="school-districts-eligibility" class="usa-accordion__content usa-prose">
128+
129+
<p>Domain requests from school district governments must be authorized by someone in a role of significant, executive responsibility within the district (board chair, superintendent, senior technology officer, or equivalent).</p>
130+
131+
<p>We use the <a href="https://www.census.gov/library/publications/2024/econ/2022isd.html" class="usa-link usa-link--external" target="_blank" rel="noopener noreferrer">U.S. Census Bureau's definition of school district governments</a>.</p>
132+
133+
</div>
134+
135+
<h3 class="usa-accordion__heading">
136+
<button type="button" class="usa-accordion__button" aria-expanded="false" aria-controls="interstate-organizations-eligibility">
137+
Interstate organizations
138+
</button>
139+
</h3>
140+
141+
<div id="interstate-organizations-eligibility" class="usa-accordion__content usa-prose">
142+
143+
<p>Domain requests from interstate organizations must be authorized by someone in a role of significant, executive responsibility within the organization (president, director, chair, senior technology officer, or equivalent) or one of the state’s CIOs.</p>
144+
</div>
145+
</div>
146+
</section>
Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
- **Federal**: an agency of the U.S. government’s legislative, executive, or judicial branches
2-
- **Interstate**: an organization of two or more states
32
- **State or territory**: one of the 50 U.S. states, the District of Columbia, American Samoa, Guam, Northern Mariana Islands, Puerto Rico, or the U.S. Virgin Islands
43
- **Tribal**: a tribal government recognized by the federal or a state government
54
- **County**: a county, parish, or borough
65
- **City**: a city, town, township, village, etc.
76
- **Special district**: an independent government that delivers specialized, essential services
87
- **School district**: a school district that is not part of a local government
8+
- **Interstate**: an organization of two or more states

pages/domains/domains_eligibility.md

Lines changed: 5 additions & 71 deletions
Original file line numberDiff line numberDiff line change
@@ -13,9 +13,9 @@ eleventyNavigation:
1313

1414

1515
## Only verified U.S. government organizations can register and operate a .gov domain
16-
For a fee, anyone can register a .com, .org, or .us domain. .Gov domains are different because they’re only available to U.S.-based government organizations, and they’re free.
16+
Anyone can register a .com, .org, or .us domain for a fee. .Gov domains are different because they’re only available to U.S.-based government organizations, and they’re free.
1717

18-
The Cybersecurity and Infrastructure Security Agency (CISA) manages the .gov top-level domain. We verify the identity of everyone who requests a .gov domain and we make sure that their organization meets the criteria for having a .gov domain.
18+
The Cybersecurity and Infrastructure Security Agency (CISA) manages the .gov top-level domain. We verify the identity of everyone who requests a .gov domain and we make sure that their organization meets the criteria for registering a .gov domain.
1919

2020

2121
## Government organizations at all levels are eligible for .gov domains
@@ -30,77 +30,11 @@ After you request a .gov domain, we'll review the information you provided about
3030
## You must have approval from a senior official within your organization
3131
Your senior official is a person within your organization who can authorize your domain request. This person must be in a role of significant, executive responsibility within the organization.
3232

33-
When you request a .gov domain, we’ll ask for information about your senior official (role, contact information). We typically don’t reach out to them, but if contact is necessary, our practice is to coordinate first with you, the requestor.
33+
When you request a .gov domain, we’ll ask for information about your senior official (role, contact information). We typically don’t reach out to them, but if contact is necessary, our practice is to coordinate first with you, the requester.
3434

35-
**Read more about senior officials for**:
36-
- [Executive branch federal agencies](#executive-branch-federal-agencies)
37-
- [Judicial branch federal agencies](#judicial-branch-federal-agencies)
38-
- [Legislative branch federal agencies](#legislative-branch-federal-agencies)
39-
- [U.S. Senate](#u-s-senate)
40-
- [U.S. House of Representatives](#u-s-house-of-representatives)
41-
- [Other legislative branch agencies](#other-legislative-branch-agencies)
42-
- [Interstate organizations](#interstate-organizations)
43-
- [U.S. states and territories](#u-s-states-and-territories)
44-
- [States and territories: executive branch](#states-and-territories-executive-branch)
45-
- [States and territories: judicial and legislative branches](#states-and-territories-judicial-and-legislative-branches)
46-
- [Tribal governments](#tribal-governments)
47-
- [Counties](#counties)
48-
- [Cities](#cities)
49-
- [Special districts](#special-districts)
50-
- [School districts](#school-districts)
35+
Read more about senior officials for your organization:
5136

52-
### Executive branch federal agencies {.h4}
53-
Domain requests from executive branch federal agencies must be authorized by the agency’s CIO or the head of the agency.
54-
55-
See [OMB Memorandum M-23-10](https://whitehouse.gov/wp-content/uploads/2023/02/M-23-10-DOTGOV-Act-Guidance.pdf){.usa-link--external} for more information.
56-
57-
### Judicial branch federal agencies {.h4}
58-
Domain requests for judicial branch federal agencies, except the U.S. Supreme Court, must be authorized by the director or CIO of the Administrative Office (AO) of the United States Courts.
59-
60-
Domain requests from the U.S. Supreme Court must be authorized by the director of information technology for the U.S. Supreme Court.
61-
62-
### Legislative branch federal agencies {.h4}
63-
64-
#### U.S. Senate {.h5}
65-
Domain requests from the U.S. Senate must come from the Senate Sergeant at Arms.
66-
67-
#### U.S. House of Representatives {.h5}
68-
Domain requests from the U.S. House of Representatives must come from the House Chief Administrative Officer.
69-
70-
#### Other legislative branch agencies {.h5}
71-
Domain requests from legislative branch agencies must come from the agency’s head or CIO.
72-
73-
Domain requests from legislative commissions must come from the head of the commission, or the head or CIO of the parent agency, if there is one.
74-
75-
### Interstate organizations {.h4}
76-
Domain requests from interstate organizations must be authorized by someone in a role of significant, executive responsibility within the organization (president, director, chair, senior technology officer, or equivalent) or one of the state’s governors or CIOs.
77-
78-
### U.S. states and territories {.h4}
79-
80-
#### States and territories: executive branch {.h5}
81-
Domain requests from states and territories must be authorized by the governor or someone in a role of significant, executive responsibility within the agency (department secretary, senior technology officer, or equivalent).
82-
83-
#### States and territories: judicial and legislative branches {.h5}
84-
Domain requests from state legislatures and courts must be authorized by an agency’s CIO or someone in a role of significant, executive responsibility within the agency.
85-
86-
### Tribal governments {.h4}
87-
Domain requests from federally-recognized tribal governments must be authorized by the tribal leader the [Bureau of Indian Affairs](https://www.bia.gov/service/tribal-leaders-directory){.usa-link--external} recognizes.
88-
89-
Domain requests from state-recognized tribal governments must be authorized by the tribal leader the individual state recognizes.
90-
91-
### Counties {.h4}
92-
Domain requests from counties must be authorized by the commission chair or someone in a role of significant, executive responsibility within the county (county judge, county mayor, parish/borough president, senior technology officer, or equivalent). Other county-level offices (county clerk, sheriff, county auditor, comptroller) may qualify, as well, in some instances.
93-
94-
### Cities {.h4}
95-
Domain requests from cities must be authorized by someone in a role of significant, executive responsibility within the city (mayor, council president, city manager, township/village supervisor, select board chairperson, chief, senior technology officer, or equivalent).
96-
97-
### Special districts {.h4}
98-
Domain requests from special districts must be authorized by someone in a role of significant, executive responsibility within the district (CEO, chair, executive director, senior technology officer, or equivalent).
99-
100-
### School districts {.h4}
101-
Domain requests from school district governments must be authorized by someone in a role of significant, executive responsibility within the district (board chair, superintendent, senior technology officer, or equivalent).
102-
103-
We use the [U.S. Census Bureau's definition of school district governments](https://www.census.gov/library/publications/2024/econ/2022isd.html){.usa-link--external}.
37+
{% include 'content-blocks/eligibility_org_types.html' %}
10438

10539
## Request your .gov domain
10640

0 commit comments

Comments
 (0)