What does Pulse measure about federal domains?
What federal domains are being measured?
Currently, Pulse uses the official
.govdomain list as a starting point, and focuses on domains owned by federal agencies. This also includes a few domains ending in
.fed.us. Domains ending in other suffixes, such as
.us, are not included at this time.
Subdomains, such as
travel.state.gov, are not measured at this time.
What is HTTPS, and why does Pulse measure it?
HTTPS provides a secure connection across the internet between websites and their visitors, and is becoming the new baseline for public web services across the internet. As part of this shift, the U.S. federal government is in the process of transitioning entirely to HTTPS.
Note that HTTPS generally does not affect whether a website is vulnerable to hacking. For more information on what HTTPS does (and doesn't do), visit the HTTPS FAQ.
What is the Digital Analytics Program, and why does Pulse measure participation?
The Digital Analytics Program is an important federal government project that gives federal agencies and the public a window into how people use government services.
Any publicly accessible federal website in the executive branch can participate in the Digital Analytics Program (DAP). The easiest way for federal websites to get started is to send the DAP team an email.
What is Accessibility, and why does Pulse measure it?
For websites, accessibility means that pages should be built according to certain standards that ensure, for example, that a visually impaired user accessing a government site through a screen reader will be able to navigate and access the same information available to a non-visually-impaired user.
The Accessibility Report measures adherence to best practices for implementing accessible websites in the federal government.
The US Government’s mission is to serve the needs of all its citizens, including the approximately 60 million who live with disabilities.
When was the data last updated on Pulse?
All data was last measured on March 24, 2017.
Where can I send feedback?
For questions specific to HTTPS deployment, you may wish to open an issue on the HTTPS-Only Standard's GitHub repository.
Your information about my domain is wrong! Can you please fix it?
If you just changed something about your domain to address an issue on Pulse, be aware that data does not yet automatically refresh on Pulse, and so there may be a delay before your domain's information updates.
If you see a mistake, please send an email to email@example.com and it will be investigated.