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 of America (the)

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

;; QUESTION SECTION:
;161.102.234.142.		IN	A

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

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jan 29 13:53:19 CST 2025
;; MSG SIZE  rcvd: 108
Host info
Host 142.234.102.161.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 142.234.102.161.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
93.105.58.83 attack
Automatic report - SSH Brute-Force Attack
2020-01-19 13:39:14
212.36.40.221 attackspam
20/1/18@23:58:36: FAIL: Alarm-Network address from=212.36.40.221
...
2020-01-19 13:14:55
193.32.163.123 attackbots
SSH Brute-Force reported by Fail2Ban
2020-01-19 13:20:31
119.202.212.237 attack
Unauthorized connection attempt detected from IP address 119.202.212.237 to port 23 [J]
2020-01-19 13:44:50
212.64.54.49 attack
Unauthorized connection attempt detected from IP address 212.64.54.49 to port 2220 [J]
2020-01-19 13:28:38
183.89.64.3 attackspambots
1579409919 - 01/19/2020 05:58:39 Host: 183.89.64.3/183.89.64.3 Port: 445 TCP Blocked
2020-01-19 13:13:11
192.144.161.16 attack
Jan 19 01:57:33 firewall sshd[19031]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.144.161.16
Jan 19 01:57:33 firewall sshd[19031]: Invalid user usertest from 192.144.161.16
Jan 19 01:57:36 firewall sshd[19031]: Failed password for invalid user usertest from 192.144.161.16 port 56498 ssh2
...
2020-01-19 13:39:43
89.187.186.70 attackbots
MultiHost/MultiPort Probe, Scan, Hack -
2020-01-19 13:44:38
177.140.197.32 attack
Jan 19 05:31:27 ns382633 sshd\[10297\]: Invalid user track from 177.140.197.32 port 57792
Jan 19 05:31:27 ns382633 sshd\[10297\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.140.197.32
Jan 19 05:31:30 ns382633 sshd\[10297\]: Failed password for invalid user track from 177.140.197.32 port 57792 ssh2
Jan 19 05:57:31 ns382633 sshd\[14353\]: Invalid user jerome from 177.140.197.32 port 38011
Jan 19 05:57:31 ns382633 sshd\[14353\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.140.197.32
2020-01-19 13:41:31
185.153.199.210 attackbotsspam
Jan 19 05:57:51 vps sshd[25499]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.153.199.210 
Jan 19 05:57:53 vps sshd[25499]: Failed password for invalid user 0 from 185.153.199.210 port 47804 ssh2
Jan 19 05:58:34 vps sshd[25515]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.153.199.210 
...
2020-01-19 13:13:36
222.186.175.220 attackspam
Jan 19 06:37:52 vmanager6029 sshd\[27866\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.220  user=root
Jan 19 06:37:54 vmanager6029 sshd\[27866\]: Failed password for root from 222.186.175.220 port 20132 ssh2
Jan 19 06:37:57 vmanager6029 sshd\[27866\]: Failed password for root from 222.186.175.220 port 20132 ssh2
2020-01-19 13:40:32
132.232.29.208 attackspam
Jan 18 23:56:01 ny01 sshd[17155]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.232.29.208
Jan 18 23:56:04 ny01 sshd[17155]: Failed password for invalid user lx from 132.232.29.208 port 50642 ssh2
Jan 18 23:58:48 ny01 sshd[17594]: Failed password for root from 132.232.29.208 port 44320 ssh2
2020-01-19 13:09:06
154.8.209.64 attackbots
2020-01-19T05:09:11.498492shield sshd\[5846\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=154.8.209.64  user=root
2020-01-19T05:09:13.409200shield sshd\[5846\]: Failed password for root from 154.8.209.64 port 39900 ssh2
2020-01-19T05:11:52.223887shield sshd\[6930\]: Invalid user totto from 154.8.209.64 port 58974
2020-01-19T05:11:52.232732shield sshd\[6930\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=154.8.209.64
2020-01-19T05:11:53.912516shield sshd\[6930\]: Failed password for invalid user totto from 154.8.209.64 port 58974 ssh2
2020-01-19 13:34:44
157.230.39.232 attackspam
Jan 19 00:26:04 ny01 sshd[21475]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.230.39.232
Jan 19 00:26:05 ny01 sshd[21475]: Failed password for invalid user syed from 157.230.39.232 port 40270 ssh2
Jan 19 00:29:11 ny01 sshd[21960]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.230.39.232
2020-01-19 13:40:56
82.130.24.224 attackspambots
Unauthorized connection attempt detected from IP address 82.130.24.224 to port 22 [J]
2020-01-19 13:47:57

Recently Reported IPs

85.219.58.113 162.55.147.12 219.94.54.66 184.60.108.246
161.103.105.133 43.116.30.217 239.181.146.103 87.93.195.65
217.84.188.246 215.148.35.95 200.132.17.29 140.162.141.219
20.205.77.242 229.112.45.37 235.99.22.91 246.82.103.3
200.137.5.211 73.10.87.39 135.171.122.254 49.143.227.164