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

;; QUESTION SECTION:
;216.145.14.142.			IN	A

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

;; Query time: 20 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 13 16:45:33 CST 2022
;; MSG SIZE  rcvd: 107
Host info
142.14.145.216.in-addr.arpa domain name pointer ipv4-216-145-14-142.greenhousedata.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
142.14.145.216.in-addr.arpa	name = ipv4-216-145-14-142.greenhousedata.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
73.229.232.218 attackspam
Aug 16 17:26:45 web9 sshd\[28654\]: Invalid user mj from 73.229.232.218
Aug 16 17:26:45 web9 sshd\[28654\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=73.229.232.218
Aug 16 17:26:46 web9 sshd\[28654\]: Failed password for invalid user mj from 73.229.232.218 port 48262 ssh2
Aug 16 17:33:22 web9 sshd\[30148\]: Invalid user owner from 73.229.232.218
Aug 16 17:33:22 web9 sshd\[30148\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=73.229.232.218
2019-08-17 11:34:43
112.252.31.28 attack
Port Scan: TCP/80
2019-08-17 12:08:42
31.172.80.89 attackspambots
Aug 17 00:22:29 cp sshd[32572]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=31.172.80.89
2019-08-17 12:07:53
78.186.208.216 attackspambots
Aug 17 03:09:50 XXX sshd[31755]: Invalid user sn from 78.186.208.216 port 44072
2019-08-17 11:59:17
201.217.58.136 attackbots
SSH Brute-Forcing (ownc)
2019-08-17 11:31:54
104.248.71.7 attackbots
Aug 17 05:42:32 vps691689 sshd[4293]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.71.7
Aug 17 05:42:35 vps691689 sshd[4293]: Failed password for invalid user mysql from 104.248.71.7 port 55976 ssh2
Aug 17 05:46:44 vps691689 sshd[4454]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.71.7
...
2019-08-17 11:50:50
223.196.89.130 attack
Aug 17 04:49:34 [munged] sshd[12403]: Invalid user oracle from 223.196.89.130 port 53308
Aug 17 04:49:34 [munged] sshd[12403]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=223.196.89.130
2019-08-17 11:42:39
185.139.21.21 attack
Tried sshing with brute force.
2019-08-17 12:02:33
46.174.8.3 attack
Chat Spam
2019-08-17 11:43:28
185.228.82.92 attackbots
Brute force attempt
2019-08-17 11:26:36
167.86.125.29 attackbots
404 NOT FOUND
2019-08-17 11:40:21
111.37.171.159 attackbots
:
2019-08-17 11:36:39
121.43.180.99 attackbots
WordPress brute force
2019-08-17 11:27:24
170.233.117.32 attackbots
Splunk® : Brute-Force login attempt on SSH:
Aug 16 15:59:59 testbed sshd[17063]: Disconnected from 170.233.117.32 port 35164 [preauth]
2019-08-17 11:44:46
190.72.110.195 attack
Unauthorized connection attempt from IP address 190.72.110.195 on Port 445(SMB)
2019-08-17 11:32:48

Recently Reported IPs

216.146.234.183 216.151.183.4 216.151.191.23 216.146.234.190
216.151.191.86 216.154.33.250 216.185.247.108 216.18.240.68
216.189.0.240 216.202.203.252 216.151.183.123 216.155.93.161
216.177.164.149 216.218.152.168 216.24.179.130 216.24.226.98
216.215.56.181 216.243.51.119 216.24.176.116 216.21.213.58