> Potentially bad ns for domain in body, potentially bad ns for domain in title ---------- Potentially bad ns for domain in body - acedata.cloud NS suspicious pianist.dnspod.net.,jazz.dnspod.net. Potentially bad ns for domain in title - acedata.cloud NS suspicious pianist.dnspod.net.,jazz.dnspod.net.
@Dragonrage That pattern looks like it's already caught by Bad keyword in answer and Bad keyword in body Append -force to the command word(s) if you really want to add the pattern you provided.
@Cow That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command word(s) if you really want to add the pattern you provided.
@JeffSchaller A normalized version, {{'18187511395', '8187511395'}}, of that pattern is already on the number blacklist. You can use !!/bisect-number +1(818)-751-1395 to determine which entries on the number lists match that pattern, which would tell you: Matched by +1(818)-751-1395 on line 3320 of blacklisted_numbers.txt: +1(818)-751-1395 found verbatim; 8187511395 found normalized
