Worst case example of a proposed DID endpoint?

I'm seeing an example of a real-world or proposed DID endpoint that is
either quite complex (lots of parameters), or has multiple values (multiple
endpoints), or is a non http endpoint, or risks unique identity
correlation. Ideally all of these!

It doesn't have to be a current DID method, but it should be something that
I can reference.

My goal is to show how to transform that example into a safe,
non-correlatable commitment for that endpoint.

Any suggestions of an example?

-- Christopher Allen