Thank you for the suggestion.
I am familiar with Virustotal and have used it in the past to analyze files but didn't realize that it can also analyze urls. Good thing to know. A troubleshooting tool that I can use in the future.
I submitted both the primary url and the url that the primary redirects to (the host of the connection while the Kamo lock is taking place), performed a reanalyze to make more current analysis, and neither url had a single hit. I don't know how deep the analysis is. For all I know, Kamo is objecting to another url redirect with in the page of the connection, a url that I have no knowledge of. The fact is that a given page contains a truckload of host connections that are being accessed to build the page, and I have no way of knowing which, if any, are the problem.
I am hesitant to post here the urls that are at issue in this public arena for you to try. If they are Kamo false positives, I do not wish that to reflect on the company that I am a customer of.
I recognize this is a community forum and you may or may not have direct communication with the Kamo support/development staff, but I would like to make them aware of the need for a feature to be added to the program that presents a warning notification or log entry that identifies the specific url/connection that is being blocked and what action by that web page is the reason for the block.
I employ other security programs and they all provide those functions and therefore it is very simple to make a judgement call about the validity of the block and provides me the customer with enough information to ask the target company to resolve the issue if they want my business.
I am also going to have have a closer look at how Kamo is functioning. I was aware that it was doing some magic behind the scenes to make it more difficult to identify my browser/location but I was not aware that it was capable of actively blocking a site, and without notification at that.
In the meantime I have several workarounds. I have several computing platforms, pc and mobile, that are not running Kamo that continue to provide access to the site in question; and I have the option of disbling Kamo temporarily/permanently on my primary/preferred computer.
Again, thank you for your assistance.