There are a relatively small number of infrastructure domains to which a
huge number of our users are exposed:

doi.org
handle.net
...

In my view pretty much anything which can be used as a lever to get them to
become more secure has to be a good idea, since these are websites which we
have basically no choice about exposing our users to.

cheers
stuart

--
...let us be heard from red core to black sky

On Wed, Feb 3, 2016 at 6:08 AM, Eric Hellman <[log in to unmask]> wrote:

> The folks at 18F offered to set up a dashboard for the library world like
> https://pulse.cio.gov/https/domains/
>  <https://pulse.cio.gov/https/domains/>
>
>  <https://pulse.cio.gov/https/domains/>
> b <https://pulse.cio.gov/https/domains/>ut we thought it might be too
> depressing just now.
>
>  <https://pulse.cio.gov/https/domains/>
>
>  <https://pulse.cio.gov/https/domains/>
> > On Feb 1, 2016, at 2:21 PM, Stuart A. Yeates <[log in to unmask]> wrote:
> >
> > Does anyone know of an alerting service for HTTPS certs? Ideally one that
> > covers both soon-to-expire certs and
> > now-below-recommended-security-settings certs?
> >
> > cheers
> > stuart
> >
> > --
> > ...let us be heard from red core to black sky
> >
>
>