Re:How we discovered a database leak in one of the biggest S...
by redsec on Tuesday March 06, 2018 @10:12AM
(#16529273)
Sorry, but to avoid problem for now, we prefer to keep the provider anonymous, however we can assure you that it is not metanet.ch.
Re:How we discovered a database leak in one of the biggest S...
by piquadrat on Thursday March 08, 2018 @09:44AM
(#16544586)
You should probably mention that at the top of your blog post. bipson is probably not the only one coming to this (apparently) wrong conclusion based on your current hoster.
Re:How we discovered a database leak in one of the biggest S...
by bipson on Wednesday March 07, 2018 @06:15AM
(#16535669)
My mistake, and I am sorry. Feel free to downvote my above post into oblivion.
Re:How we discovered a database leak in one of the biggest S...
by logronoide on Tuesday March 06, 2018 @09:16AM
(#16528965)
Maybe I’m wrong but the PTR of the IP seems to be in a spam blacklist:
https://apility.io/search?q=infoteam.ch
https://apility.io/search?q=80.74.143.113
https://apility.io/search?q=dynco.ch
This thing happens sometimes, specially if you use a shared hosting. Recently using a well known cloud provider the Public IP address assigned was in a spam blacklist! It’s a good idea to have a look at your IP and domains frequently.
(Disclaimer: I’m the founder of the tool used for the lookup in the blacklists)
Not trying to ruin their business, but they should consider handling issues like this one properly.