139.59.91.130 - IPInfo

Basic Info

City: unknown

Region: unknown

Country: Singapore

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:

Make a comment on this IP

No discussion about this IP yet. Click above link to make one.

Comments on same subnet:

IP	Type	Details	Datetime
139.59.91.254	attackspambots	Jul 19 18:06:47 ajax sshd[11849]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.91.254 Jul 19 18:06:49 ajax sshd[11849]: Failed password for invalid user postgres from 139.59.91.254 port 48234 ssh2	2020-07-20 01:26:19
139.59.91.23	attackbots	Invalid user admin from 139.59.91.23 port 53526	2020-04-17 14:06:35
139.59.91.23	attack	Apr 16 13:44:27 www_kotimaassa_fi sshd[16132]: Failed password for root from 139.59.91.23 port 55098 ssh2 ...	2020-04-17 01:24:59
139.59.91.22	attackspam	Jan 19 22:08:06 vpn01 sshd[29170]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.91.22 Jan 19 22:08:08 vpn01 sshd[29170]: Failed password for invalid user hosting from 139.59.91.22 port 51236 ssh2 ...	2020-01-20 05:54:07
139.59.91.165	attackspambots	Unauthorized connection attempt detected from IP address 139.59.91.165 to port 2220 [J]	2020-01-15 09:26:31
139.59.91.165	attackspam	Unauthorized connection attempt detected from IP address 139.59.91.165 to port 2220 [J]	2020-01-14 20:38:18
139.59.91.176	attackspam	Nov 28 13:11:23 vpn01 sshd[12983]: Failed password for root from 139.59.91.176 port 56023 ssh2 ...	2019-11-28 22:31:15
139.59.91.176	attackspambots	Nov 27 15:03:21 vpn01 sshd[26949]: Failed password for root from 139.59.91.176 port 38403 ssh2 ...	2019-11-27 22:08:31
139.59.91.215	attackspam	2019-11-24T07:59:53.405861matrix.arvenenaske.de sshd[358984]: Invalid user mysql from 139.59.91.215 port 37302 2019-11-24T07:59:53.410726matrix.arvenenaske.de sshd[358984]: pam_sss(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.91.215 user=mysql 2019-11-24T07:59:53.411274matrix.arvenenaske.de sshd[358984]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.91.215 2019-11-24T07:59:53.405861matrix.arvenenaske.de sshd[358984]: Invalid user mysql from 139.59.91.215 port 37302 2019-11-24T07:59:55.437052matrix.arvenenaske.de sshd[358984]: Failed password for invalid user mysql from 139.59.91.215 port 37302 ssh2 2019-11-24T08:06:20.413519matrix.arvenenaske.de sshd[359101]: Invalid user adhhostname from 139.59.91.215 port 50514 2019-11-24T08:06:20.418255matrix.arvenenaske.de sshd[359101]: pam_sss(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.91.215 user=adhh........ ------------------------------	2019-11-25 02:46:00
139.59.91.176	attackbots	detected by Fail2Ban	2019-11-10 19:30:54
139.59.91.176	attackspam	Nov 7 08:26:32 vpn01 sshd[15260]: Failed password for root from 139.59.91.176 port 44660 ssh2 ...	2019-11-07 20:11:37
139.59.91.139	attackspambots	(sshd) Failed SSH login from 139.59.91.139 (-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Sep 26 08:37:12 chookity sshd[30151]: Did not receive identification string from 139.59.91.139 port 60946 Sep 26 08:40:19 chookity sshd[30312]: Invalid user doctor from 139.59.91.139 port 33116 Sep 26 08:40:47 chookity sshd[30323]: Invalid user virus from 139.59.91.139 port 48666 Sep 26 08:41:15 chookity sshd[30326]: Invalid user windows from 139.59.91.139 port 37018 Sep 26 08:41:42 chookity sshd[30334]: Invalid user dummy from 139.59.91.139 port 52776	2019-09-26 21:00:58
139.59.91.139	attackspambots	Sep 4 02:20:00 vpn01 sshd\[21555\]: Invalid user quan from 139.59.91.139 Sep 4 02:20:00 vpn01 sshd\[21555\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.91.139 Sep 4 02:20:02 vpn01 sshd\[21555\]: Failed password for invalid user quan from 139.59.91.139 port 53652 ssh2	2019-09-04 11:00:48
139.59.91.139	attackbots	Sep 3 04:30:17 lcl-usvr-02 sshd[11852]: Invalid user patrick from 139.59.91.139 port 52970 Sep 3 04:30:17 lcl-usvr-02 sshd[11852]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.91.139 Sep 3 04:30:17 lcl-usvr-02 sshd[11852]: Invalid user patrick from 139.59.91.139 port 52970 Sep 3 04:30:18 lcl-usvr-02 sshd[11852]: Failed password for invalid user patrick from 139.59.91.139 port 52970 ssh2 Sep 3 04:34:49 lcl-usvr-02 sshd[12866]: Invalid user test from 139.59.91.139 port 51652 ...	2019-09-03 05:51:44
139.59.91.139	attack	Aug 15 10:51:50 localhost sshd[25589]: Invalid user est from 139.59.91.139 port 46252 Aug 15 10:51:50 localhost sshd[25589]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.91.139 Aug 15 10:51:50 localhost sshd[25589]: Invalid user est from 139.59.91.139 port 46252 Aug 15 10:51:52 localhost sshd[25589]: Failed password for invalid user est from 139.59.91.139 port 46252 ssh2 ...	2019-08-15 16:18:48

Whois info:

Dig info:

; <<>> DiG 9.10.3-P4-Ubuntu <<>> 139.59.91.130
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 1065
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;139.59.91.130.			IN	A

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

;; Query time: 77 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 27 17:38:08 CST 2022
;; MSG SIZE  rcvd: 106

Host info

Host 130.91.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 130.91.59.139.in-addr.arpa: NXDOMAIN

Related IP info:

Related comments:

IP	Type	Details	Datetime
177.126.165.170	attackbotsspam	Dec 2 04:03:10 clarabelen sshd[23730]: Address 177.126.165.170 maps to mm5-170.resultmarketing3.com.br, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT! Dec 2 04:03:10 clarabelen sshd[23730]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.126.165.170 user=r.r Dec 2 04:03:12 clarabelen sshd[23730]: Failed password for r.r from 177.126.165.170 port 40008 ssh2 Dec 2 04:03:12 clarabelen sshd[23730]: Received disconnect from 177.126.165.170: 11: Bye Bye [preauth] Dec 2 04:12:19 clarabelen sshd[24396]: Address 177.126.165.170 maps to mm5-170.resultmarketing3.com.br, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT! Dec 2 04:12:19 clarabelen sshd[24396]: Invalid user action from 177.126.165.170 Dec 2 04:12:19 clarabelen sshd[24396]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.126.165.170 Dec 2 04:12:22 clarabelen sshd[24396]: Failed ........ -------------------------------	2019-12-04 03:51:36
105.186.122.95	attack	Automatic report - Port Scan Attack	2019-12-04 04:15:51
81.130.187.49	attackspambots	Fail2Ban Ban Triggered	2019-12-04 03:44:46
207.180.254.181	attackbots	Dec 3 20:25:10 dedicated sshd[26278]: Invalid user toto from 207.180.254.181 port 40794	2019-12-04 03:43:39
37.59.224.39	attack	$f2bV_matches	2019-12-04 03:54:49
189.8.68.56	attackspam	Dec 3 20:08:11 vs01 sshd[28066]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.8.68.56 Dec 3 20:08:13 vs01 sshd[28066]: Failed password for invalid user ahto123 from 189.8.68.56 port 39930 ssh2 Dec 3 20:15:17 vs01 sshd[640]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.8.68.56	2019-12-04 03:45:31
187.18.108.73	attackbotsspam	Dec 3 19:41:06 heissa sshd\[8727\]: Invalid user wallant from 187.18.108.73 port 48505 Dec 3 19:41:06 heissa sshd\[8727\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=r237-pw-guarapo.ibys.com.br Dec 3 19:41:09 heissa sshd\[8727\]: Failed password for invalid user wallant from 187.18.108.73 port 48505 ssh2 Dec 3 19:50:20 heissa sshd\[10108\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=r237-pw-guarapo.ibys.com.br user=root Dec 3 19:50:22 heissa sshd\[10108\]: Failed password for root from 187.18.108.73 port 41150 ssh2	2019-12-04 04:12:02
179.113.83.106	attackbots	Dec 3 01:11:07 server sshd\[22247\]: Invalid user lisa from 179.113.83.106 Dec 3 01:11:07 server sshd\[22247\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.113.83.106 Dec 3 01:11:09 server sshd\[22247\]: Failed password for invalid user lisa from 179.113.83.106 port 40424 ssh2 Dec 3 21:15:06 server sshd\[23444\]: Invalid user guest from 179.113.83.106 Dec 3 21:15:06 server sshd\[23444\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.113.83.106 ...	2019-12-04 03:51:16
145.239.94.191	attackspambots	SSH brute-force: detected 6 distinct usernames within a 24-hour window.	2019-12-04 03:42:42
182.61.14.224	attackbotsspam	2019-12-03T17:22:46.586230abusebot-6.cloudsearch.cf sshd\[11203\]: Invalid user mfajre from 182.61.14.224 port 36116	2019-12-04 03:37:45
113.31.112.11	attack	no	2019-12-04 03:40:04
45.40.194.129	attack	Failed password for root from 45.40.194.129 port 51458 ssh2	2019-12-04 04:00:29
132.232.113.102	attack	SSH bruteforce	2019-12-04 03:38:31
118.91.255.14	attackbotsspam	ssh intrusion attempt	2019-12-04 03:55:52
193.188.22.188	attackspambots	2019-12-03T19:37:46.940012abusebot-7.cloudsearch.cf sshd\[5253\]: Invalid user media from 193.188.22.188 port 23984	2019-12-04 03:49:27

Recently Reported IPs

124.188.199.191	139.59.89.184	139.59.90.93	139.59.90.27
139.59.9.190	139.59.91.220	139.59.91.177	139.59.90.68
139.59.92.150	139.59.92.76	139.59.94.104	139.59.95.50
139.59.95.77	139.59.93.221	139.59.93.18	139.59.93.233
139.59.94.214	139.59.94.98	139.59.95.108	139.59.95.88