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
139.9.222.188 attackspam
139.9.222.188 - - [26/Nov/2019:05:54:04 +0100] "POST //plus/moon.php HTTP/1.1" 301 615
...
2019-11-26 14:14:28
139.9.222.188 attackspambots
/user.php?act=login
2019-11-04 05:23:37
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 139.9.222.242
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 59178
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;139.9.222.242.			IN	A

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

;; Query time: 55 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 27 12:41:43 CST 2022
;; MSG SIZE  rcvd: 106
Host info
242.222.9.139.in-addr.arpa domain name pointer ecs-139-9-222-242.compute.hwclouds-dns.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
242.222.9.139.in-addr.arpa	name = ecs-139-9-222-242.compute.hwclouds-dns.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
119.28.29.169 attackspambots
Unauthorized connection attempt detected from IP address 119.28.29.169 to port 2220 [J]
2020-01-17 02:11:36
49.235.42.177 attack
Jan 16 12:48:58 XXX sshd[3805]: Invalid user kasandra from 49.235.42.177 port 46070
2020-01-17 02:05:47
160.178.85.65 attackbotsspam
SSH_scan
2020-01-17 02:04:50
138.68.82.194 attackbots
Unauthorized connection attempt detected from IP address 138.68.82.194 to port 2220 [J]
2020-01-17 02:19:52
120.132.30.27 attack
Unauthorized connection attempt detected from IP address 120.132.30.27 to port 2220 [J]
2020-01-17 02:11:51
41.250.116.34 attack
SSH_scan
2020-01-17 02:06:03
104.37.169.192 attack
Unauthorized connection attempt detected from IP address 104.37.169.192 to port 2220 [J]
2020-01-17 02:39:15
206.189.124.254 attack
Unauthorized connection attempt detected from IP address 206.189.124.254 to port 2220 [J]
2020-01-17 02:29:21
211.142.118.38 attackbots
Jan 16 18:52:13 mout sshd[11805]: Invalid user tep from 211.142.118.38 port 33388
2020-01-17 02:12:30
64.188.16.37 attackbotsspam
Unauthorized connection attempt detected from IP address 64.188.16.37 to port 2220 [J]
2020-01-17 02:09:40
103.1.209.245 attackbotsspam
Unauthorized connection attempt detected from IP address 103.1.209.245 to port 2220 [J]
2020-01-17 02:39:47
125.213.150.7 attackbots
SSH Brute Force
2020-01-17 02:35:42
183.82.99.100 attack
Unauthorized connection attempt from IP address 183.82.99.100 on Port 445(SMB)
2020-01-17 02:01:18
171.239.194.52 attackbots
Jan 16 14:13:30 MK-Soft-VM7 sshd[18059]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=171.239.194.52 
Jan 16 14:13:32 MK-Soft-VM7 sshd[18059]: Failed password for invalid user guest from 171.239.194.52 port 52013 ssh2
...
2020-01-17 02:08:20
80.20.39.42 attackspambots
Invalid user kyle from 80.20.39.42 port 53300
2020-01-17 02:10:22

Recently Reported IPs

139.9.197.184 139.9.121.90 139.9.116.80 139.9.220.250
139.9.237.251 139.9.59.33 139.9.52.140 83.77.242.172
139.9.60.191 139.9.82.18 139.95.5.169 139.91.201.52
139.99.114.79 139.9.73.218 139.91.90.206 139.9.3.83
139.99.112.118 139.99.115.56 139.99.116.135 139.99.122.139