City: unknown
Region: unknown
Country: South Africa
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 146.141.194.227
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 17196
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;146.141.194.227. IN A
;; AUTHORITY SECTION:
. 3600 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2019070800 1800 900 604800 86400
;; Query time: 2 msec
;; SERVER: 67.207.67.2#53(67.207.67.2)
;; WHEN: Mon Jul 08 20:38:18 CST 2019
;; MSG SIZE rcvd: 119227.194.141.146.in-addr.arpa domain name pointer pc227.helenj.wits.ac.za.Server: 67.207.67.2
Address: 67.207.67.2#53
Non-authoritative answer:
227.194.141.146.in-addr.arpa name = pc227.helenj.wits.ac.za.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 64.94.211.152 | attackbotsspam | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found serenityfamilychiropractic.com after doing a quick search – you showed up near the top of the rankings, so whatever you’re doing for SEO, looks like it’s working well. So here’s my question – what happens AFTER someone lands on your site? Anything? Research tells us at least 70% of the people who find your site, after a quick once-over, they disappear… forever. That means that all the work and effort you put into getting them to show up, goes down the tubes. Why would you want all that good work – and the great site you’ve built – go to waste? Because the odds are they’ll just skip over calling or even grabbing their phone, leaving you high and dry. But here’s a thought… what if you could make it super-simple for someone to raise their hand, say, “okay, let’s talk” without requiring them to even pull their cell phone from their pocket? You can – thanks to revolutionary new s |
2020-02-26 23:09:34 |
| 213.167.46.166 | attackspambots | $f2bV_matches |
2020-02-26 23:09:58 |
| 40.124.4.131 | attackspam | Feb 26 13:54:25 sigma sshd\[17639\]: Invalid user flytlink from 40.124.4.131Feb 26 13:54:26 sigma sshd\[17639\]: Failed password for invalid user flytlink from 40.124.4.131 port 54430 ssh2 ... |
2020-02-26 22:46:19 |
| 34.73.212.241 | attackspambots | SIP/5060 Probe, BF, Hack - |
2020-02-26 22:48:19 |
| 213.32.88.138 | attackbotsspam | $f2bV_matches |
2020-02-26 22:44:17 |
| 213.59.123.221 | attack | $f2bV_matches |
2020-02-26 22:42:07 |
| 213.183.101.89 | attackspam | $f2bV_matches |
2020-02-26 23:03:31 |
| 51.255.150.119 | attack | Feb 26 14:37:57 v22018076622670303 sshd\[8560\]: Invalid user oracle from 51.255.150.119 port 36168 Feb 26 14:37:57 v22018076622670303 sshd\[8560\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.255.150.119 Feb 26 14:37:58 v22018076622670303 sshd\[8560\]: Failed password for invalid user oracle from 51.255.150.119 port 36168 ssh2 ... |
2020-02-26 22:32:27 |
| 106.12.215.238 | attackbots | (sshd) Failed SSH login from 106.12.215.238 (CN/China/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Feb 26 15:52:51 amsweb01 sshd[18716]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.215.238 user=root Feb 26 15:52:53 amsweb01 sshd[18716]: Failed password for root from 106.12.215.238 port 51792 ssh2 Feb 26 15:54:47 amsweb01 sshd[18878]: User mysql from 106.12.215.238 not allowed because not listed in AllowUsers Feb 26 15:54:47 amsweb01 sshd[18878]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.215.238 user=mysql Feb 26 15:54:48 amsweb01 sshd[18878]: Failed password for invalid user mysql from 106.12.215.238 port 39108 ssh2 |
2020-02-26 22:59:08 |
| 5.94.66.245 | attack | suspicious action Wed, 26 Feb 2020 10:37:43 -0300 |
2020-02-26 22:55:18 |
| 186.10.125.209 | attackspam | Feb 26 09:29:28 NPSTNNYC01T sshd[19590]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.10.125.209 Feb 26 09:29:29 NPSTNNYC01T sshd[19590]: Failed password for invalid user devp from 186.10.125.209 port 17050 ssh2 Feb 26 09:31:09 NPSTNNYC01T sshd[19707]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.10.125.209 ... |
2020-02-26 22:43:21 |
| 213.215.115.94 | attack | $f2bV_matches |
2020-02-26 22:57:43 |
| 222.186.173.142 | attackspam | Feb 26 04:31:41 auw2 sshd\[28645\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.173.142 user=root Feb 26 04:31:44 auw2 sshd\[28645\]: Failed password for root from 222.186.173.142 port 40040 ssh2 Feb 26 04:32:03 auw2 sshd\[28686\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.173.142 user=root Feb 26 04:32:05 auw2 sshd\[28686\]: Failed password for root from 222.186.173.142 port 58478 ssh2 Feb 26 04:32:24 auw2 sshd\[28703\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.173.142 user=root |
2020-02-26 22:36:07 |
| 213.245.35.117 | attack | $f2bV_matches |
2020-02-26 22:52:45 |
| 213.32.91.37 | attack | $f2bV_matches |
2020-02-26 22:42:27 |