> Potentially bad ns for domain in body, potentially bad ns for domain in title, potentially problematic ns configuration in body, potentially problematic ns configuration in title ---------- Potentially bad ns for domain in body - gitysoft.in NS suspicious ns622.redserverhost.com.,ns621.redserverhost.com. Potentially bad ns for domain in title - gitysoft.in NS suspicious ns622.redserverhost.com.,ns621.redserverhost.com. Potentially problematic ns configuration in body - Suspicious nameservers: all IP addresses for gitysoft.in are in set {'94.23.164.13'}
> Bad keyword in body, bad keyword in title, bad keyword in username ---------- Bad keyword in body - Position 0-18: Captain WebGenesis Bad keyword in title - Position 0-18: Captain WebGenesis Bad keyword in username - Position 0-18: Captain WebGenesis
@Nick 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.
@VLAZ The regex contains an unescaped ".", which should be "\." in most cases. Append -force to the command word(s) if you really want to add the pattern you provided.
@Cow yeah, but they spammed their library in almost every post they have written. I think they deserve to remain on the blacklist (although I did retract my spam flag)
halflife:2024-04-24 07:37:43,454:https://rb.gy/au7du0 redirects to https://kwork.com/smm/31714818/i-will-organic-facebook-marketing-and-promotion-for-sales-and-traffic
@tripleee That pattern looks like it's already caught by Bad keyword in body and Bad keyword in answer Append -force to the command word(s) if you really want to add the pattern you provided.
