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

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:
IP Type Details Datetime
139.255.53.26 attack
.
2020-05-22 03:21:57
139.255.53.26 attackspam
20/4/30@00:22:43: FAIL: Alarm-Network address from=139.255.53.26
20/4/30@00:22:44: FAIL: Alarm-Network address from=139.255.53.26
...
2020-04-30 19:38:47
139.255.53.178 attackspambots
Mar 20 06:21:31 ns37 sshd[8286]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.255.53.178
2020-03-20 14:28:40
139.255.53.178 attackbotsspam
Mar 16 23:47:53 sd-53420 sshd\[15983\]: Invalid user chenchengxin from 139.255.53.178
Mar 16 23:47:53 sd-53420 sshd\[15983\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.255.53.178
Mar 16 23:47:55 sd-53420 sshd\[15983\]: Failed password for invalid user chenchengxin from 139.255.53.178 port 42981 ssh2
Mar 16 23:52:05 sd-53420 sshd\[17269\]: User root from 139.255.53.178 not allowed because none of user's groups are listed in AllowGroups
Mar 16 23:52:05 sd-53420 sshd\[17269\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.255.53.178  user=root
...
2020-03-17 07:41:35
139.255.53.82 attackbots
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/139.255.53.82/ 
 
 ID - 1H : (48)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : ID 
 NAME ASN : ASN9905 
 
 IP : 139.255.53.82 
 
 CIDR : 139.255.52.0/22 
 
 PREFIX COUNT : 93 
 
 UNIQUE IP COUNT : 75008 
 
 
 ATTACKS DETECTED ASN9905 :  
  1H - 1 
  3H - 1 
  6H - 1 
 12H - 1 
 24H - 1 
 
 DateTime : 2019-10-21 13:45:24 
 
 INFO :  HACK ! - Looking for resource vulnerabilities Scan Detected and Blocked by ADMIN  - data recovery
2019-10-21 20:31:35
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 139.255.53.85
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 22297
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;139.255.53.85.			IN	A

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

;; Query time: 21 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 08:30:07 CST 2022
;; MSG SIZE  rcvd: 106
Host info
85.53.255.139.in-addr.arpa domain name pointer blast.firstwifi.id.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
85.53.255.139.in-addr.arpa	name = blast.firstwifi.id.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
223.247.140.89 attackbots
Scanned 6 times in the last 24 hours on port 22
2020-01-26 01:55:07
89.250.166.191 attackspam
Honeypot attack, port: 445, PTR: PTR record not found
2020-01-26 01:49:06
117.255.214.207 attack
Honeypot attack, port: 445, PTR: PTR record not found
2020-01-26 01:41:43
42.113.128.149 attackbotsspam
Honeypot attack, port: 445, PTR: PTR record not found
2020-01-26 01:48:07
106.124.131.70 attackbotsspam
$f2bV_matches
2020-01-26 01:40:53
83.34.192.185 attackspam
SSH/22 MH Probe, BF, Hack -
2020-01-26 01:44:13
131.255.216.0 attackspambots
Unauthorized connection attempt detected from IP address 131.255.216.0 to port 80 [J]
2020-01-26 02:10:32
193.112.174.67 attackbots
Unauthorized connection attempt detected from IP address 193.112.174.67 to port 2220 [J]
2020-01-26 01:38:35
220.137.94.1 attack
Unauthorized connection attempt detected from IP address 220.137.94.1 to port 23 [J]
2020-01-26 01:56:01
177.205.105.147 attackbots
Unauthorized connection attempt detected from IP address 177.205.105.147 to port 23 [J]
2020-01-26 02:07:57
220.77.95.154 attackspambots
Unauthorized connection attempt detected from IP address 220.77.95.154 to port 23 [J]
2020-01-26 02:04:12
102.40.69.28 attackspam
Unauthorized connection attempt detected from IP address 102.40.69.28 to port 23 [J]
2020-01-26 02:02:05
188.125.42.103 attack
2020-01-25T17:11:38.601115tmaserv sshd[29516]: Invalid user nginx from 188.125.42.103 port 54958
2020-01-25T17:11:38.603712tmaserv sshd[29516]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=apn-188-125-42-103.static.gprs.plus.pl
2020-01-25T17:11:38.601115tmaserv sshd[29516]: Invalid user nginx from 188.125.42.103 port 54958
2020-01-25T17:11:40.890281tmaserv sshd[29516]: Failed password for invalid user nginx from 188.125.42.103 port 54958 ssh2
2020-01-25T18:06:44.114471tmaserv sshd[32025]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=apn-188-125-42-103.static.gprs.plus.pl  user=root
2020-01-25T18:06:46.591829tmaserv sshd[32025]: Failed password for root from 188.125.42.103 port 46906 ssh2
2020-01-25T18:18:56.283473tmaserv sshd[32590]: Invalid user postgres from 188.125.42.103 port 43294
2020-01-25T18:18:56.287304tmaserv sshd[32590]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty
...
2020-01-26 01:51:23
93.86.60.152 attackspambots
proto=tcp  .  spt=58071  .  dpt=25  .     Found on   Dark List de      (443)
2020-01-26 01:43:02
109.242.228.84 attackbotsspam
Unauthorized connection attempt detected from IP address 109.242.228.84 to port 80 [J]
2020-01-26 02:14:43

Recently Reported IPs

139.255.52.70 139.255.48.164 139.255.55.146 139.255.55.34
139.255.54.106 139.255.55.10 139.255.56.18 139.255.54.186
139.255.57.18 139.255.57.1 139.255.57.32 118.254.140.50
139.255.58.202 139.255.56.82 139.255.59.18 139.255.58.233
139.255.60.122 139.255.6.106 139.255.60.236 139.255.61.130