@Stormblessed Because there's a regex on the watchlist which looks for URLs which end in several different groups of characters, which gcommonly indicate a country. That's a common pattern for spam URLs. That regex is https?://[^<>"'\s]+(?<![?/][a-z]{2})-(?:uk|ca|fr|es|za|de|au|it|dk|br|nz|be|se|us|ch|nl|at|id|no|ie|sg|pt|hr|pl|mx|lt|lu|fi|kr)(?=/[<>"'\s]|/$) and is currently here.

I'd have to do more research to get its exact numbers, but it's running in the ballpark of 92% TP.

@Makyen so how exactly is it supposed to work?

I don’t know Regex

On a side note, is it “ree-jex” or “reg-ex”?

@Stormblessed For an email address like this, which is moderately obfuscated, and where the email's username is sufficiently unique such that it's unlikely to trigger false positives when detected by itself, we usually use a regex that looks like: danielle6751(?:\W*(?:at\W*)?outlook\W*(?:dot\W*)?com)? That regex covers a number of different ways in which an email address is commonly obfuscated, while not being nearly as complex as is required to catch more advanced obfuscation.

@Stormblessed reg-ex

@Stormblessed To see how regular expressions work, it's often very helpful to use a regular expression tester. There are several online, and some you can download. I usually use regex101.com (I also see many other people linking to it). For this regex, you can take a look at a test version of it here, which will show you explanations of the different parts and kinds of things used as you move the mouse around the regex and/or click on things.

There's also a good write-up about Regular Expressions, including a tutorial, at Regular-Expressions.info.

@Stormblessed The only posts I'm seeing with this are from 4 years ago. Is there something newer?

@Stormblessed Yeah, that's not good.

@Stormblessed I've created an issue on GitHub for this.

[ metasmoke ] ci/circleci: rubocop failure on 653f12f: Your tests failed on CircleCI

[ metasmoke ] ci/circleci: rubocop failure on 0b652cc: Your tests failed on CircleCI

[ metasmoke ] ci/circleci: rails-tests failure on 653f12f: Your tests failed on CircleCI

[ metasmoke-deploy ] deploy started by ArtOfCode

[ SmokeDetector | MS ] Potentially bad keyword in body (1): Nyt article on population by Bat Batkk on skeptics.SE

[ metasmoke ] ci/circleci: rails-tests failure on 0b652cc: Your tests failed on CircleCI

[ SmokeDetector | MS ] Potentially problematic ns configuration in answer (1): How could one display several images in the background on at the time? by Jonathan Jackson on stackoverflow.com

[ SmokeDetector | MS ] Potentially bad ns for domain in answer (1): Can simulation theory be considered a form of religion? by SanityMaker on philosophy.SE

[ SmokeDetector | MS ] Bad keyword in body, link at end of body, pattern-matching product name in body, pattern-matching website in body, potentially bad ns for domain in body, +1 more (393): Must Try This product for better results by FeliciaRittenhouse89 on askubuntu.com

[ SmokeDetector | MS ] Potentially bad asn for hostname in answer (1): SIM800L HTTPSSL with unknown error by cisco_salazar on stackoverflow.com

tpu- feedback received on Must Try This product for better results [MS]

[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Simple cat program ✏️ by Mr. Negi on codegolf.SE