City: unknown
Region: unknown
Country: Hong Kong
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 192.198.143.9
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 44056
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;192.198.143.9. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025022700 1800 900 604800 86400
;; Query time: 11 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 27 15:17:14 CST 2025
;; MSG SIZE rcvd: 106Host 9.143.198.192.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 9.143.198.192.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 5.59.135.94 | attack | Unauthorized connection attempt from IP address 5.59.135.94 on Port 445(SMB) |
2019-10-31 03:30:37 |
| 103.129.99.72 | attack | http://....com/.../?locale=en1111111111111'%20UNION%20SELECT%20CHAR(45,120,49,45,81,45),CHAR(45,120,50,45,81,45)--%20%20 |
2019-10-31 03:10:09 |
| 49.234.48.86 | attackbots | $f2bV_matches |
2019-10-31 03:18:48 |
| 118.89.247.74 | attackspambots | Oct 30 18:49:45 v22018076622670303 sshd\[29850\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.89.247.74 user=root Oct 30 18:49:47 v22018076622670303 sshd\[29850\]: Failed password for root from 118.89.247.74 port 59120 ssh2 Oct 30 18:54:27 v22018076622670303 sshd\[29912\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.89.247.74 user=root ... |
2019-10-31 03:31:00 |
| 222.186.173.180 | attackbots | Oct 30 09:01:41 web1 sshd\[13227\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.173.180 user=root Oct 30 09:01:43 web1 sshd\[13227\]: Failed password for root from 222.186.173.180 port 25902 ssh2 Oct 30 09:01:47 web1 sshd\[13227\]: Failed password for root from 222.186.173.180 port 25902 ssh2 Oct 30 09:01:51 web1 sshd\[13227\]: Failed password for root from 222.186.173.180 port 25902 ssh2 Oct 30 09:01:55 web1 sshd\[13227\]: Failed password for root from 222.186.173.180 port 25902 ssh2 |
2019-10-31 03:02:44 |
| 196.205.3.135 | attackbotsspam | Unauthorized connection attempt from IP address 196.205.3.135 on Port 445(SMB) |
2019-10-31 03:06:11 |
| 148.70.231.231 | attackbots | wp-login.php |
2019-10-31 03:21:31 |
| 177.185.14.14 | attack | Unauthorized connection attempt from IP address 177.185.14.14 on Port 445(SMB) |
2019-10-31 03:05:30 |
| 105.242.49.97 | attackbots | Unauthorized connection attempt from IP address 105.242.49.97 on Port 445(SMB) |
2019-10-31 03:00:06 |
| 164.132.74.78 | attackbotsspam | Oct 30 19:47:46 SilenceServices sshd[19931]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.74.78 Oct 30 19:47:48 SilenceServices sshd[19931]: Failed password for invalid user administrator from 164.132.74.78 port 50042 ssh2 Oct 30 19:52:56 SilenceServices sshd[23227]: Failed password for root from 164.132.74.78 port 33090 ssh2 |
2019-10-31 02:54:08 |
| 109.194.217.168 | attackspambots | Oct 30 12:30:55 riskplan-s sshd[1788]: reveeclipse mapping checking getaddrinfo for 109x194x217x168.dynamic.voronezh.ertelecom.ru [109.194.217.168] failed - POSSIBLE BREAK-IN ATTEMPT! Oct 30 12:30:55 riskplan-s sshd[1788]: Invalid user kafka from 109.194.217.168 Oct 30 12:30:55 riskplan-s sshd[1788]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=109.194.217.168 Oct 30 12:30:58 riskplan-s sshd[1788]: Failed password for invalid user kafka from 109.194.217.168 port 19351 ssh2 Oct 30 12:31:00 riskplan-s sshd[1788]: Failed password for invalid user kafka from 109.194.217.168 port 19351 ssh2 ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=109.194.217.168 |
2019-10-31 02:58:01 |
| 118.99.73.38 | attack | Unauthorized connection attempt from IP address 118.99.73.38 on Port 445(SMB) |
2019-10-31 03:08:10 |
| 157.245.107.153 | attackbots | Oct 30 19:34:58 h2177944 sshd\[16187\]: Invalid user ucpss from 157.245.107.153 port 41864 Oct 30 19:34:58 h2177944 sshd\[16187\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.245.107.153 Oct 30 19:35:00 h2177944 sshd\[16187\]: Failed password for invalid user ucpss from 157.245.107.153 port 41864 ssh2 Oct 30 20:07:14 h2177944 sshd\[17758\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.245.107.153 user=root ... |
2019-10-31 03:30:22 |
| 94.191.31.53 | attackspambots | Oct 30 16:15:06 server sshd\[15008\]: Invalid user tk from 94.191.31.53 Oct 30 16:15:06 server sshd\[15008\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.191.31.53 Oct 30 16:15:07 server sshd\[15008\]: Failed password for invalid user tk from 94.191.31.53 port 58500 ssh2 Oct 30 17:50:47 server sshd\[4367\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.191.31.53 user=root Oct 30 17:50:50 server sshd\[4367\]: Failed password for root from 94.191.31.53 port 41830 ssh2 ... |
2019-10-31 03:19:41 |
| 167.71.212.242 | attack | 2019-10-30T13:40:10.843975tmaserv sshd\[4405\]: Invalid user 12345678 from 167.71.212.242 port 51818 2019-10-30T13:40:10.850306tmaserv sshd\[4405\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.212.242 2019-10-30T13:40:12.175639tmaserv sshd\[4405\]: Failed password for invalid user 12345678 from 167.71.212.242 port 51818 ssh2 2019-10-30T13:44:46.734466tmaserv sshd\[4634\]: Invalid user member from 167.71.212.242 port 38736 2019-10-30T13:44:46.740721tmaserv sshd\[4634\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.212.242 2019-10-30T13:44:48.623010tmaserv sshd\[4634\]: Failed password for invalid user member from 167.71.212.242 port 38736 ssh2 ... |
2019-10-31 03:13:33 |