Probably not new - 127.0.0.1:port# at every site

[WTP]

...in fact, I think it's a FAQ, though I don't quite get it - Everywhere I go, either my software or hardware firewalls, my ISP or Something Scary Under the Bed generates an HTTP://127.... like the above, and NoScript reacts with horror. Since I seem to remember something about the address being a loopback code, 1) why is NoScript set to be so scared of it and 2), since it is, should I just take it lightly, either white-listing it or ... could it actually be something to worry about?

[GµårÐïåñ]

This was answered a while back and the issue seems to have been closed but for anyone who might come across a similar issue in the future, keep in mind also that some applications modify your host file which CAN have a lot of 127.0.0.1 loopbacks to prevent access to certain addresses. In fact many malware and spyware utilities, such as Spybot S&D and Adaware, will actually insert a list of known blacklisted "baddie" sites into the host file referenced to 127.0.0.1 as a loopback to effectively block access to them on the system level. They also tend to lock the host file to prevent malware from modifying it. So either make sure that the host file is protect against modification and check what's in it to make sure you are not being hijacked by having say google.com go to somebadsite.com instead. That may be what's triggering the "alarms" too. Hope this helps someone.