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 <<>> 114.220.204.50
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 44389
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;114.220.204.50.			IN	A

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

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jan 14 06:14:46 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 50.204.220.114.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 50.204.220.114.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
109.102.158.14 attackspam
Jan  6 07:08:58 ip-172-31-62-245 sshd\[30301\]: Invalid user guest from 109.102.158.14\
Jan  6 07:09:00 ip-172-31-62-245 sshd\[30301\]: Failed password for invalid user guest from 109.102.158.14 port 50262 ssh2\
Jan  6 07:12:26 ip-172-31-62-245 sshd\[30423\]: Invalid user ziyad from 109.102.158.14\
Jan  6 07:12:27 ip-172-31-62-245 sshd\[30423\]: Failed password for invalid user ziyad from 109.102.158.14 port 54110 ssh2\
Jan  6 07:16:00 ip-172-31-62-245 sshd\[30477\]: Invalid user go from 109.102.158.14\
2020-01-06 16:09:45
27.159.122.188 attackspam
Unauthorized connection attempt detected from IP address 27.159.122.188 to port 1433 [J]
2020-01-06 15:52:13
45.55.128.109 attackbotsspam
Unauthorized connection attempt detected from IP address 45.55.128.109 to port 2220 [J]
2020-01-06 15:51:21
95.158.8.26 attackspambots
Unauthorized connection attempt detected from IP address 95.158.8.26 to port 85 [J]
2020-01-06 15:45:02
85.105.228.236 attackspam
Unauthorized connection attempt detected from IP address 85.105.228.236 to port 23 [J]
2020-01-06 15:48:32
190.196.54.36 attack
Unauthorized connection attempt detected from IP address 190.196.54.36 to port 88 [J]
2020-01-06 15:59:15
159.203.65.34 attackspambots
Unauthorized connection attempt detected from IP address 159.203.65.34 to port 2220 [J]
2020-01-06 16:04:26
189.171.30.183 attack
Unauthorized connection attempt detected from IP address 189.171.30.183 to port 4567 [J]
2020-01-06 15:59:50
177.22.232.67 attack
Unauthorized connection attempt detected from IP address 177.22.232.67 to port 2323 [J]
2020-01-06 15:34:35
107.175.33.240 attackspam
Unauthorized connection attempt detected from IP address 107.175.33.240 to port 2220 [J]
2020-01-06 16:10:28
27.2.100.201 attackbotsspam
Unauthorized connection attempt detected from IP address 27.2.100.201 to port 5555 [J]
2020-01-06 15:52:29
112.16.143.202 attackspam
Unauthorized connection attempt detected from IP address 112.16.143.202 to port 4899 [J]
2020-01-06 16:09:13
124.156.64.176 attackbots
Unauthorized connection attempt detected from IP address 124.156.64.176 to port 902 [J]
2020-01-06 15:39:17
116.111.139.87 attack
Unauthorized connection attempt detected from IP address 116.111.139.87 to port 81 [J]
2020-01-06 16:07:33
201.21.120.90 attackspambots
Unauthorized connection attempt detected from IP address 201.21.120.90 to port 23 [J]
2020-01-06 15:57:51

Recently Reported IPs

58.162.53.25 227.167.103.41 3.225.5.48 198.50.86.240
34.213.171.217 17.195.103.175 53.196.127.92 220.156.251.6
17.120.84.221 17.218.176.234 94.241.95.213 72.146.122.143
252.121.137.145 151.185.245.182 193.14.18.137 63.28.176.68
131.33.35.78 134.31.221.246 35.57.125.55 244.233.145.44