Defaults.Exposed

88,740 .gov domains, eight years after the BOD 18-01 deadline

The November 2026 census holds 88,740 names under .gov, and 71,738 of them are dead. When the scan asked for their name servers, the answer was a definitive empty one. 71,733 of those dead names are missing from the list of registered .gov domains that CISA publishes. The census’s source lists still carry them, and the registry doesn’t. The live side matches the registry closely. In its last snapshot before the scan, the registry listed 16,999 .gov domains, and 16,469 of them are among the census’s 16,480 live, graded .gov domains.

That is why this page leads with live domains. On the census’s standard base, graded plus dead, 86.8% of .gov scores an F, and dead names make up 93.7% of those Fs. Among the 16,480 live, graded .gov domains the F share is 29.4%.

Most .gov names in the census are dead, and almost none of those are registered

Figure 1. The census holds far more .gov names than the registry lists, and the dead names make up the difference. The live, graded names and the registry are almost the same set of domains.

CISA’s Binding Operational Directive 18-01 binds one group of .gov holders: federal executive branch agencies. It gave them until 16 October 2018, a little over eight years before this census, to publish a DMARC (Domain-based Message Authentication, Reporting and Conformance) policy of p=reject on every second-level domain. In this census, 89.6% of the 1,111 live federal executive .gov domains publish p=reject. Among the 1,359 live state and territory domains, which the directive does not cover, 14.5% do.

DMARC p=reject by who holds the .gov domain

Figure 2. DMARC p=reject by domain type in CISA’s registry list, with the number of live, graded domains in each group in brackets.

What the directives asked for

Four federal instructions set the controls this page measures. Each is addressed to federal executive departments and agencies or their chief information officers.

State, county, city and tribal governments hold most registered .gov domains, and none of the four applies to them.

.gov beside .edu and .us

Two neighbours give a reference point. .edu has no federal mandate of this kind, and .us is the United States country-code domain. The first table shows what the census holds in each, and why .gov needs a different base from the other two.

.gov.edu.us
Names in the census88,7407,0701,416,487
Dead (no name servers)71,73804,977
Alive17,0027,0701,411,510
Live and graded16,4806,8251,338,541
Graded plus dead, the census’s standard base88,2186,8251,343,518

An alive domain that isn’t graded answered the scan without giving the checks enough to grade, or never answered at all. How the domains were counted explains each state.

The second table uses one base in every column: the live, graded domains of that TLD (Top-Level Domain).

Share of live, graded domains.gov.edu.us
Domains in the base16,4806,8251,338,541
Publish a DMARC record59.7%74.4%23.8%
DMARC p=reject19.1%16.2%7.3%
Publish an SPF record81.4%83.5%48.3%
Serve HTTPS (Hypertext Transfer Protocol Secure)78.4%89.5%61.1%
HSTS header, or on the preload list40.0%24.0%9.6%
DNSSEC signed13.2%4.9%3.0%
IPv6 address on the apex20.1%20.9%14.3%
Grade F29.4%22.1%79.2%

.gov, .edu and .us on the same controls

Figure 3. The seven controls in the table above, each as a share of that TLD’s live, graded domains.

Taken as a whole, live .gov sits closer to .edu than to .us. .edu is ahead on publishing a DMARC record, SPF, HTTPS and IPv6. .gov is ahead on p=reject, HSTS and DNSSEC. .us trails both on every row. The zone-wide .gov figures also blend the one group the directives bind with the much larger groups they don’t, and the registry’s domain types pull them apart.

.gov by who holds it

CISA’s public dotgov-data list gives a domain type for every registered .gov domain. Joined to the census on the domain name, it splits the live, graded .gov domains into the groups below. The two count columns come first. Every share after them uses the same base: the live, graded domains in that row.

