twitterdoesntcareaboutspamreports

[anyone8]

Tracking link: http://t.co/ [removed]

No recent reports, no history available

Host t.co (checking ip) = 199.59.148.12

Resolves to 199.59.148.12

Routing details for 199.59.148.12

[refresh/show] Cached whois for 199.59.148.12 : net-abuse[at]twitter.com

tcoabuse[at]twitter.com redirects to twitterdoesntcareaboutspamreports[at]devnull.spamcop.net

Using best contacts twitterdoesntcareaboutspamreports[at]devnull.spamcop.net

Or tracking URL, for those who want to see it for themselves: http://www.spamcop.net/sc?id=z6007628019z0a553839e8ee127e2cde75b677032013z

I have to confess I laughed when I saw this. An email address that makes a statement (twitterdoesntcareaboutspamreports is "twitter doesn't care about spam reports", for anyone who has trouble seeing it) is totally something I would do.

Now I don't know whether to be sad or pissed off that twitter has demonstrated such an attitude that someone has gone to the trouble of setting the reporting address like this.

If there is any interesting history on what lead up to this, it might make interesting reading.

[Farelf]

Using best contacts twitterdoesntcareaboutspamreports[at]devnull.spamcop.net

a pungent commentary indeed. Good to know someone at SC can be provoked by twitter's blatant hypocrisy (placing onus on phishing and hacking avoidance squarely with the user).

Using VirusTotal (https://www.virustotal.com/en/url/e98b2e7fa5de739620fda804cb2230e90598b69d2fdc37ef81f175761d85a64b/analysis/1415333536/) we can find where the t.co shortener involved redirects, we can get a VT analysis of the target from the link in the first analysis - (http://www.virustotal.com/url/1cd60dbd451fd9e15458d7a596a82e47430faad8996e9deb67d5e07d8c0d1fca/analysis/) - we can get quttera.com file analysis and commentary for both from the links provided in the VT reports and any details of any blacklists (t.co).