Oh, so that declaring of http://TEXTFILES.COM as a "dangeous site" on Chrome by Google extended not just to the (wrong) main site's set, but they've banned all of my domains, *.textfiles.com, no matter what they have on them or what they do. Good job everyone. Excellent work.
-
Show this thread
-
Replying to @textfiles @JoeBeOne
If you sign up for Search Console, you can see details of the block & appeal. Usually this happens if your servers are hacked
2 replies 0 retweets 14 likes -
See https://developers.google.com/web/fundamentals/security/hacked/how_do_I_know_if_site_hacked … for instructions for finding out what URLs are triggering the flag
5 replies 0 retweets 11 likes -
4. I look forward to someone getting back to me randomly as to why my 20 year old site and files unchanged since 1997 are suddenly dangerous enough to block every one of my domains and associated sites.
1 reply 0 retweets 2 likes -
Replying to @textfiles @JoeBeOne
This sounds frustrating. It's quite possible that some newer piece of malware is reusing some of this old code. I'll escalate to the ops team, although to be honest I have no idea what the policy is for sites that intentionally host old malware.
3 replies 0 retweets 7 likes
It has happened to my site before, from legitimate ancient security advisories written by me. The team wouldn't budge, their advice was to add some javascript that required you to enter some text before loading the page then request a rescan. 
-
-
Add some JavaScript... irony is old friend but this is a good one!
0 replies 1 retweet 9 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.