[elliottinvent]

I really appreciate the detailed feedback here, I somehow missed it.

I don't think site ownership data is something to be concerned about since we'll only publish that if we find it on the website. So if a company doesn't have a website or has no company details on their website then we won't populate a record for it. So it's unlikely NUM would make it any easier to name a domain registrant in a law suit than the website would.

I think a module that lists a company's products or services could have some really interesting applications.

NUM is of course compatible with all DNS implementations, so a local DNS zone mycompany.local could hold it's NUM records in _num.mycompany.local – I think this has got a lot of potential for large companies and public sector organisations.

You're right that great care needs to be taken when scraping website data and publishing it to the DNS to prevent inadvertent publishing data that was intended to be private or was published to the web before spam was such an issue, also for GDPR reasons. It's unavoidable that making machine-readable data open and freely available will result in it being consumed through automated means and it's likely that some of this data will be used in ways which are undesirable.