Domain typeRegisteredLive and gradedp=rejectSPFHTTPSHSTS or preloadDNSSECIPv6
Federal Executive1,1741,11189.6%92.3%81.4%77.0%84.4%50.5%
State or territory1,4851,35914.5%50.8%73.4%31.2%14.3%16.6%
County3,0522,98017.7%83.2%75.0%45.4%9.2%17.7%
City9,6119,40612.4%85.2%80.9%36.1%5.6%18.1%
Tribal29328218.4%84.4%68.1%35.8%3.2%11.0%
Federal Legislative and Judicial14513528.9%57.8%68.1%25.9%76.3%31.1%
All other types1,2391,19614.2%74.6%75.3%35.4%9.9%18.6%
All registered .gov16,99916,46919.1%81.5%78.5%40.0%13.2%20.1%

“All other types” covers special districts, election offices, school districts, interstate bodies and two domains typed only as Federal.

Federal executive domains lead every column. Their p=reject share is 89.6%. State, county, city and tribal domains sit between 12.4% and 18.4%. DNSSEC shows the same split: 84.4% of federal executive domains are signed, against 3.2% to 14.3% for the four non-federal groups. Legislative and judicial branch domains are federal and outside BOD 18-01. On p=reject they sit between the executive branch and the non-federal groups, at 28.9%. On DNSSEC they are nearer the executive branch, at 76.3%.

Federal executive domains against the four non-federal groups

Figure 4. For each control, the dot is the federal executive branch and the grey bar runs from the lowest to the highest of the state, county, city and tribal groups.

Few domains have all six controls in place. A domain passes all six here if it publishes p=reject and SPF, serves HTTPS, has HSTS by header or preload, is signed with DNSSEC and has an IPv6 address on the apex. 437 live .gov domains pass all six, and 392 of them are federal executive.

The census shows where the gap is. It can’t show why.

The federal executive branch, read against the directive

The registry lists 1,174 federal executive .gov domains, and every one of them is in the census. 1,111 are live and graded, 2 are dead and 61 were unreachable or could not be graded. The table reads the 1,111 live, graded domains against the directive’s own wording where the census can see it.

Federal executive, live and gradedDomainsShare
DMARC p=reject99589.6%
p=reject with no weaker sp= and pct at 10098888.9%
reports@dmarc.cyber.dhs.gov in rua=95285.7%
SPF record1,02692.3%
Serve HTTPS90481.4%
Serve HTTPS and redirect HTTP (Hypertext Transfer Protocol) to it67861.0%
HSTS header with max-age of a year or more62055.8%
On the HSTS preload list65859.2%
Either of the two rows above84976.4%
DNSSEC signed93884.4%
IPv6 address on the apex56150.5%

The second row uses the stricter form CISA’s guidance describes for the deadline: p=reject at 100 percent, with no subdomain policy weaker than reject. It lowers the figure by less than a point.

HSTS needs two rows because the directive accepts either route. The last row counts a header only when its max-age is a year or more, so it comes to 76.4% where the type table, which counts any HSTS header, has 77.0%. CISA’s page on the directive says preloading a domain is technical compliance with its HTTPS requirement, and that the .gov registry began preloading new federal .gov domains automatically in 2017. According to get.gov, every newly registered .gov domain is now preloaded, and the registry intends to preload the .gov top-level domain as a whole. On the Chromium list it hadn’t yet: the list carried no entry for .gov itself, and 5,059 entries for individual .gov domains. Across all live .gov domains, 18.4% send an HSTS header, 28.4% are preloaded, and 40.0% have one or the other.

What the census can and can’t see

For the grade shares of every TLD on the census’s standard base, see the TLD statistics page. The DMARC pillar explains what p=reject does to spoofed mail, and HSTS explains the header and the preload list.

See your own

The free scan reads any domain live, .gov or otherwise, on the same checks the census uses, including DMARC, SPF, HTTPS, HSTS, DNSSEC and IPv6.

Figures from the defaults.exposed census, data as of 2 November 2026. Domain types are from CISA’s public dotgov-data list and preload status from the Chromium HSTS preload list, neither of them census data. Census numbers move every month; the current values are on the census data page.