No, there is no mention of port scanning in the firewall logs for this address.

(I do see other IP addresses where the “Rule” says “IP Blocked”, and if I change the Firewall Logs display to show Rules, I see where those IPs were blocked for port scanning and I really don’t care about those IP addresses; but I don’t see any rules set up there against 63.245.215.80, the bugzilla.mozilla.org site I am having difficulties with.)

This is at home, going through an Arris TG862G (a combined cable modem / router leased from Comcast). Normally I have the computer connected to it via an Ethernet cable. I did try wireless and the only difference in the firewall logs is the change in the local IP address (10.0.0.2 being the local Ethernet port on the computer; 10.0.0.5 being the address assigned to the local WiFi port).

The log shows that the packet is being blocked going out, and that it is going out from “System”, not “Chrome” (my primary browser), not “Firefox” (my former primary browser but still installed and still kept up to date).

For whatever it’s worth, Ping works and gets replies and resolves bugzilla.mozilla.org to the same IPv4 address that the firewall is blocking for an outgoing https request.

If you really think I need to try another location, I think I can do it, but this desktop isn’t exactly light. I can switch antivirus software faster than I can transport the computer, monitor, keyboard, and mouse to another location.