NoScript is trying to connect to w<x>.hackademix.net

Ask for help about NoScript, no registration needed to post
AnotherMember
Posts: 2
Joined: Fri Jan 13, 2017 11:05 am

NoScript is trying to connect to w<x>.hackademix.net

Post by AnotherMember »

Hi all,

This is my very first post.
I have been searching for this issue but could not find a topic at this forum about my issue.
I've noticed that NoScript is trying to access several web hosts from hackademix.net
My firewall warns me with a list of host that are being blocked.

Time: Process: Direction Protocol Remote address: Port: Action:
11:24:05 FIREFOX.EXE OUT TCP w2.hackademix.net 443 Blocked by IP Block list
11:24:05 FIREFOX.EXE OUT TCP w1.hackademix.net 443 Blocked by IP Block list
11:24:05 FIREFOX.EXE OUT TCP w4.hackademix.net 443 Blocked by IP Block list
11:24:05 FIREFOX.EXE OUT TCP w3.hackademix.net 443 Blocked by IP Block list
11:24:05 FIREFOX.EXE OUT TCP w2.hackademix.net 443 Blocked by IP Block list
11:24:05 FIREFOX.EXE OUT TCP w1.hackademix.net 443 Blocked by IP Block list
11:24:05 FIREFOX.EXE OUT TCP w5.hackademix.net 443 Blocked by IP Block list
11:24:05 FIREFOX.EXE OUT TCP w4.hackademix.net 443 Blocked by IP Block list
11:24:05 FIREFOX.EXE OUT TCP w3.hackademix.net 443 Blocked by IP Block list

This behavior occurs after starting op Firefox.

Questions:
Is this normal behavior?
Why is NoScript 'phoning home'?
Is it OK to keep the sites blocked (Does it interfere with NoScript functionality)?

Can someone clarify this.
Thanks in advance.
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:45.0) Gecko/20100101 Firefox/45.0
barbaz
Senior Member
Posts: 11141
Joined: Sat Aug 03, 2013 5:45 pm

Re: NoScript is trying to connect to w<x>.hackademix.net

Post by barbaz »

Your firewall is messing with you. Do a DNS lookup of secure.informaction.com, then do DNS lookup of those hackademix.net domains.
AnotherMember wrote:Why is NoScript 'phoning home'?
NoScript is contacting https://secure.informaction.com/ipecho/ to lookup your WAN IP. It's part of NoScript's protection, and it's normal and expected.
AnotherMember wrote:Is it OK to keep the sites blocked
If you're going to do that, you might as well also go to NoScript Options > Advanced > ABE, and un-check "WAN IP ∈ LOCAL". That should prevent NoScript from making the connection in the first place.
AnotherMember wrote:(Does it interfere with NoScript functionality)?
Yes. You lose the protection noted above.
*Always* check the changelogs BEFORE updating that important software!
-
AnotherMember
Posts: 2
Joined: Fri Jan 13, 2017 11:05 am

Re: NoScript is trying to connect to w<x>.hackademix.net

Post by AnotherMember »

Hi barbaz,

Many thanks for replying.
barbaz wrote:Your firewall is messing with you. Do a DNS lookup of secure.informaction.com, then do DNS lookup of those hackademix.net domains.
I did the suggested DNS lookup and I learned that both secure.informaction.com and hackademix.net use the same IP's.
So it's not my firewall messing with me, it's a matter of which name was resolved first.

barbaz wrote:NoScript is contacting https://secure.informaction.com/ipecho/ to lookup your WAN IP. It's part of NoScript's protection, and it's normal and expected.
.....If you're going to do that, you might as well also go to NoScript Options > Advanced > ABE, and un-check "WAN IP ∈ LOCAL". That should prevent NoScript from making the connection in the first place.
OK, so ABE is using these IP's for doing it's job.
Question: I'm using DNSsec. Is ABE needed in such case?
Mozilla/5.0 (Windows NT 6.1; rv:45.0) Gecko/20100101 Firefox/45.0
barbaz
Senior Member
Posts: 11141
Joined: Sat Aug 03, 2013 5:45 pm

Re: NoScript is trying to connect to w<x>.hackademix.net

Post by barbaz »

AnotherMember wrote:Question: I'm using DNSsec. Is ABE needed in such case?
I'm using a sledgehammer. Is a power drill needed in such case?

IIUC, DNSsec is a means to prevent forged DNS responses. ABE, by default, is designed to protect your local network from access by webpages. Both useful protections, but quite different.

Also, a webpage can still try to connect to your public IP, independently of DNS.

So I would suggest to browse to your public IP and see what happens. If it doesn't respond, you're probably safe to turn off the WAN IP ∈ LOCAL feature.
*Always* check the changelogs BEFORE updating that important software!
-
Post Reply