12 karma · joined February 24, 2013
Looks like their IP block is in the Netherlands when I check whois w/ ripe.net (https://apps.db.ripe.net/search/query.html).
The ip block for dot.tk is 213.206.98.160 - 213.206.98.175.
When I check the IP of where the tracert stops at IS Core Network in the Netherlands.
Maybe there is a certain router that is down in which I can't hop to.
Looks like (IS Core Network in the Netherlands) is cloud hosting.
I tweeted the cloud hosting company with the issue and info.
IsItUp is now showing www.dot.tk (54.230.206.33) and dot.tk both as being up. I still can't get to it yet.
Looks like a lot traffic over there: http://www.akamai.com/html/technology/dataviz1.html, but couldn't really see anything causing my issue yet.
Verified that someone else out there on Twitter has the same issue. Yeah, I'm not crazy! :P
And this is just cool: http://cybermap.kaspersky.com/
So now isitup.org shows dot.tk up at an ip of 213.206.98.165. It shows www.dot.tk as being down.
But then I tried this command and it echoed "vulnerable". env var='() { ignore this;}; echo vulnerable' bash -c /bin/true
Like for instance, in the bundle.js file there is a line of code that has this "$window.location.origin + '/config.json'"
the window.location.origin is not supported in IE. You may want to add something like this to your javascript for IE support:
if (!window.location.origin) { window.location.origin = window.location.protocol + "//" + window.location.hostname + (window.location.port ? ':' + window.location.port: ''); }
Also, when I try to add an IP to ban, I am getting an error "Unable to get property 'indexOf' of undefined or null reference".
After looking at it, it looks like I'm getting an empty IPList from the fail2rest api.
So the code dies here "activeJail.data.IPList.indexOf(ipAddress) === -1" since the IPList is null. Maybe I have something misconfigured for the fail2rest, but I'm am not currently sure yet.
Also, the adding and deleting of regexes does work fine! :)
UPDATE: Looks like my updates are not working, but the reading of the config file is working. I'm thinking it might be something with my fail2rest...