I recently had a subtle production bug introduced by creating more than one Ninject binding for a given interface to the same instance.
I wanted to be able to see what bindings existed for a given interface, but Ninject does not provide an easy way to do that.
This gist contains an extension method I wrote (with the help of a StackOverflow article) to acquire this information.
As this code relies on using reflection to get a private member variable, this code is brittle in the face of a change in the implementation of KernelBase. In the meantime, it works on my machine.