[ SmokeDetector | MS ] Bad keyword in answer, potentially bad keyword in answer, potentially problematic ns configuration in answer (90): Slot Qris Gacor by Slot Qris on gis.SE
!!/report stackoverflow.com/a/78412302/4957508 "undisclosed affiliation; YouTube name matches SO profile name; 0 views on video; video was uploaded recently"
[ SmokeDetector | MS ] Few unique characters in answer, no whitespace in answer, potentially bad keyword in answer, repeating characters in answer (264): Zeus' Lightning Bolt by user11156 on mythology.SE
[ SmokeDetector | MS ] Url in title, potentially bad asn for hostname in body, potentially bad asn for hostname in title (96): www.awsdumps.com/ by joan withe on meta.mathoverflow.net
> Potentially bad ns for domain in body, potentially bad ns for domain in title ---------- Potentially bad ns for domain in body - techsocial.com.ng NS suspicious dns2.namecheaphosting.com.,dns1.namecheaphosting.com. Potentially bad ns for domain in title - techsocial.com.ng NS suspicious dns2.namecheaphosting.com.,dns1.namecheaphosting.com.
> Bad ns for domain in body, bad ns for domain in title, blacklisted website in body, blacklisted website in title, blacklisted website in username ---------- Bad ns for domain in body - servicemycar.com NS suspicious ns-20.awsdns-02.com.,ns-902.awsdns-48.net.,ns-1117.awsdns-11.org.,ns-1994.awsdns-57.co.uk. Bad ns for domain in title - servicemycar.com NS suspicious ns-20.awsdns-02.com.,ns-902.awsdns-48.net.,ns-1117.awsdns-11.org.,ns-1994.awsdns-57.co.uk. Blacklisted website in body - Position 0-16: servicemycar.com
> Bad ip for hostname in body, bad ip for hostname in title, bad ns for domain in body, bad ns for domain in title, blacklisted website in body, blacklisted website in title, blacklisted website in username ---------- Bad ip for hostname in body - dumpsboss.com suspicious IP address 104.21.63.138 Bad ip for hostname in title - dumpsboss.com suspicious IP address 104.21.63.138 Bad ns for domain in body - dumpsboss.com NS suspicious dana.ns.cloudflare.com.,josh.ns.cloudflare.com. Bad ns for domain in title - dumpsboss.com NS suspicious dana.ns.cloudflare.com.,josh.ns.cloudflare.com.
> Bad ns for domain in body, bad ns for domain in title, potentially bad ip for hostname in body, potentially bad ip for hostname in title, potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Bad ns for domain in body - studyfy.com NS suspicious trey.ns.cloudflare.com.,lorna.ns.cloudflare.com. Bad ns for domain in title - studyfy.com NS suspicious trey.ns.cloudflare.com.,lorna.ns.cloudflare.com. Potentially bad ip for hostname in body - studyfy.com suspicious IP address 3.233.126.24
@Makyen That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer Append -force to the command word(s) if you really want to add the pattern you provided.
@Makyen That pattern may be a North American number. If it is, please use a format which starts with an optional 1 followed by possible separator text and has the main number in the format 991-556-0947 where - could be a single alpha character or any [\W_]*+. Alternately, you can add the comment (?#IS NorAm) to the end of the pattern to force also using the alternate normalized form, or (?#NO NorAm) if it's not a North American phone number and it's incorrectly recognized as one. Perhaps try !!/blacklist-number 991-556-0947. Append -force to the command word(s) if you really want to add the pattern you provided.
