About 5 seconds after I start SeaMonkey v2.31, I get a notification from MalwareBytes that it blocked outgoing from local port (variable) to, I kid you not, my external IP, the one on the WAN side of the router that my ISP issues every once in a while. That's on Win7. Nothing special in the Outpost firewall log. On XP - the same thing. So I turned on logging in the firewall. I don't have MBAM pro with its traffic scans on XP. Here, on the same SeaMonkey start, the same router, the firewall (Kerio or Sunbelt) shows it's outbound by TCP to ... my external IP, port 80. Can someone explain this? Why would I be going to http port of the other side of the router? Not sure if this post should be here or in Other... Edit: I forgot to mention, this is a quick, fleeting, affair of SYN_SENT, three times or so (on XP) and then no more.