# Analysis of Federal Executive .govs (Part Deux)

**TL;DR:** Nearly three years after my first analysis, I resurrected Site Inspector to see how federal executive .govs have changed: about a quarter fewer domains, one in four supporting SSL but only one in ten enforcing it, and 74 sites still running IIS 6.0. Check my work, and if you find an error, open an issue or submit a pull request.

Published 2014-07-07 · [View on Ben Balter's site](https://ben.balter.com/2014/07/07/analysis-of-federal-executive-domains-part-deux/)

---

In September 2011, in response to the Office of Management and Budget releasing [a list of all federal executive domains](https://github.com/GSA/data/blob/2ccdcb73bc6f/dotgov-domains/current-federal.csv), I built a small tool called [Site Inspector](https://github.com/benbalter/Site-Inspector) and created [a quick analysis of the technology and capabilities that power each federal domain](https://ben.balter.com/2011/09/07/analysis-of-federal-executive-domains/).

Nearly three years later, I [resurrected that tool](https://github.com/benbalter/site-inspector), albeit a bit smarter, and, using [the latest list](https://web.archive.org/web/20160311191728/https://explore.data.gov/Federal-Government-Finances-and-Employment/Federal-Executive-Agency-Internet-Domains-as-of-06/ku4m-7ynp?), thought I'd take a look at how things have changed in the time since. Efforts like the Digital Strategy and Open Data Policy have surely moved the needle, right? RIGHT?!

Here's what changed:

- Approximately a quarter reduction in number of .govs (`1640 - 1229 = 411`)
- 1000 of those domains are live ([about 83%](https://web.archive.org/web/20140722085457/http://dotgov-browser.herokuapp.com/domains?live=true), up from 73%)
- Of those live domains, [about 83%](https://web.archive.org/web/20140720034430/http://dotgov-browser.herokuapp.com/domains?non_www=true) are reachable without the `www.` prefix, a negligible increase
- [Only 64 sites](https://web.archive.org/web/20140722085446/http://dotgov-browser.herokuapp.com/domains?ipv6=true) return an `AAAA` record, the first step towards IPv6 compliance (up from 10)
- [250 sites](https://web.archive.org/web/20140720041608/http://dotgov-browser.herokuapp.com/domains?ssl=true), approximately one in four, support SSL (HTTPS), but only [one in ten](https://web.archive.org/web/20140720034410/http://dotgov-browser.herokuapp.com/domains?enforce_https=true) enforce it
- 87% of sites use no detectable content management system, about a 5% decrease
- Of those with a CMS, Drupal is still by far the most popular (100+ sites), with [WordPress powering 14 sites](https://web.archive.org/web/20140720040651/http://dotgov-browser.herokuapp.com/domains?cms=wordpress) and [Joomla powering 7](https://web.archive.org/web/20140720040623/http://dotgov-browser.herokuapp.com/domains?cms=joomla)
- [One in four sites](https://web.archive.org/web/20140720040559/http://dotgov-browser.herokuapp.com/domains?analytics=google_analytics) use Google Analytics (almost a three-fold increase), with a handful of sites using Facebook insights
- Roughly a third of sites advertise that they are powered by open source server software (for example, [Apache](https://web.archive.org/web/20140720041504/http://dotgov-browser.herokuapp.com/domains?server=Apache), [Nginx](https://web.archive.org/web/20140720034506/http://dotgov-browser.herokuapp.com/domains?server=nginx)), slightly more than those that are powered by closed source server software (for example, Microsoft, Oracle, Sun)
- [74 sites](https://web.archive.org/web/20140722085513/http://dotgov-browser.herokuapp.com/domains?server=Microsoft-IIS%2F6.0) are still running IIS 6.0, a ten+ year old server
- HHS is the biggest perpetrator of domain sprawl with [110 domains](https://web.archive.org/web/20140722083919/http://dotgov-browser.herokuapp.com/domains?agency=Department%20of%20Health%20And%20Human%20Services), followed by GSA ([105](https://web.archive.org/web/20140720034323/http://dotgov-browser.herokuapp.com/domains?agency=General%20Services%20Administration)), Treasury ([92](https://web.archive.org/web/20140720034306/http://dotgov-browser.herokuapp.com/domains?agency=Department%20of%20the%20Treasury)), and Interior ([89](https://web.archive.org/web/20140720034248/http://dotgov-browser.herokuapp.com/domains?agency=Department%20of%20the%20Interior))
- [142](https://web.archive.org/web/20140720034602/http://dotgov-browser.herokuapp.com/domains?slash_developer=true) domains have a `/developer` page, [171](https://web.archive.org/web/20140722083929/http://dotgov-browser.herokuapp.com/domains?slash_data=true) domains have a `/data` page, [146](https://web.archive.org/web/20140720034350/http://dotgov-browser.herokuapp.com/domains?data_dot_json=true) domains have a `/data.json` page, roughly 15%
- [16 domains](https://web.archive.org/web/20140722083924/http://dotgov-browser.herokuapp.com/domains?redirect=www.whitehouse.gov) redirect to whitehouse.gov, [10](https://web.archive.org/web/20140720041307/http://dotgov-browser.herokuapp.com/domains?redirect=justice.gov) to justice.gov, [9](https://web.archive.org/web/20140722085506/http://dotgov-browser.herokuapp.com/domains?redirect=consumerfinance.gov) to consumerfinance.gov and [8](https://web.archive.org/web/20140720034452/http://dotgov-browser.herokuapp.com/domains?redirect=www.usa.gov) to usa.gov

Math's never been my strong point, so I highly encourage you to check my work. You can browse the full results at [dotgov-browser.herokuapp.com](https://web.archive.org/web/20140720040527/http://dotgov-browser.herokuapp.com/domains) or check an individual site (.gov or otherwise) at [site-inspector.herokuapp.com](https://web.archive.org/web/20160311202809/https://site-inspector.herokuapp.com/).

*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](https://github.com/benbalter/site-inspector). If you find an error, I encourage you to [open an issue](https://github.com/benbalter/site-inspector-ruby/issues/new) or [submit a pull request](https://guides.github.com/introduction/flow/).*