@Makyen That pattern looks like it's already caught by Pattern-matching email in answer and Pattern-matching email in body; append -force if you really want to do that.
@SmokeDetector Undisclosed affiliation (see profile). Link is just to the site's homepage. It's isn't relevant to the question/answer. It's just promoting the site.
[ SmokeDetector | MS ] Potentially bad ip for hostname in answer, potentially bad keyword in answer, potentially problematic ns configuration in answer (3): Date format in Alteryx by Yamini Undavalli on stackoverflow.com
@Shree 'guestpostingindia.com' is not caught by a blacklist or watchlist item.
@Shree That pattern looks like it's already caught by Pattern-matching website in answer and Pattern-matching website in body; append -force if you really want to do that.
@Shree That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
[ SmokeDetector | MS ] Bad ip for hostname in body, body starts with title and ends in url, link at end of body, pattern-matching website in body, potentially bad keyword in body (395): This will help you to make the most by KristenSmine on askubuntu.com
> Pattern-matching website in body, pattern-matching website in title ---------- Pattern-matching website in body - Position 0-23: buyresurgesupplement.co Pattern-matching website in title - Position 0-23: buyresurgesupplement.co
@double-beep The post qualified for autoflagging. Unfortunately, at that time, MS was blocked from using the SE API, due to too many requests. You can see the failure message by hovering over the "fail" on this page.
@Makyen No such item (?-i:OpenAIresearch)(?<=bit\.ly/OpenAIresearchly) in watchlist.
@Makyen That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
@Makyen That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
@Makyen That pattern looks like it's already caught by Potentially bad keyword in body, Bad keyword in answer, Potentially bad keyword in answer, and Bad keyword in body; append -force if you really want to do that.
@Makyen 'reliant keto' is not caught by a blacklist or watchlist item.