Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
llnw is Limelight Networks, it's a content delivery network -- they have access points globally. So Italy is probably just the closest one to you, or the one chosen at the time you started Ninja.
If you look at futures.io (formerly BMT) pages you'll see a CDN here too, and the CDN node for you will be different than me, as I am in Dallas and you are not. futures.io (formerly BMT) uses Amazon S3 CloudFront and they have nodes worldwide. So what you are seeing is someone who has contracted with llnw for a service, all you see is that end point, you would need to research it more (might be able to find the customer by examining the CNAME record) to see who or what it really is.
We're going but the CDN changes IP's frequently, like in Dallas there are many IP's and edge nodes. I am sure is same in Europe -- so each time you ping cdn.bigmiketrading.com you will see a different IP in a small group of IP's in rotation for your region. You also shouldn't focus on where the IP address is registered or where it shows on some IP registry geolocation map service --- you should look at the ping time as latency is what the CDN is all about. Of course here the primary purpose of this thread is not CDN, but security. Just a quick guesstimate from the A-record you posted above, "fra2" most likely means Frankfurt since you are in Germany, and the traffic is coming from your region.
Here is a small utility for measuring world wide latency. Here cdn.bigmiketrading.com is just a CNAME. Amazon CloudFront will then handle deciding a geographically appropriate destination region, and then from there it will go to a pool of servers in that region. The same is true of Limelight in your NT example.
Have changed my post, while you were posting yours, as I checked the servers via Ping, Now also have checked the other server from Limelight Network, which is used by NinjaTrader, It is also located in Frankfurt, not in Italy. The information from IP address - The best IP address tools at IPaddress.com is not reliable.
That hat is my native attire design we call "Abeti-aja"; which means dog's hears, 'cos it is dog's hears-like; but we use real clothing materials (not foil) to sew it. Our Hunters wear it for hunting in the bush. That should really protect you
I know of someone who dedicates one computer just for trading - no internet or email at all. He uses a whitelist in his firewall to allow only those sites required for trading, but I don't believe that he uses NT. You might try disabling some of the questionable IP addresses to see if if impacts your ability to log-in, obtain data, etc.
I think that this is rather harmless, to be honest. I was just astonished by the complexity, as I could not imagine that NT7 would establish 6 different connections into the internet prior to connecting.
How do you patent a software concept like a static DOM? There has to be a way to implement the same functionality around the restrictions of that patent, something like scrolling the dynamic DOM 1 row and then back to the original position, or something like that. I'm sure there is a way to get around that patent. And, why doesn't NT just drop the static DOM and be done with it? If sounds like more trouble then it's worth, given that only a minute percentage of users are using it. I think every company and product using the static DOM and paying TT, should just drop the static DOM altogether and screw TT over good.
Just a guess that it is parsing an XML file. The top of XML files are stamped with their version info with a w3 URL and the coder is taking it literally by reading the format from w3.
but the CDN changes IP's frequently, like in Dallas there are many IP's and edge nodes. I am sure is same in Europe -- so each time you ping cdn.bigmiketrading.com you will see a different IP in a small group of IP's in rotation for your region. You also shouldn't focus on where the IP address is registered or where it shows on some IP registry geolocation map service --- you should look at the ping time as latency is what the CDN is all about. Of course here the primary purpose of this thread is not CDN, but security. Just a quick guesstimate from the A-record you posted above, "fra2" most likely means Frankfurt since you are in Germany, and the traffic is coming from your region.
