GµårÐïåñ wrote:A) Does this external ip detection using GoDaddy go through the svchost or through the browser's internal core? Meaning piggy backing on the already allowed traffic of the browser through the firewall.
The external IP detection does not "use GoDadday". It uses my own dedicated servers (3 at this moment, load balanced through a DNS round robin) which respond to https://secure.informaction.com/ipecho
A GoDaddy server is contacted by Firefox to validate the SSL certificate of secure.informaction.com, like it does for any certificate released by GoDaddy's CA.
This means that both the requests (the primary one to secure.informaction.com and the secondary SSL validating one to oscp.godaddy.com) are made by Firefox and are subject to the same (likely less restrictive) rules of any other web browser request.
GµårÐïåñ wrote:B) If inside the browser, then I am fine, since that is configured using the Browser rules configuration, but if using svchost (OS level), then there is a 100% chance its being blocked, how will that adversely affect NoScript's ability to properly function and secure if it can't obtain the external ip? and furthermore is there a specific ip for your server (even if hosted by godaddy) that I can specifically open for NoScript usages only whilst blocking the rest of the ranges.
As I said above, those requests are unlikely to be blocked (otherwise your browser would probably be disfunctional and you couldn't install any XPI from the noscript.net direct links).
You can easily verify whether this feature is working by opening NoScript Options|Advanced|ABE
and checking the detected IP on the top right.
Anyway the secure.informaction.com IPs (which are not hosted by GoDaddy, see above) are 22.214.171.124, 126.96.36.199 and 188.8.131.52.