I fully agree, and even with all these points I don't think it's likely.
1. You should be running your own authoritative DNS, it's not hard. The only thing that can really happen to you is your registrar pulling your domain name, so you need to have a bunch registered piratebay-style. You should also own your IP space but that can be a bit pricey -- but once you own it it basically can't ever be revoked and you can advertise it to whoever you wish.
2. I sincerely doubt Let's Encrypt / ISRG would blacklist a domain name for cert issuance. Even if they did there's a whole lotta roots in the trust stores, I'm sure you'd find an issuer happy to make you a cert for a fee.
3. I deal with T1/T2 carriers in $dayjob and I promise they don't give a triangular shit about what you push through their pipes, given the constant stream of phishing/spam/ddos/malware they're happy to carry as long as someone pays the bills.
1. You should be running your own authoritative DNS, it's not hard. The only thing that can really happen to you is your registrar pulling your domain name, so you need to have a bunch registered piratebay-style. You should also own your IP space but that can be a bit pricey -- but once you own it it basically can't ever be revoked and you can advertise it to whoever you wish.
2. I sincerely doubt Let's Encrypt / ISRG would blacklist a domain name for cert issuance. Even if they did there's a whole lotta roots in the trust stores, I'm sure you'd find an issuer happy to make you a cert for a fee.
3. I deal with T1/T2 carriers in $dayjob and I promise they don't give a triangular shit about what you push through their pipes, given the constant stream of phishing/spam/ddos/malware they're happy to carry as long as someone pays the bills.