@easyDNS: Is that an old ongoing case? Everywhere in the document they're using 2016.

It seems quite funny that they started that in 2016 and using a judgment from 2017 in 2019...