Boring answer, but it's probably a badly configured load balancer.


Mark

On Wed, Apr 1, 2015 at 2:35 PM, Georgi Guninski <guninski@guninski.com> wrote:
On Wed, Apr 01, 2015 at 01:37:27PM +0100, Mark Steward wrote:
> $ curl -i defcon.org:443
> HTTP/1.0 503 Service Unavailable
> ...
>

Same for http://www.defcon.org/

Is this a sound April first joke?

>
>
> On Wed, Apr 1, 2015 at 1:18 PM, Georgi Guninski <guninski@guninski.com>
> wrote:
>
> > On Wed, Apr 01, 2015 at 02:57:05PM +0300, Georgi Guninski wrote:
> > > As of Wed AprĀ  1 11:54:42 UTC 2015 can't browse:
> > > https://www.defcon.org/html/links/dc-transparency.html
> > >
> > > Other people can't too.
> > >
> > > Is it only us?
> >
> > $ openssl s_client -connect www.defcon.org:443
> > CONNECTED(00000003)
> > 19658:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake
> > failure:s23_lib.c:188
> >
> > from at least 2 distinct IPs.
> >
> >