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:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 139.255.145.44
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 58716
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;139.255.145.44.			IN	A

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

;; Query time: 44 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 08:29:10 CST 2022
;; MSG SIZE  rcvd: 107
Host info
44.145.255.139.in-addr.arpa domain name pointer ln-static-139-255-145-44.link.net.id.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
44.145.255.139.in-addr.arpa	name = ln-static-139-255-145-44.link.net.id.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
223.171.61.175 attack
Unauthorized connection attempt detected from IP address 223.171.61.175 to port 23 [J]
2020-03-03 02:37:51
223.71.167.165 attackbotsspam
Unauthorized connection attempt detected from IP address 223.71.167.165 to port 1720 [J]
2020-03-03 02:38:17
79.183.53.72 attack
Unauthorized connection attempt detected from IP address 79.183.53.72 to port 143 [J]
2020-03-03 02:30:43
122.51.203.249 attack
Unauthorized connection attempt detected from IP address 122.51.203.249 to port 1433 [J]
2020-03-03 02:48:00
125.31.26.139 attackbotsspam
Unauthorized connection attempt detected from IP address 125.31.26.139 to port 80 [J]
2020-03-03 02:47:35
222.186.175.154 attack
Mar  2 19:54:59 dedicated sshd[7778]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.154  user=root
Mar  2 19:55:01 dedicated sshd[7778]: Failed password for root from 222.186.175.154 port 63938 ssh2
2020-03-03 02:59:46
79.119.225.210 attack
Unauthorized connection attempt detected from IP address 79.119.225.210 to port 23 [J]
2020-03-03 02:30:58
91.185.193.145 attackbotsspam
Unauthorized connection attempt detected from IP address 91.185.193.145 to port 1433 [J]
2020-03-03 02:53:26
45.115.174.100 attackspam
Unauthorized connection attempt detected from IP address 45.115.174.100 to port 23 [J]
2020-03-03 02:57:35
79.137.86.205 attackbots
frenzy
2020-03-03 03:02:43
181.94.68.180 attackspam
Unauthorized connection attempt detected from IP address 181.94.68.180 to port 23 [J]
2020-03-03 02:43:58
158.69.110.31 attack
Mar  2 17:47:21 vpn01 sshd[4168]: Failed password for root from 158.69.110.31 port 36470 ssh2
...
2020-03-03 03:04:16
128.90.22.170 attackbotsspam
Unauthorized connection attempt detected from IP address 128.90.22.170 to port 587 [J]
2020-03-03 02:47:20
222.186.175.181 attackbotsspam
sshd jail - ssh hack attempt
2020-03-03 03:00:53
210.183.21.48 attack
Mar  2 18:53:31 MK-Soft-VM5 sshd[19687]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.183.21.48 
Mar  2 18:53:33 MK-Soft-VM5 sshd[19687]: Failed password for invalid user admin from 210.183.21.48 port 6010 ssh2
...
2020-03-03 03:04:30

Recently Reported IPs

139.255.145.31 118.250.2.189 139.255.145.182 139.255.144.172
139.255.149.156 139.255.145.40 139.255.149.71 139.255.151.139
139.255.149.38 139.255.153.43 139.255.153.36 139.255.151.137
139.255.151.144 139.255.152.197 139.255.153.50 118.250.2.218
139.255.154.113 139.255.156.24 139.255.155.25 139.255.158.147