The White House’s Office of Management and Budget recently released a list of all domains owned and operated by federal executive agencies. Leveraging a previous tool I had built called Site Inspector which provides information about a domain and its technical capabilities, I imported the list into the content management system WordPress, and created a plugin called Domain Inventory to scan each domain and curate the results. A summary of my preliminary results appears below, as well as a link to the browsable dataset.
The project tracks each Federal Executive .Gov by
- Agency (as provided in the data.gov list)
- Server status (response code, if it is reachable, etc.)
- Non-WWW support (is
www.required to access the site)
- IPv6 Support (is it reachable via next generation technology)
- CDN Provider (do they use a content distribution network, if so what)
- CMS (do they use a content management system, if so what)
- Cloud Provider (are they hosted in the cloud, if so by whom)
- Analytics Source (do they track visitors, if so how)
- HTTPS Support (is the site browsable via the secure HTTPS protocol)
Key Highlights of the Preliminary Results
- Only 73% of domains are live and in use
- Of live domains 80% are accessible without typing the
- Only 10 sites fully support the federally mandated IPv6 standard.
- 87 domains use the Akamai content distribution network.
- 12 are believed to be in the cloud, including 10 in Amazon, and 2 in Rackspace.
- 103 use some form of analytics, with Google Analytics being the most popular, found on 86 domains.
- Drupal is by far the most popular CMS, powering nearly twice as many domains as all other CMSs combined.
- WordPress is the second most popular primary CMS (17), followed by Microsoft SharePoint (13).
- 93% of live domains use no detectable CMS, or use a custom-built solution.
- Slightly more than half of live servers are powered by commercial software.
Please note: This data is to be treated as preliminary and is provided “as is” with no guarantee as to its validity. The source code for all tools used, including the resulting data, is available on GitHub]. If you find a systemic error, I encourage you to fork the code and I will try my best to recrawl the list to improve the data’s accuracy.
Update (10/4): Updated the above statistics (and underlying data) based on an updated domain list published on data.gov and recrawled using the same tools. The above numbers now use the number of live sites (rather than total number of domains) as the denominator for percentages, and excludes approximately 300 domains which simply redirects to other .govs.
Update (October 2013): The original site is no longer available online. You may use the linked resource to recreate the results.
If you enjoyed this post, you might enjoy:
- Securing the Status Quo
- Towards a More Agile Government
- How I over-engineered my home network for privacy and security
- Why open source
- Ten ways to make a product great
- Why WordPress
- Analysis of federal .gov domains, pre-Biden edition
- Twelve tips for growing communities around your open source project
- Four characteristics of modern collaboration tools
- 19 reasons why technologists don't want to work at your government agency
- Will Federal Contracting Officers Soon Have Their Heads in the Clouds?
Ben Balter is a Staff Technical Program Manager at GitHub, the world’s largest software development network. Previously, as the Senior Product Manager overseeing the platform’s Trust and Safety efforts, Ben shipped more than 500 features in support of community management, privacy, compliance, content moderation, product security, platform health, and open source workflows to ensure the GitHub community and platform remained safe, secure, and welcoming for all software developers. Before joining GitHub’s Product team, Ben served as GitHub’s Government Evangelist, leading the efforts to encourage more than 2,000 government organizations across 75 countries to adopt open source philosophies for code, data, and policy development. More about the author →