The general legal precedent here as I see it is that domain registrars are generally not liable for content hosted on domains they sell, nor are they responsibl

The general legal precedent here as I see it is that domain registrars are generally not liable for content hosted on domains they sell, nor are they responsible for enforcing them. They usually will cooperate to take down sites if they are obvious phishing attacks, or if there is a court order, but abuse management through this channel is very rare. More often than that, they refer any reports to the owner of the IP address the domain is pointing to. The "entry point" for almost all abuse (DMCA/phishing/whatever) reporting is whomever holds the abuse contact for the owner of the IP addresses. They simply do a lookup on the IPs with ARIN (or APNIC or RIPE depending on where the IPs are managed), and then email that abuse contact. We've had plenty of issues with this approach, now that Neocities hosts a lot of sites. I've recently acquired an IP block largely for the purpose of having control over this abuse contact, so that we can directly receive abuse emails. Some providers also do SWIP, which allows you to be the contact for a specific IP address in their block, but not all providers will do this (Ramnode does - DigitalOcean does not. I don't think Google Cloud or AWS do this either, but let me know if they do). Bigger organizations that need this level of control go this route - you'll note that even companies like Uber use their own IP addresses instead of throwing it up on a cloud providers'. If you're planning to host a lot of user submitted web sites or content, this isn't the easiest/cheapest route, but it's the route you want to seek. I'm available for consulting on this if you'd like to pursue this for your organization, I've become quite the expert on the topic out of necessity. :)