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

Region: Georgia

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

;; QUESTION SECTION:
;85.239.52.141.			IN	A

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

;; Query time: 73 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Oct 03 06:08:25 CST 2023
;; MSG SIZE  rcvd: 106
Host info
141.52.239.85.in-addr.arpa domain name pointer occaecaz.transnet.pics.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
141.52.239.85.in-addr.arpa	name = occaecaz.transnet.pics.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
159.203.201.150 attackbotsspam
54607/tcp 109/tcp 4330/tcp...
[2019-09-12/10-25]35pkt,31pt.(tcp),1pt.(udp)
2019-10-25 21:48:21
154.68.39.6 attack
SSH Brute-Force reported by Fail2Ban
2019-10-25 21:50:08
199.249.230.82 attackbotsspam
Automatic report - XMLRPC Attack
2019-10-25 22:06:37
124.156.139.104 attackspam
$f2bV_matches
2019-10-25 21:53:19
159.203.47.205 attackbots
$f2bV_matches
2019-10-25 21:58:51
193.32.163.182 attack
Oct 25 14:24:53 localhost sshd\[25280\]: Invalid user admin from 193.32.163.182 port 50255
Oct 25 14:24:53 localhost sshd\[25280\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.32.163.182
Oct 25 14:24:55 localhost sshd\[25280\]: Failed password for invalid user admin from 193.32.163.182 port 50255 ssh2
...
2019-10-25 22:28:33
202.129.29.135 attackspam
Oct 25 16:36:30 sauna sshd[221144]: Failed password for root from 202.129.29.135 port 38972 ssh2
...
2019-10-25 21:51:46
178.128.97.154 attack
Oct 25 19:08:29 lcl-usvr-02 sshd[10343]: Invalid user support from 178.128.97.154 port 59231
Oct 25 19:08:29 lcl-usvr-02 sshd[10343]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.97.154
Oct 25 19:08:29 lcl-usvr-02 sshd[10343]: Invalid user support from 178.128.97.154 port 59231
Oct 25 19:08:30 lcl-usvr-02 sshd[10343]: Failed password for invalid user support from 178.128.97.154 port 59231 ssh2
...
2019-10-25 22:17:07
218.92.0.145 attackbots
ssh brute force
2019-10-25 21:47:23
181.48.29.35 attackbots
Oct 25 15:08:53 MK-Soft-VM6 sshd[11337]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.48.29.35 
Oct 25 15:08:55 MK-Soft-VM6 sshd[11337]: Failed password for invalid user sinta from 181.48.29.35 port 41520 ssh2
...
2019-10-25 22:06:10
72.139.119.82 attack
Oct 22 17:15:09 reporting sshd[16087]: Address 72.139.119.82 maps to unallocated-static.rogers.com, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Oct 22 17:15:09 reporting sshd[16087]: User r.r from 72.139.119.82 not allowed because not listed in AllowUsers
Oct 22 17:15:09 reporting sshd[16087]: Failed password for invalid user r.r from 72.139.119.82 port 36512 ssh2
Oct 22 17:32:17 reporting sshd[25091]: Address 72.139.119.82 maps to unallocated-static.rogers.com, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Oct 22 17:32:17 reporting sshd[25091]: Invalid user openstack from 72.139.119.82
Oct 22 17:32:17 reporting sshd[25091]: Failed password for invalid user openstack from 72.139.119.82 port 58054 ssh2
Oct 22 17:36:37 reporting sshd[27193]: Address 72.139.119.82 maps to unallocated-static.rogers.com, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Oct 22 17:36:37 reporting sshd[27193]: User r.r fr........
-------------------------------
2019-10-25 22:05:40
223.171.32.55 attackspam
Oct 25 14:00:06 game-panel sshd[18293]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=223.171.32.55
Oct 25 14:00:08 game-panel sshd[18293]: Failed password for invalid user 123 from 223.171.32.55 port 35176 ssh2
Oct 25 14:05:13 game-panel sshd[18453]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=223.171.32.55
2019-10-25 22:18:44
134.175.121.145 attack
Oct 25 14:09:14 *** sshd[14334]: User root from 134.175.121.145 not allowed because not listed in AllowUsers
2019-10-25 22:10:05
117.117.165.131 attackspambots
Oct 25 15:48:28 eventyay sshd[14208]: Failed password for root from 117.117.165.131 port 51763 ssh2
Oct 25 15:53:04 eventyay sshd[14251]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.117.165.131
Oct 25 15:53:06 eventyay sshd[14251]: Failed password for invalid user ftpuser from 117.117.165.131 port 36998 ssh2
...
2019-10-25 22:00:50
221.226.58.102 attackspam
Oct 25 02:03:22 tdfoods sshd\[14956\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.226.58.102  user=root
Oct 25 02:03:24 tdfoods sshd\[14956\]: Failed password for root from 221.226.58.102 port 60272 ssh2
Oct 25 02:08:28 tdfoods sshd\[15352\]: Invalid user misionamaras from 221.226.58.102
Oct 25 02:08:28 tdfoods sshd\[15352\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.226.58.102
Oct 25 02:08:30 tdfoods sshd\[15352\]: Failed password for invalid user misionamaras from 221.226.58.102 port 35806 ssh2
2019-10-25 22:25:55

Recently Reported IPs

221.199.96.40 192.147.208.200 152.20.37.179 91.105.7.172
0.70.170.220 49.208.238.201 184.129.119.79 152.213.39.47
231.105.17.42 169.11.80.199 128.230.194.3 245.67.218.37
218.194.78.172 184.191.4.14 156.222.83.251 136.140.175.238
87.34.115.185 97.32.250.173 68.32.29.181 79.53.238.24