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: Beijing Baidu Netcom Science and Technology Co. Ltd.

Hostname: unknown

Organization: unknown

Usage Type: Search Engine Spider

Comments:
Type Details Datetime
attackspam
(sshd) Failed SSH login from 106.13.134.142 (CN/China/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Sep  8 10:48:46 optimus sshd[26065]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.134.142  user=root
Sep  8 10:48:48 optimus sshd[26065]: Failed password for root from 106.13.134.142 port 58966 ssh2
Sep  8 10:54:08 optimus sshd[28026]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.134.142  user=root
Sep  8 10:54:10 optimus sshd[28026]: Failed password for root from 106.13.134.142 port 57340 ssh2
Sep  8 10:59:37 optimus sshd[29889]: Did not receive identification string from 106.13.134.142
2020-09-09 00:13:09
attackspam
firewall-block, port(s): 7374/tcp
2020-09-08 15:44:46
attackspambots
k+ssh-bruteforce
2020-09-08 08:18:33
attackbotsspam
firewall-block, port(s): 29420/tcp
2020-09-03 03:43:07
attack
Invalid user zt from 106.13.134.142 port 38514
2020-09-02 19:21:55
attackbots
" "
2020-09-01 00:36:51
attackbots
Invalid user anon from 106.13.134.142 port 49572
2020-08-17 04:12:17
Comments on same subnet:
IP Type Details Datetime
106.13.134.19 attackbots
May 19 20:50:46 vmd48417 sshd[18889]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.134.19
2020-05-20 04:03:28
106.13.134.19 attackspambots
May  8 23:00:10 vps46666688 sshd[31277]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.134.19
May  8 23:00:13 vps46666688 sshd[31277]: Failed password for invalid user anonymous from 106.13.134.19 port 41980 ssh2
...
2020-05-10 01:38:55
106.13.134.19 attackspambots
May  1 13:38:17 ns392434 sshd[13174]: Invalid user pai from 106.13.134.19 port 34706
May  1 13:38:17 ns392434 sshd[13174]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.134.19
May  1 13:38:17 ns392434 sshd[13174]: Invalid user pai from 106.13.134.19 port 34706
May  1 13:38:19 ns392434 sshd[13174]: Failed password for invalid user pai from 106.13.134.19 port 34706 ssh2
May  1 13:45:20 ns392434 sshd[13444]: Invalid user kalista from 106.13.134.19 port 45798
May  1 13:45:20 ns392434 sshd[13444]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.134.19
May  1 13:45:20 ns392434 sshd[13444]: Invalid user kalista from 106.13.134.19 port 45798
May  1 13:45:22 ns392434 sshd[13444]: Failed password for invalid user kalista from 106.13.134.19 port 45798 ssh2
May  1 13:47:52 ns392434 sshd[13496]: Invalid user test_user from 106.13.134.19 port 43416
2020-05-02 00:47:01
106.13.134.19 attack
2020-04-21T12:55:14.597397homeassistant sshd[7451]: Invalid user admin from 106.13.134.19 port 57042
2020-04-21T12:55:14.609134homeassistant sshd[7451]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.134.19
...
2020-04-21 23:49:49
106.13.134.248 attack
Automatic report - SSH Brute-Force Attack
2020-04-12 21:16:58
106.13.134.19 attack
SSH Brute-Force reported by Fail2Ban
2020-04-11 05:38:52
106.13.134.19 attackbots
Apr  9 23:21:42 php1 sshd\[20825\]: Invalid user deploy from 106.13.134.19
Apr  9 23:21:42 php1 sshd\[20825\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.134.19
Apr  9 23:21:44 php1 sshd\[20825\]: Failed password for invalid user deploy from 106.13.134.19 port 45516 ssh2
Apr  9 23:25:43 php1 sshd\[21241\]: Invalid user deploy from 106.13.134.19
Apr  9 23:25:43 php1 sshd\[21241\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.134.19
2020-04-10 19:34:21
106.13.134.164 attackbots
Apr  6 00:47:38 vmd48417 sshd[14398]: Failed password for root from 106.13.134.164 port 50976 ssh2
2020-04-06 07:17:15
106.13.134.161 attack
Mar 25 18:35:51 itv-usvr-01 sshd[14660]: Invalid user marissa from 106.13.134.161
Mar 25 18:35:51 itv-usvr-01 sshd[14660]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.134.161
Mar 25 18:35:51 itv-usvr-01 sshd[14660]: Invalid user marissa from 106.13.134.161
Mar 25 18:35:52 itv-usvr-01 sshd[14660]: Failed password for invalid user marissa from 106.13.134.161 port 43756 ssh2
2020-03-28 01:29:13
106.13.134.161 attackbotsspam
fail2ban
2020-03-27 00:39:15
106.13.134.161 attack
Invalid user dan from 106.13.134.161 port 33386
2020-03-21 10:02:34
106.13.134.161 attackbotsspam
Jan 10 13:12:28 pi sshd[21928]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.134.161 
Jan 10 13:12:30 pi sshd[21928]: Failed password for invalid user nexus from 106.13.134.161 port 57548 ssh2
2020-03-18 20:37:39
106.13.134.161 attackspambots
$f2bV_matches
2020-03-11 09:13:30
106.13.134.161 attackbotsspam
Mar  7 10:32:11 vps46666688 sshd[17056]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.134.161
Mar  7 10:32:13 vps46666688 sshd[17056]: Failed password for invalid user 123456 from 106.13.134.161 port 40198 ssh2
...
2020-03-08 00:28:01
106.13.134.161 attackbots
Feb 29 23:50:01 sso sshd[3303]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.134.161
Feb 29 23:50:02 sso sshd[3303]: Failed password for invalid user admin1 from 106.13.134.161 port 40900 ssh2
...
2020-03-01 07:45:01
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 106.13.134.142
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 17870
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

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

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

;; Query time: 68 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Aug 17 04:12:14 CST 2020
;; MSG SIZE  rcvd: 118
Host info
Host 142.134.13.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 142.134.13.106.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
103.7.43.15 attackbots
Automatic report - XMLRPC Attack
2019-11-17 18:26:20
106.245.160.140 attackspambots
Nov 17 09:51:39 vps58358 sshd\[1573\]: Invalid user nirvana from 106.245.160.140Nov 17 09:51:42 vps58358 sshd\[1573\]: Failed password for invalid user nirvana from 106.245.160.140 port 33766 ssh2Nov 17 09:55:39 vps58358 sshd\[1587\]: Invalid user phen from 106.245.160.140Nov 17 09:55:41 vps58358 sshd\[1587\]: Failed password for invalid user phen from 106.245.160.140 port 42326 ssh2Nov 17 09:59:34 vps58358 sshd\[1591\]: Invalid user tuffo from 106.245.160.140Nov 17 09:59:36 vps58358 sshd\[1591\]: Failed password for invalid user tuffo from 106.245.160.140 port 50888 ssh2
...
2019-11-17 18:43:31
178.128.233.118 attackbotsspam
\[Sun Nov 17 10:49:12.041643 2019\] \[authz_core:error\] \[pid 1854\] \[client 178.128.233.118:38002\] AH01630: client denied by server configuration: /var/www/michele/xmlrpc.php
...
2019-11-17 18:25:34
51.83.32.232 attackspam
Nov 17 14:11:50 itv-usvr-01 sshd[25495]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.83.32.232  user=root
Nov 17 14:11:52 itv-usvr-01 sshd[25495]: Failed password for root from 51.83.32.232 port 35222 ssh2
2019-11-17 18:35:32
67.54.210.116 attackspambots
Automatic report - Port Scan Attack
2019-11-17 18:24:47
145.255.160.118 attackbots
CloudCIX Reconnaissance Scan Detected, PTR: PTR record not found
2019-11-17 18:20:14
199.249.230.119 attackspambots
Automatic report - XMLRPC Attack
2019-11-17 18:39:11
185.234.216.173 attack
Connection by 185.234.216.173 on port: 25 got caught by honeypot at 11/17/2019 9:26:04 AM
2019-11-17 18:28:20
139.198.18.120 attack
Nov 17 14:37:47 gw1 sshd[19253]: Failed password for root from 139.198.18.120 port 59242 ssh2
...
2019-11-17 18:19:09
120.234.134.34 attack
120.234.134.34 was recorded 5 times by 2 hosts attempting to connect to the following ports: 65529,3389. Incident counter (4h, 24h, all-time): 5, 8, 8
2019-11-17 18:33:44
196.35.41.86 attackspam
"Fail2Ban detected SSH brute force attempt"
2019-11-17 18:15:03
207.38.86.27 attackbots
Automatic report - XMLRPC Attack
2019-11-17 18:29:00
185.216.132.15 attack
no
2019-11-17 18:29:34
115.159.220.190 attack
Nov 17 09:15:44 nextcloud sshd\[7274\]: Invalid user rada from 115.159.220.190
Nov 17 09:15:44 nextcloud sshd\[7274\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.159.220.190
Nov 17 09:15:46 nextcloud sshd\[7274\]: Failed password for invalid user rada from 115.159.220.190 port 34128 ssh2
...
2019-11-17 18:14:03
88.238.116.68 attackbotsspam
" "
2019-11-17 18:07:45

Recently Reported IPs

178.239.156.247 14.115.28.101 185.60.219.13 200.177.108.167
129.28.171.44 147.224.174.58 230.138.161.166 37.175.99.183
39.250.69.135 117.245.247.151 62.237.113.42 103.115.126.2
247.110.246.221 112.75.151.139 205.207.252.210 245.77.170.197
2.243.143.230 216.249.133.107 183.167.54.28 250.185.102.73