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

Region: California

Country: United States

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

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

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

;; Query time: 63 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Dec 05 01:01:29 CST 2019
;; MSG SIZE  rcvd: 117
Host info
242.69.16.214.in-addr.arpa domain name pointer dchp-69-242.rev.sd.mil.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
242.69.16.214.in-addr.arpa	name = dchp-69-242.rev.sd.mil.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
101.255.92.38 attackspambots
Unauthorized connection attempt detected from IP address 101.255.92.38 to port 8080 [J]
2020-03-01 06:11:04
220.134.29.165 attack
Unauthorized connection attempt detected from IP address 220.134.29.165 to port 23 [J]
2020-03-01 06:22:20
87.21.214.92 attack
Unauthorized connection attempt detected from IP address 87.21.214.92 to port 80 [J]
2020-03-01 06:13:09
154.160.66.42 attackbots
Feb 29 23:15:19 * sshd[28348]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=154.160.66.42
Feb 29 23:15:21 * sshd[28348]: Failed password for invalid user svnuser from 154.160.66.42 port 35968 ssh2
2020-03-01 06:34:18
172.96.171.222 attackspam
Unauthorized connection attempt detected from IP address 172.96.171.222 to port 23 [J]
2020-03-01 06:32:44
189.213.128.228 attackbotsspam
Unauthorized connection attempt detected from IP address 189.213.128.228 to port 23 [J]
2020-03-01 06:27:17
116.103.138.104 attackspambots
Unauthorized connection attempt detected from IP address 116.103.138.104 to port 23 [J]
2020-03-01 06:38:38
221.169.185.55 attackspambots
Unauthorized connection attempt detected from IP address 221.169.185.55 to port 23 [J]
2020-03-01 06:21:47
185.44.229.23 attackbots
Unauthorized connection attempt detected from IP address 185.44.229.23 to port 23 [J]
2020-03-01 06:29:25
106.1.188.234 attackbots
Unauthorized connection attempt detected from IP address 106.1.188.234 to port 23 [J]
2020-03-01 06:41:14
118.89.25.205 attackspambots
RDP Bruteforce
2020-03-01 06:07:26
45.83.65.6 attack
Unauthorized connection attempt detected from IP address 45.83.65.6 to port 22 [J]
2020-03-01 06:19:48
93.170.216.229 attackbotsspam
Unauthorized connection attempt detected from IP address 93.170.216.229 to port 23 [J]
2020-03-01 06:42:00
71.40.139.186 attack
Unauthorized connection attempt detected from IP address 71.40.139.186 to port 4567 [J]
2020-03-01 06:45:41
113.22.187.87 attack
Unauthorized connection attempt detected from IP address 113.22.187.87 to port 23 [J]
2020-03-01 06:09:34

Recently Reported IPs

237.115.218.29 113.179.142.91 84.3.122.229 112.78.37.38
13.8.201.7 202.67.46.18 103.56.114.212 36.79.248.38
92.34.11.168 72.115.249.0 103.81.182.83 157.133.224.36
148.54.88.90 1.253.97.138 147.51.28.197 24.40.135.70
150.108.102.63 67.170.50.45 43.63.125.68 2.147.38.41