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: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
IP Type Details Datetime
119.29.242.48 attack
Invalid user sakshi from 119.29.242.48 port 37520
2020-01-03 15:51:50
119.29.242.48 attack
Input Traffic from this IP, but critial abuseconfidencescore
2020-01-01 01:02:05
119.29.242.48 attack
frenzy
2019-12-16 20:49:03
119.29.242.48 attackspam
Dec  9 21:48:46 v22018086721571380 sshd[4099]: Failed password for invalid user steam from 119.29.242.48 port 48340 ssh2
2019-12-10 05:29:38
119.29.242.48 attackbotsspam
2019-12-05T23:47:50.708193abusebot.cloudsearch.cf sshd\[30348\]: Invalid user witwicke from 119.29.242.48 port 58554
2019-12-06 07:54:09
119.29.242.48 attackspambots
Nov 30 03:47:46 sachi sshd\[25343\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.242.48  user=root
Nov 30 03:47:49 sachi sshd\[25343\]: Failed password for root from 119.29.242.48 port 51746 ssh2
Nov 30 03:52:58 sachi sshd\[25687\]: Invalid user fansler from 119.29.242.48
Nov 30 03:52:58 sachi sshd\[25687\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.242.48
Nov 30 03:53:00 sachi sshd\[25687\]: Failed password for invalid user fansler from 119.29.242.48 port 58574 ssh2
2019-11-30 22:15:56
119.29.242.48 attackbots
2019-11-29T15:00:17.412146abusebot-5.cloudsearch.cf sshd\[789\]: Invalid user web from 119.29.242.48 port 47722
2019-11-29 23:09:58
119.29.242.48 attackbots
Nov 19 15:48:31 server sshd\[12972\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.242.48  user=root
Nov 19 15:48:33 server sshd\[12972\]: Failed password for root from 119.29.242.48 port 38188 ssh2
Nov 19 16:05:23 server sshd\[17443\]: Invalid user martine from 119.29.242.48
Nov 19 16:05:23 server sshd\[17443\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.242.48 
Nov 19 16:05:25 server sshd\[17443\]: Failed password for invalid user martine from 119.29.242.48 port 44762 ssh2
...
2019-11-19 21:41:01
119.29.242.48 attack
Nov  9 08:11:05 lnxweb62 sshd[5419]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.242.48
2019-11-09 16:22:19
119.29.242.48 attackbots
Oct 29 15:59:49 ny01 sshd[14026]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.242.48
Oct 29 15:59:51 ny01 sshd[14026]: Failed password for invalid user chase from 119.29.242.48 port 42084 ssh2
Oct 29 16:04:03 ny01 sshd[14383]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.242.48
2019-10-30 04:08:38
119.29.242.48 attackbots
Oct 24 17:17:57 lnxmysql61 sshd[20615]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.242.48
2019-10-24 23:48:58
119.29.242.84 attack
Oct 24 06:15:57 localhost sshd\[1469\]: Invalid user ntadmin123 from 119.29.242.84 port 45218
Oct 24 06:15:57 localhost sshd\[1469\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.242.84
Oct 24 06:15:59 localhost sshd\[1469\]: Failed password for invalid user ntadmin123 from 119.29.242.84 port 45218 ssh2
2019-10-24 12:18:56
119.29.242.84 attackbots
Oct 23 00:09:55 ArkNodeAT sshd\[24871\]: Invalid user gj from 119.29.242.84
Oct 23 00:09:55 ArkNodeAT sshd\[24871\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.242.84
Oct 23 00:09:57 ArkNodeAT sshd\[24871\]: Failed password for invalid user gj from 119.29.242.84 port 38486 ssh2
2019-10-23 07:01:21
119.29.242.84 attackspam
Oct 21 05:46:39 SilenceServices sshd[26334]: Failed password for root from 119.29.242.84 port 39270 ssh2
Oct 21 05:51:36 SilenceServices sshd[27681]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.242.84
Oct 21 05:51:38 SilenceServices sshd[27681]: Failed password for invalid user test6 from 119.29.242.84 port 48900 ssh2
2019-10-21 15:00:56
119.29.242.84 attackbots
Oct 13 14:08:48 vps01 sshd[31733]: Failed password for root from 119.29.242.84 port 49832 ssh2
2019-10-13 20:23:35
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 119.29.242.180
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 48112
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;119.29.242.180.			IN	A

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

;; Query time: 56 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jan 10 16:11:37 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 180.242.29.119.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 180.242.29.119.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
3.15.170.106 attack
May 17 01:39:37 mout sshd[17887]: Connection closed by 3.15.170.106 port 48860 [preauth]
May 17 01:55:14 mout sshd[19434]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=3.15.170.106  user=root
May 17 01:55:15 mout sshd[19434]: Failed password for root from 3.15.170.106 port 42684 ssh2
2020-05-17 07:56:53
189.145.95.229 attackspambots
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2020-05-17 08:02:23
14.98.213.14 attackspambots
May 17 00:24:14 prox sshd[25053]: Failed password for root from 14.98.213.14 port 46890 ssh2
2020-05-17 07:56:17
89.248.168.218 attackspambots
May 17 01:53:32 debian-2gb-nbg1-2 kernel: \[11932055.225374\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=89.248.168.218 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=31120 PROTO=TCP SPT=46739 DPT=21678 WINDOW=1024 RES=0x00 SYN URGP=0
2020-05-17 08:15:54
60.22.72.209 attackspam
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2020-05-17 08:21:53
61.133.232.248 attackbotsspam
Invalid user ubuntu from 61.133.232.248 port 55820
2020-05-17 07:52:42
46.180.192.253 attack
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2020-05-17 08:24:59
104.206.128.54 attackbots
 TCP (SYN) 104.206.128.54:54703 -> port 5900, len 44
2020-05-17 08:09:33
107.148.131.145 attack
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2020-05-17 08:09:01
61.133.232.251 attack
Invalid user cvs from 61.133.232.251 port 31942
2020-05-17 07:51:54
92.63.194.35 attack
 TCP (SYN) 92.63.194.35:39657 -> port 1723, len 60
2020-05-17 08:14:48
51.83.171.20 attackspambots
 TCP (SYN) 51.83.171.20:44652 -> port 18989, len 44
2020-05-17 08:23:49
45.178.1.37 attackbots
Invalid user job from 45.178.1.37 port 48122
2020-05-17 07:54:45
45.143.220.5 attackspambots
Scanned 1 times in the last 24 hours on port 5060
2020-05-17 08:26:56
180.101.233.130 attackbots
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2020-05-17 08:06:30

Recently Reported IPs

114.61.227.192 146.211.30.115 210.139.206.90 127.225.68.216
14.125.128.252 54.48.78.215 154.230.62.64 103.113.84.244
131.238.167.170 31.101.197.165 150.135.157.148 133.21.35.153
164.157.204.66 30.204.86.246 127.113.13.210 175.63.133.61
143.121.98.173 143.125.16.190 144.212.190.141 141.27.12.232