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

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.59.44.117 attackspam
Aug 18 11:41:11 h2040555 sshd[7686]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.44.117  user=r.r
Aug 18 11:41:13 h2040555 sshd[7686]: Failed password for r.r from 139.59.44.117 port 60460 ssh2
Aug 18 11:41:13 h2040555 sshd[7686]: Received disconnect from 139.59.44.117: 11: Bye Bye [preauth]
Aug 18 11:55:56 h2040555 sshd[7756]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.44.117  user=r.r
Aug 18 11:55:58 h2040555 sshd[7756]: Failed password for r.r from 139.59.44.117 port 38502 ssh2
Aug 18 11:55:58 h2040555 sshd[7756]: Received disconnect from 139.59.44.117: 11: Bye Bye [preauth]
Aug 18 12:00:26 h2040555 sshd[7779]: Invalid user norbert from 139.59.44.117
Aug 18 12:00:26 h2040555 sshd[7779]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.44.117 
Aug 18 12:00:28 h2040555 sshd[7779]: Failed password for invalid user norbert f........
-------------------------------
2020-08-21 07:12:06
139.59.44.173 attackbots
SSH login attempts.
2020-05-28 17:44:47
139.59.44.173 attack
k+ssh-bruteforce
2020-05-25 23:25:30
139.59.44.173 attackspam
$f2bV_matches
2020-05-01 15:41:38
139.59.44.173 attack
Apr 16 16:31:19 ny01 sshd[3501]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.44.173
Apr 16 16:31:21 ny01 sshd[3501]: Failed password for invalid user qb from 139.59.44.173 port 35638 ssh2
Apr 16 16:35:35 ny01 sshd[4118]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.44.173
2020-04-17 04:42:44
139.59.44.173 attackbots
Apr 10 11:11:53 webhost01 sshd[11076]: Failed password for root from 139.59.44.173 port 33668 ssh2
Apr 10 11:20:39 webhost01 sshd[11226]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.44.173
...
2020-04-10 12:32:42
139.59.44.173 attackbots
Invalid user ling from 139.59.44.173 port 45770
2020-03-21 22:53:32
139.59.44.173 attack
Mar 19 08:04:02 OPSO sshd\[28912\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.44.173  user=apache
Mar 19 08:04:05 OPSO sshd\[28912\]: Failed password for apache from 139.59.44.173 port 56440 ssh2
Mar 19 08:07:51 OPSO sshd\[29625\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.44.173  user=root
Mar 19 08:07:52 OPSO sshd\[29625\]: Failed password for root from 139.59.44.173 port 34124 ssh2
Mar 19 08:11:33 OPSO sshd\[30289\]: Invalid user newuser from 139.59.44.173 port 40038
Mar 19 08:11:33 OPSO sshd\[30289\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.44.173
2020-03-19 15:27:25
139.59.44.173 attackspambots
Unauthorized connection attempt detected from IP address 139.59.44.173 to port 2220 [J]
2020-02-03 05:15:20
139.59.44.173 attackbots
Invalid user sambhav from 139.59.44.173 port 54112
2020-01-31 07:28:05
139.59.44.104 attackbotsspam
19/11/7@01:21:17: FAIL: IoT-SSH address from=139.59.44.104
...
2019-11-07 20:50:14
139.59.44.223 attackspambots
xmlrpc attack
2019-08-25 06:16:34
139.59.44.60 attack
Triggered by Fail2Ban at Vostok web server
2019-07-11 22:13:18
139.59.44.60 attackspambots
SSH-bruteforce attempts
2019-07-11 04:53:45
139.59.44.60 attackbots
22/tcp 22/tcp 22/tcp...
[2019-06-25/07-10]19pkt,1pt.(tcp)
2019-07-10 21:19:22
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 139.59.44.13
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 29506
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;139.59.44.13.			IN	A

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

;; Query time: 80 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 27 17:37:49 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 13.44.59.139.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 13.44.59.139.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
51.91.248.153 attack
2019-08-08T19:32:39.422973abusebot-7.cloudsearch.cf sshd\[11386\]: Invalid user franklin from 51.91.248.153 port 40666
2019-08-09 05:45:11
138.68.174.198 attack
Detected by Synology server trying to access the inactive 'admin' account
2019-08-09 05:29:35
89.28.162.24 attack
@LucianNitescu Personal Honeypot Network <<<>>> Donate at paypal.me/LNitescu <<<>>> 2019-08-08 10:29:57,433 INFO [amun_request_handler] PortScan Detected on Port: 445 (89.28.162.24)
2019-08-09 05:54:50
38.64.128.3 attackbots
@LucianNitescu Personal Honeypot Network <<<>>> Donate at paypal.me/LNitescu <<<>>> 2019-08-08 10:30:40,521 INFO [amun_request_handler] PortScan Detected on Port: 445 (38.64.128.3)
2019-08-09 05:53:11
79.1.205.47 attackspam
Postfix RBL failed
2019-08-09 05:18:28
217.218.250.144 attackspambots
@LucianNitescu Personal Honeypot Network <<<>>> Donate at paypal.me/LNitescu <<<>>> 2019-08-08 10:26:40,566 INFO [amun_request_handler] PortScan Detected on Port: 445 (217.218.250.144)
2019-08-09 06:01:21
106.13.28.62 attackspambots
Lines containing failures of 106.13.28.62
Aug  8 13:34:33 serverjouille sshd[11853]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.28.62  user=proxy
Aug  8 13:34:35 serverjouille sshd[11853]: Failed password for proxy from 106.13.28.62 port 36690 ssh2


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=106.13.28.62
2019-08-09 05:59:39
203.177.19.123 attackspambots
SSH bruteforce
2019-08-09 05:48:18
190.95.221.216 attackspambots
Aug  8 13:26:22 mxgate1 postfix/postscreen[27510]: CONNECT from [190.95.221.216]:60731 to [176.31.12.44]:25
Aug  8 13:26:22 mxgate1 postfix/dnsblog[27511]: addr 190.95.221.216 listed by domain ix.dnsbl.xxxxxx.net as 127.0.0.2
Aug  8 13:26:22 mxgate1 postfix/dnsblog[27515]: addr 190.95.221.216 listed by domain b.barracudacentral.org as 127.0.0.2
Aug  8 13:26:28 mxgate1 postfix/postscreen[27510]: DNSBL rank 2 for [190.95.221.216]:60731
Aug  8 13:26:28 mxgate1 postfix/tlsproxy[27743]: CONNECT from [190.95.221.216]:60731
Aug x@x
Aug  8 13:26:30 mxgate1 postfix/postscreen[27510]: DISCONNECT [190.95.221.216]:60731
Aug  8 13:26:30 mxgate1 postfix/tlsproxy[27743]: DISCONNECT [190.95.221.216]:60731


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=190.95.221.216
2019-08-09 05:35:58
84.235.57.61 attack
@LucianNitescu Personal Honeypot Network <<<>>> Donate at paypal.me/LNitescu <<<>>> 2019-08-08 10:30:55,557 INFO [amun_request_handler] PortScan Detected on Port: 445 (84.235.57.61)
2019-08-09 05:51:21
165.227.150.158 attackspam
Aug  8 23:33:50 ubuntu-2gb-nbg1-dc3-1 sshd[30609]: Failed password for root from 165.227.150.158 port 35958 ssh2
Aug  8 23:37:31 ubuntu-2gb-nbg1-dc3-1 sshd[30834]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.227.150.158
...
2019-08-09 05:58:35
142.93.101.148 attack
Automatic report - Banned IP Access
2019-08-09 06:03:36
45.40.134.20 attackspambots
WordPress login Brute force / Web App Attack on client site.
2019-08-09 05:46:51
79.137.84.144 attack
$f2bV_matches_ltvn
2019-08-09 05:32:19
138.97.245.25 attackspambots
SASL Brute Force
2019-08-09 05:45:44

Recently Reported IPs

139.59.50.157 139.59.48.241 139.59.42.150 139.59.45.208
139.59.54.150 139.59.46.241 139.59.51.111 139.59.44.236
139.59.4.9 139.59.42.52 139.59.57.175 139.59.60.8
139.59.63.220 139.59.65.142 139.59.6.190 139.59.58.171
139.59.68.97 139.59.61.61 139.59.6.80 139.59.66.50