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

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

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

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

;; Query time: 198 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Apr 08 02:06:59 CST 2020
;; MSG SIZE  rcvd: 118
Host info
Host 114.220.204.12.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 114.220.204.12.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
80.82.64.125 attack
sshd[...]: Invalid user admin from 80.82.64.214 port 30246
sshd[...]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.82.64.214
sshd[...]: Failed password for invalid user admin from 80.82.64.214 port 30246 ssh2
sshd[...]: Invalid user squid from 80.82.64.214 port 1674
sshd[...]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.82.64.214
sshd[...]: Failed password for invalid user squid from 80.82.64.214 port 1674 ssh2
2020-01-25 08:29:35
103.204.231.50 attackbots
Unauthorized connection attempt detected from IP address 103.204.231.50 to port 23 [J]
2020-01-25 08:08:55
82.62.55.178 attack
Unauthorized connection attempt detected from IP address 82.62.55.178 to port 88 [J]
2020-01-25 08:31:21
106.12.24.5 attack
Unauthorized connection attempt detected from IP address 106.12.24.5 to port 2220 [J]
2020-01-25 08:08:40
178.212.49.26 attackbotsspam
Unauthorized connection attempt detected from IP address 178.212.49.26 to port 80 [J]
2020-01-25 08:19:42
85.107.11.171 attack
Unauthorized connection attempt detected from IP address 85.107.11.171 to port 23 [J]
2020-01-25 08:09:27
119.199.29.166 attack
Unauthorized connection attempt detected from IP address 119.199.29.166 to port 23 [J]
2020-01-25 08:06:21
191.115.84.157 attackbots
Unauthorized connection attempt detected from IP address 191.115.84.157 to port 23 [J]
2020-01-25 08:15:52
80.182.12.231 attackbotsspam
Unauthorized connection attempt detected from IP address 80.182.12.231 to port 88 [J]
2020-01-25 08:32:20
111.231.141.221 attackbots
Unauthorized connection attempt detected from IP address 111.231.141.221 to port 2220 [J]
2020-01-25 08:26:44
109.224.52.186 attackspambots
Unauthorized connection attempt detected from IP address 109.224.52.186 to port 23 [J]
2020-01-25 08:07:48
42.119.204.47 attackspambots
Unauthorized connection attempt detected from IP address 42.119.204.47 to port 23 [J]
2020-01-25 08:11:01
145.236.38.128 attackbotsspam
Unauthorized connection attempt detected from IP address 145.236.38.128 to port 2220 [J]
2020-01-25 08:04:45
218.87.107.134 attackbots
Unauthorized connection attempt detected from IP address 218.87.107.134 to port 1433 [J]
2020-01-25 08:41:16
193.105.235.241 attackspam
Unauthorized connection attempt detected from IP address 193.105.235.241 to port 1433 [J]
2020-01-25 08:15:32

Recently Reported IPs

54.173.47.250 245.143.114.64 118.233.14.188 198.71.62.217
195.154.251.142 36.92.132.98 183.89.237.24 185.189.160.21
143.204.190.71 103.242.2.175 45.133.99.11 252.154.74.68
106.13.237.226 210.138.87.15 67.87.187.228 36.112.41.194
197.61.12.122 139.199.18.200 91.83.175.74 14.18.54.30