So, suddenly we're noticing a LOT of image search results from bing are being served by, for example tse*.explicit.bing.net instead of the usual. As *.explicit.bing.net is filtered for adult, this is throwing our alerts haywire.
To test, https://www.bing.com/images/search?q=emoji%20wallpapers&qs=n&form=QBIR&pq=emoji%20wallpa&sc=0-0&sp=-1&sk=
You'll find several thumbnails missing if you exclude the explicit bing domain in your policy - yet when you hover of them, it's apparent they're quite safe. This is new - we're getting so many alerts now for safe images. This started happening late last week.
Anyone got any ideas (apart from reclassifying *.explicit.bing.net) what we can do here?
A