On Nov 10, 2018, at 06:35, Lloyd Wood <lloyd.wood=40yahoo.co.uk@xxxxxxxxxxxxxx> wrote: > > Is there any particular reason www.irtf.org appears > to be unreachable? WFM. > (over IPv4. Haven’t tried IPv6, which noone uses...) If you cared to acquire more knowledge about this (e.g., [1].[2],[3]), you would be surprised. (In this case, I am too lazy to find out whether www.irtf.org came via a stagecoach or via today’s IP.) Grüße, Carsten [1]: http://www.worldipv6launch.org/major-mobile-us-networks-pass-50-ipv6-threshold/ [2]: https://www.google.com/intl/en/ipv6/statistics.html#tab=ipv6-adoption [3]: https://www.google.com/intl/en/ipv6/statistics.html#tab=per-country-ipv6-adoption OBTW, $ curl -I www.irtf.org HTTP/1.1 301 Moved Permanently Date: Sat, 10 Nov 2018 00:23:23 GMT Server: Apache Strict-Transport-Security: max-age=16070400; includeSubDomains Location: https://www.irtf.org/ Cache-Control: max-age=0 Expires: Sat, 10 Nov 2018 00:23:23 GMT Content-Type: text/html; charset=iso-8859-1 So we do “have” it, but of course it redirects to https. And then: $ /usr/bin/curl -I https://www.irtf.org/ HTTP/1.1 301 Moved Permanently Date: Sat, 10 Nov 2018 00:27:46 GMT Server: Apache Location: http://irtf.org/ Content-Type: text/html; charset=iso-8859-1 As it should be. (Except that the copy of curl at hand doesn’t accept the cert chain, so I have to switch to another copy. Standard fare.)
