The public IP address for MS is: 50.211.70.70, which, when DNS was working, could be found by just a normal DNS lookup. In order to access MS on a personal machine, you can add the entry (the entire line):
to your "hosts" file, which will cause those two host names to resolve to the correct IP address. For unix/linux based machines, that file is /etc/hosts. For Windows based machines, that file is, typically, in C:\Windows\System32\drivers\etc.
Adding the entry to your hosts file should allow you to access metasmoke normally from your machine.
I'd suggest removing the added entry, not the entire file, thus once again relying on DNS, once the DNS issues are resolved.
Is there a reason I'm all of a sudden able to add tags to domains/posts? Is it something to do with having to access MS by adding an entry to the hosts file or have I gained a new permission I wasn't aware of?
@Jesse 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.
@Jesse As you noticed, that's something that can be done with the "Core" role. I gave the "Core" role to a few people, including you, about 12 hours ago.
@SmokeDetector I'm inclined to believe this is spam. Although this specific subdomain has not been seen before, the website virbox.com has appeared in 6 posts (including this one), 3 of which were marked TP. Also, a different user with the exact same name posted another link to this site 5 months ago.
Could someone with 10k on superuser provide a screenshot of this question? MS failed to get a record of it. Alternatively, just watch any links/patterns in it directly.
@cigien 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 807-748-4648 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 !!/watch-number 807-748-4648. Append -force to the command word(s) if you really want to add the pattern you provided.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in link text in body, bad keyword in title, blacklisted website in body, pattern-matching product name in body, +2 more (554): Farmers Garden CBD Gummies Reviews by JosephMcAlpin on meta.SE (@Ollie @Ethan)
@JeffSchaller 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 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.
[ SmokeDetector | MS ] Phone number detected in title, potentially bad keyword in body, potentially bad keyword in title, potentially problematic ns configuration in body, blacklisted user (163): family lawyers near me |Ph.8800788535 by lead india on law.SE (@RyanM)
@CanO'Spam 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.
@Jesse has this been seen in more than just the one post? I'm thinking it'd be more appropriate to watch it first. We tend to jump to blacklisting if it's part of a larger spam campaign, so before approving or rejecting this PR, I wanted to get your perspective. Thanks, and sorry for the double ping
@CanO'Spam 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.
