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:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 119.102.130.21
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 7843
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;119.102.130.21.			IN	A

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

;; Query time: 64 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Mar 08 17:50:03 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 21.130.102.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 21.130.102.119.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
109.103.51.74 attackbots
Autoban   109.103.51.74 AUTH/CONNECT
2019-06-22 18:51:06
185.220.102.4 attack
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.220.102.4  user=root
Failed password for root from 185.220.102.4 port 36373 ssh2
Failed password for root from 185.220.102.4 port 36373 ssh2
Failed password for root from 185.220.102.4 port 36373 ssh2
Failed password for root from 185.220.102.4 port 36373 ssh2
2019-06-22 18:25:40
106.12.21.123 attackspam
2019-06-22T06:46:44.594460test01.cajus.name sshd\[32171\]: Invalid user tomcat from 106.12.21.123 port 41406
2019-06-22T06:46:44.614310test01.cajus.name sshd\[32171\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.21.123
2019-06-22T06:46:46.534469test01.cajus.name sshd\[32171\]: Failed password for invalid user tomcat from 106.12.21.123 port 41406 ssh2
2019-06-22 18:33:28
114.108.254.254 attackbots
TCP port 445 (SMB) attempt blocked by firewall. [2019-06-22 06:24:54]
2019-06-22 18:34:22
79.85.235.126 attack
Jun 22 06:24:37 srv02 sshd\[9127\]: Invalid user test from 79.85.235.126 port 45170
Jun 22 06:24:37 srv02 sshd\[9127\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=79.85.235.126
Jun 22 06:24:39 srv02 sshd\[9127\]: Failed password for invalid user test from 79.85.235.126 port 45170 ssh2
2019-06-22 18:51:41
14.215.46.94 attackspambots
Jun 22 08:54:50 MK-Soft-Root1 sshd\[32667\]: Invalid user minecraft from 14.215.46.94 port 33004
Jun 22 08:54:51 MK-Soft-Root1 sshd\[32667\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.215.46.94
Jun 22 08:54:53 MK-Soft-Root1 sshd\[32667\]: Failed password for invalid user minecraft from 14.215.46.94 port 33004 ssh2
...
2019-06-22 19:10:53
91.61.38.231 attackspambots
SSH login attempts brute force.
2019-06-22 18:34:44
104.248.185.25 attackbots
" "
2019-06-22 18:45:01
184.105.139.67 attackbots
3389/tcp 27017/tcp 7547/tcp...
[2019-04-22/06-22]253pkt,14pt.(tcp),2pt.(udp)
2019-06-22 18:31:41
194.28.115.244 attackbots
Scanning (more than 2 packets) random ports - tries to find possible vulnerable services
2019-06-22 18:51:59
85.113.162.42 attack
Scanning random ports - tries to find possible vulnerable services
2019-06-22 19:10:32
189.7.217.23 attackspam
Jun 22 10:11:12 amit sshd\[21309\]: Invalid user zabbix from 189.7.217.23
Jun 22 10:11:12 amit sshd\[21309\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.7.217.23
Jun 22 10:11:14 amit sshd\[21309\]: Failed password for invalid user zabbix from 189.7.217.23 port 59623 ssh2
...
2019-06-22 18:54:42
153.3.122.159 attackbots
Jun 22 06:46:16 apollo sshd\[28035\]: Failed password for root from 153.3.122.159 port 48878 ssh2Jun 22 06:46:18 apollo sshd\[28035\]: Failed password for root from 153.3.122.159 port 48878 ssh2Jun 22 06:46:21 apollo sshd\[28035\]: Failed password for root from 153.3.122.159 port 48878 ssh2
...
2019-06-22 19:09:28
86.142.127.63 attackbotsspam
Jun 21 00:22:24 hosname24 sshd[26919]: Bad protocol version identification '' from 86.142.127.63 port 33382
Jun 21 00:22:37 hosname24 sshd[26926]: Invalid user support from 86.142.127.63 port 34550
Jun 21 00:22:41 hosname24 sshd[26926]: Failed password for invalid user support from 86.142.127.63 port 34550 ssh2
Jun 21 00:22:46 hosname24 sshd[26926]: Connection closed by 86.142.127.63 port 34550 [preauth]
Jun 21 00:23:02 hosname24 sshd[26929]: Invalid user ubnt from 86.142.127.63 port 40950
Jun 21 00:23:05 hosname24 sshd[26929]: Failed password for invalid user ubnt from 86.142.127.63 port 40950 ssh2
Jun 21 00:23:08 hosname24 sshd[26929]: Connection closed by 86.142.127.63 port 40950 [preauth]
Jun 21 00:23:23 hosname24 sshd[26933]: Invalid user cisco from 86.142.127.63 port 47890
Jun 21 00:23:27 hosname24 sshd[26933]: Failed password for invalid user cisco from 86.142.127.63 port 47890 ssh2
Jun 21 00:23:32 hosname24 sshd[26933]: Connection closed by 86.142.127.63 port 47........
-------------------------------
2019-06-22 18:40:21
185.85.239.195 attack
Attempted WordPress login: "GET /wp-login.php"
2019-06-22 19:01:50

Recently Reported IPs

116.226.108.44 119.102.130.214 119.102.130.228 119.102.130.238
119.102.130.245 119.102.130.243 119.102.130.231 119.102.130.236
119.102.130.25 116.226.109.209 119.102.130.32 119.102.130.253
119.102.130.29 119.102.130.37 119.102.130.35 119.102.130.4
119.102.130.47 119.102.130.53 119.102.130.55 119.102.130.59