Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: unknown

Region: unknown

Country: China

Internet Service Provider: Tencent Cloud Computing (Beijing) Co. Ltd.

Hostname: unknown

Organization: unknown

Usage Type: Data Center/Web Hosting/Transit

Comments:
Type Details Datetime
attackspambots
Feb 29 07:54:36 haigwepa sshd[22002]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.122.204 
Feb 29 07:54:38 haigwepa sshd[22002]: Failed password for invalid user userftp from 106.54.122.204 port 40658 ssh2
...
2020-02-29 22:18:55
Comments on same subnet:
IP Type Details Datetime
106.54.122.136 attack
Sep 10 18:41:44 nuernberg-4g-01 sshd[12645]: Failed password for root from 106.54.122.136 port 43972 ssh2
Sep 10 18:45:19 nuernberg-4g-01 sshd[13828]: Failed password for root from 106.54.122.136 port 53250 ssh2
2020-09-11 00:49:30
106.54.122.136 attackspam
Sep 10 06:39:40 root sshd[7295]: Invalid user admin from 106.54.122.136
...
2020-09-10 16:08:20
106.54.122.136 attackbotsspam
Sep  9 09:45:02 pixelmemory sshd[578191]: Failed password for invalid user admin from 106.54.122.136 port 40796 ssh2
Sep  9 09:48:31 pixelmemory sshd[578741]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.122.136  user=root
Sep  9 09:48:33 pixelmemory sshd[578741]: Failed password for root from 106.54.122.136 port 48904 ssh2
Sep  9 09:51:48 pixelmemory sshd[579234]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.122.136  user=root
Sep  9 09:51:50 pixelmemory sshd[579234]: Failed password for root from 106.54.122.136 port 56984 ssh2
...
2020-09-10 06:48:27
106.54.122.165 attack
2020-01-05T07:44:16.409028suse-nuc sshd[32528]: Invalid user admin from 106.54.122.165 port 52938
...
2020-02-07 10:37:41
106.54.122.165 attackbotsspam
Unauthorized connection attempt detected from IP address 106.54.122.165 to port 2220 [J]
2020-02-03 18:35:00
106.54.122.165 attackbots
Jan  1 07:40:54 DAAP sshd[21046]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.122.165  user=root
Jan  1 07:40:56 DAAP sshd[21046]: Failed password for root from 106.54.122.165 port 52048 ssh2
Jan  1 07:45:04 DAAP sshd[21067]: Invalid user lynnell from 106.54.122.165 port 49886
Jan  1 07:45:04 DAAP sshd[21067]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.122.165
Jan  1 07:45:04 DAAP sshd[21067]: Invalid user lynnell from 106.54.122.165 port 49886
Jan  1 07:45:06 DAAP sshd[21067]: Failed password for invalid user lynnell from 106.54.122.165 port 49886 ssh2
...
2020-01-01 14:45:39
106.54.122.165 attack
Automatic report - SSH Brute-Force Attack
2019-12-27 07:02:04
106.54.122.165 attackspam
Dec 24 10:55:34 pi sshd\[17724\]: Invalid user nfs from 106.54.122.165 port 43760
Dec 24 10:55:34 pi sshd\[17724\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.122.165
Dec 24 10:55:37 pi sshd\[17724\]: Failed password for invalid user nfs from 106.54.122.165 port 43760 ssh2
Dec 24 11:14:07 pi sshd\[17940\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.122.165  user=root
Dec 24 11:14:09 pi sshd\[17940\]: Failed password for root from 106.54.122.165 port 53586 ssh2
...
2019-12-24 19:44:16
106.54.122.165 attackbotsspam
SSH invalid-user multiple login try
2019-12-15 21:15:16
106.54.122.165 attack
Dec 11 07:30:20 lnxmysql61 sshd[7534]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.122.165
2019-12-11 15:13:08
106.54.122.165 attackbotsspam
Dec  8 15:16:00 MK-Soft-VM6 sshd[7414]: Failed password for root from 106.54.122.165 port 34990 ssh2
Dec  8 15:23:11 MK-Soft-VM6 sshd[7469]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.122.165 
...
2019-12-08 22:53:28
106.54.122.165 attackbots
Dec  4 10:24:00 web9 sshd\[9718\]: Invalid user ozella from 106.54.122.165
Dec  4 10:24:00 web9 sshd\[9718\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.122.165
Dec  4 10:24:02 web9 sshd\[9718\]: Failed password for invalid user ozella from 106.54.122.165 port 60140 ssh2
Dec  4 10:30:57 web9 sshd\[10729\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.122.165  user=root
Dec  4 10:31:00 web9 sshd\[10729\]: Failed password for root from 106.54.122.165 port 39008 ssh2
2019-12-05 06:36:20
106.54.122.165 attack
Dec  3 09:45:30 venus sshd\[15887\]: Invalid user 1qa2ws from 106.54.122.165 port 56448
Dec  3 09:45:30 venus sshd\[15887\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.122.165
Dec  3 09:45:32 venus sshd\[15887\]: Failed password for invalid user 1qa2ws from 106.54.122.165 port 56448 ssh2
...
2019-12-03 17:48:38
106.54.122.165 attackspambots
detected by Fail2Ban
2019-12-03 05:49:51
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 106.54.122.204
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 43906
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;106.54.122.204.			IN	A

;; AUTHORITY SECTION:
.			307	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2020022900 1800 900 604800 86400

;; Query time: 101 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 29 22:18:49 CST 2020
;; MSG SIZE  rcvd: 118
Host info
Host 204.122.54.106.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 204.122.54.106.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
91.135.168.162 attackbots
Unauthorized connection attempt detected from IP address 91.135.168.162 to port 445
2020-01-05 22:46:08
221.163.123.210 attackspam
Unauthorized connection attempt detected from IP address 221.163.123.210 to port 81
2020-01-05 22:25:38
5.38.178.205 attackbots
Unauthorized connection attempt detected from IP address 5.38.178.205 to port 80 [J]
2020-01-05 22:23:28
88.50.43.129 attackspambots
Unauthorized connection attempt detected from IP address 88.50.43.129 to port 445
2020-01-05 22:46:51
2.185.138.124 attackbotsspam
Unauthorized connection attempt detected from IP address 2.185.138.124 to port 23
2020-01-05 22:57:50
79.56.65.27 attack
Unauthorized connection attempt detected from IP address 79.56.65.27 to port 23
2020-01-05 22:16:46
152.32.130.99 attack
Unauthorized connection attempt detected from IP address 152.32.130.99 to port 2220 [J]
2020-01-05 22:39:30
194.61.24.68 attackspambots
Unauthorized connection attempt detected from IP address 194.61.24.68 to port 9100
2020-01-05 22:30:58
78.189.141.5 attack
Unauthorized connection attempt detected from IP address 78.189.141.5 to port 80 [J]
2020-01-05 22:49:40
2.136.191.82 attackbotsspam
Unauthorized connection attempt detected from IP address 2.136.191.82 to port 23 [J]
2020-01-05 22:24:00
222.73.136.205 attack
Unauthorized connection attempt detected from IP address 222.73.136.205 to port 1433 [J]
2020-01-05 22:58:35
187.147.92.55 attack
Unauthorized connection attempt detected from IP address 187.147.92.55 to port 88
2020-01-05 22:34:13
41.233.142.33 attack
Unauthorized connection attempt detected from IP address 41.233.142.33 to port 23
2020-01-05 22:56:38
190.221.56.218 attackbotsspam
Unauthorized connection attempt detected from IP address 190.221.56.218 to port 1433
2020-01-05 22:31:49
119.193.246.76 attack
Unauthorized connection attempt detected from IP address 119.193.246.76 to port 23 [J]
2020-01-05 22:42:36

Recently Reported IPs

122.128.195.129 182.72.105.106 143.240.249.123 190.196.64.93
41.167.170.224 54.89.245.48 115.222.134.163 81.173.170.91
37.52.160.123 51.1.133.45 216.151.14.8 143.28.67.159
6.126.94.130 205.74.135.215 239.92.128.240 9.127.189.34
60.253.173.149 112.157.93.16 189.15.54.31 213.30.200.142