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

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

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

;; Query time: 105 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Apr 30 14:42:15 CST 2020
;; MSG SIZE  rcvd: 115
Host info
Host 66.2.160.11.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 66.2.160.11.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
216.218.206.66 attack
Unauthorized connection attempt detected from IP address 216.218.206.66 to port 389 [J]
2020-01-06 17:21:59
47.180.4.60 attackspam
Unauthorized connection attempt detected from IP address 47.180.4.60 to port 4567 [J]
2020-01-06 17:15:06
69.250.156.161 attackbots
Jan  6 09:19:53 SilenceServices sshd[14302]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=69.250.156.161
Jan  6 09:19:55 SilenceServices sshd[14302]: Failed password for invalid user qtb from 69.250.156.161 port 56176 ssh2
Jan  6 09:25:21 SilenceServices sshd[15905]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=69.250.156.161
2020-01-06 17:12:56
94.70.173.185 attack
Unauthorized connection attempt detected from IP address 94.70.173.185 to port 82 [J]
2020-01-06 17:38:23
94.73.228.117 attackspambots
Unauthorized connection attempt detected from IP address 94.73.228.117 to port 23 [J]
2020-01-06 17:06:31
41.239.100.160 attackspambots
Unauthorized connection attempt detected from IP address 41.239.100.160 to port 22 [J]
2020-01-06 17:17:02
123.20.161.102 attackspam
Unauthorized connection attempt detected from IP address 123.20.161.102 to port 22 [J]
2020-01-06 17:34:00
170.106.76.152 attack
Unauthorized connection attempt detected from IP address 170.106.76.152 to port 2002 [J]
2020-01-06 17:30:22
124.156.240.58 attack
Unauthorized connection attempt detected from IP address 124.156.240.58 to port 110 [J]
2020-01-06 17:33:19
61.61.236.28 attack
Unauthorized connection attempt detected from IP address 61.61.236.28 to port 5555 [J]
2020-01-06 17:13:20
138.94.84.219 attackspam
Unauthorized connection attempt detected from IP address 138.94.84.219 to port 8080 [J]
2020-01-06 17:31:25
184.105.139.70 attackspam
Unauthorized connection attempt detected from IP address 184.105.139.70 to port 389 [J]
2020-01-06 17:27:13
45.84.184.176 attackspambots
Unauthorized connection attempt detected from IP address 45.84.184.176 to port 23 [J]
2020-01-06 17:16:01
218.253.69.134 attackbotsspam
frenzy
2020-01-06 17:20:38
46.42.114.229 attackspam
Unauthorized connection attempt detected from IP address 46.42.114.229 to port 23 [J]
2020-01-06 17:15:43

Recently Reported IPs

52.234.133.36 72.211.52.153 45.254.26.25 123.54.7.49
45.95.169.249 124.240.199.2 83.174.129.212 198.206.243.23
158.69.254.173 168.195.128.190 178.51.97.195 118.69.53.12
31.13.115.23 162.243.144.211 172.55.244.207 31.13.115.25
112.96.105.200 79.124.79.28 114.109.237.142 84.155.243.54