6 ms·
Show HN: Who runs this – A Chrome extension that shows who runs a site
- kaolti 10y agoMay have a couple of bugs but one use case would be finding out that rottentomatoes.com is run by Comcast.
- deleted 10y ago[deleted]
- kspaans 10y agoWhen run against www.ssa.gov it says "something seems to be wrong" LOL
- TazeTSchnitzel 10y agoFor .gov domains it might as well just show “The Government of the United States”.
- ridiculous_fish 10y agoVery cool idea. I noticed it reports that ridiculousfish.com "is run by" namecheap, but namecheap is only the registrar and does not run or even host the site.
- kaolti 10y agoThanks! Yea, the problem is the registrant organization of the domain is set to Namecheap. Not sure how to get around domain privacy for now.
- kspaans 10y agoMaybe the extension could check the info on the SSL certificates (if available) if the domain is registered through a proxy?
- degenerate 10y agoThis is almost necessary for the extension to be useful. A good number of domains I checked are all "run" by WHOISGUARD, INC.
- kaolti 10y agoHm, do SSL certificates have information about the owner?
- degenerate 10y agoI think only Extended Validation (EV) certificates have this info by default :(
- callesgg 10y agoSome do, some do not.
- MasterScrat 10y agoYou could have a list to recognise proxy names and in this case display clearly that the real owner has been obfuscated...
- kaolti 10y agoThat could work!
- TazeTSchnitzel 10y agoHmm. It can't tell me that thewaytohappiness.org is run by Scientology. But expecting it to see through Scientology front groups is perhaps asking too much. ^^
- diegorbaquero 10y agoWhen ran against my own domain (diegorbaquero.com) it just shows "Something seems to be wrong"
- kaolti 10y agoYea, it doesn't check for registrant name atm, should probably show that, if there's no registrant org.
- MasterScrat 10y agoWhat would be even more useful would be a "that's surprising!" button next to the result. When an owner is often reported as surprising for a domain, the extension should either blink or directly display the owner without being clicked.
- kaolti 10y agoThat's awesome, add that to the todos.
- djcollier 10y agoCould you share a link to the repo if its available? Very cool idea!
- kaolti 10y agoThanks! Here it is: https://github.com/kaolti/Who-Runs-This.git https://github.com/kaolti/Who-Runs-This.git
- rjbrock 10y agoThis appears to be a private key (so no one should ever be able to read this file): https://github.com/kaolti/Who-Runs-This/blob/master/key.pem https://github.com/kaolti/Who-Runs-This/blob/master/key.pem Is this for publishing to the chrome app store? If it is, I recommend taking down the extension and republishing with a new secure key ASAP.
- kaolti 10y agolol, saved my ass it looks like! Took your advice.
- callesgg 10y agoIt is still in the commit history. You need to throw that key away and get a new one.
- rjbrock 10y agoExactly, that key is now completely compromised (it was the second it was public). You can still see it here: https://github.com/kaolti/Who-Runs-This/commit/764945d8d968b29008f7d7075f014a8624830b07 https://github.com/kaolti/Who-Runs-This/commit/764945d8d968b... You will need to generate a new key and resign with the new one.
- kaolti 10y agoI removed it now, still looking into getting a new key.
- dylz 10y agoWould be nice to note that it sends hostnames of the sites you visit in plaintext, no SSL/TLS, across the internet to: http://api.corpwatch.org/companies http://104.236.253.171:9119
- kaolti 10y agoIs that really stupid?
- jsmthrowaway 10y agoYes.
- kaolti 10y agoLearned something then! Is it take it off the store stupid or just regular?
- jsmthrowaway 10y agoI can't make that decision for you but generally things that transmit address bar input from a browser to other locations are enough for me to ban something from a network, whether it's encrypted in flight or not. Your personal DigitalOcean server being on the other end of the entire install base's queries (a) gives me pause, given the logging opportunities and (b) will fall over if you get some installation footprint. Your decision not to encrypt means that the threat vector expands from solely you to you as well as any adversaries in between the browser and you, so it's sort of an extra bummer on top of some bummers. A screen shot extension for Chrome did this without telling people and it became headlines. There's a reason one popular tool for finding stuff that does this is called Little Snitch.
- kaolti 10y agoI see, thanks for letting me know. Seems like for now the best is to republish with encryption and have a note about it so that people know.
- kaolti 10y agoThanks for all the feedback guys! Took it down for now and will republish when it's fixed.
- scottydelta 10y agoIs that a private key to connect to your server in your repo? https://github.com/kaolti/Who-Runs-This/blob/master/key.pem https://github.com/kaolti/Who-Runs-This/blob/master/key.pem
- kaolti 10y agoHehe, was for the Chrome store, got rid of it now.
- scottydelta 10y ago[deleted]
- youdidwhat 10y agoDid you just publically admit to attempting to break into his server?
- scottydelta 10y agonot really.
- jnbiche 10y agoSorry, man, I'd recommend you re-package with a new key, and re-publish. There are numerous sites that log all Github commits, that private key is public now. Anyone could sign any other extension as you now.
- jhiggins777 10y agoLink is broken