nl " but this one doesn't resolve for me. I found an article mentioning their v6 Hostname " news. I was curious because I read that Eweka had full IPv6 Support since several years, apparently even since their early days (Like 2008). The IPv6 Test over at claims perfectly working Dual Stack support for my Setup (ISP: Telefonica DE), which I can confirm from other applications. Pinging the Hostname of Newsdemon, an IPv6 Address is resolved without issues, and testing my NewsDemon block account in SABnzbd Wireshark confirms that all Packets are exchanged via IPv6. When pinging eweka's hostname ( ) via cmd I get a response from a resolved Legacy IPv4 Address, v6 enforcing gives me an Error that host " could not be found". So during testing I just found out that my Eweka Usenet Access doesnt work via IPv6, the Network Packets are transported via IPv4 only. so why are usenet providers still offering that? TLS1.2 was introduced in 2008 (14 years ago), and starting from Windows 7 (SP1) and OpenSSL 1.0.1 (2012) it has been supported, so I would say deprecating TLS1.1 and lower would be OK? Those B grades are caused by offering TLS1.1 and TLS1. ?).īut then: how good is the SSL/TLS they offer? offers a guide for "SSL Server Rating Guide", and the tool testssl.sh determines that rating per server.Ī reason for a lower rating is still offering TLS1.1 and TLS1, or being vulnerable to well-known attacks like POODLE or providing low ciphers. I post that on a website, but alas my posts with that URL get banned by moderators (because of "backdoor promoting". I sometimes run a tool to check the TLS/SSL state of well known usenet servers.