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

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.180.142.5 attack
Unauthorized connection attempt detected from IP address 139.180.142.5 to port 445 [T]
2020-07-22 01:09:30
139.180.142.152 attackspambots
2019-07-25T08:00:21.580792abusebot-6.cloudsearch.cf sshd\[14092\]: Invalid user Tech\$123 from 139.180.142.152 port 55358
2019-07-25 18:34:42
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 139.180.142.220
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 16618
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;139.180.142.220.		IN	A

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

;; Query time: 182 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 08:12:12 CST 2022
;; MSG SIZE  rcvd: 108
Host info
220.142.180.139.in-addr.arpa domain name pointer 139.180.142.220.vultr.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
220.142.180.139.in-addr.arpa	name = 139.180.142.220.vultr.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
62.234.44.43 attackspam
SSH Bruteforce attempt
2019-12-15 19:36:27
175.138.108.78 attackbots
Dec 15 12:30:25 vps647732 sshd[29217]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.138.108.78
Dec 15 12:30:28 vps647732 sshd[29217]: Failed password for invalid user euro from 175.138.108.78 port 42954 ssh2
...
2019-12-15 19:47:13
182.61.177.109 attackspam
sshd jail - ssh hack attempt
2019-12-15 19:43:07
193.112.9.189 attackspam
Brute-force attempt banned
2019-12-15 19:33:55
123.132.243.217 attackspam
Scanning
2019-12-15 19:59:42
222.168.122.245 attackbots
Dec 15 15:43:41 webhost01 sshd[24468]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.168.122.245
Dec 15 15:43:43 webhost01 sshd[24468]: Failed password for invalid user terre from 222.168.122.245 port 61785 ssh2
...
2019-12-15 20:12:04
91.222.19.225 attackspam
2019-12-15T11:25:56.050548shield sshd\[4126\]: Invalid user sittig from 91.222.19.225 port 55502
2019-12-15T11:25:56.056437shield sshd\[4126\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.222.19.225
2019-12-15T11:25:58.043721shield sshd\[4126\]: Failed password for invalid user sittig from 91.222.19.225 port 55502 ssh2
2019-12-15T11:31:42.992794shield sshd\[5172\]: Invalid user michal from 91.222.19.225 port 36132
2019-12-15T11:31:42.998623shield sshd\[5172\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.222.19.225
2019-12-15 20:00:57
134.209.16.36 attackspam
Dec 15 11:25:21 gw1 sshd[4398]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.16.36
Dec 15 11:25:23 gw1 sshd[4398]: Failed password for invalid user cl from 134.209.16.36 port 50734 ssh2
...
2019-12-15 20:07:30
165.227.26.69 attackbots
Dec 15 09:14:49 mail1 sshd\[31977\]: Invalid user mathildasu from 165.227.26.69 port 44910
Dec 15 09:14:49 mail1 sshd\[31977\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.227.26.69
Dec 15 09:14:51 mail1 sshd\[31977\]: Failed password for invalid user mathildasu from 165.227.26.69 port 44910 ssh2
Dec 15 09:25:59 mail1 sshd\[5231\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.227.26.69  user=dovenull
Dec 15 09:26:01 mail1 sshd\[5231\]: Failed password for dovenull from 165.227.26.69 port 53616 ssh2
...
2019-12-15 19:44:07
153.149.29.148 attackspam
Honeypot attack, port: 445, PTR: 153-149-29-148.compute.jp-e1.cloudn-service.com.
2019-12-15 19:51:28
119.203.59.159 attack
Dec 15 10:01:13 web8 sshd\[22085\]: Invalid user mysqldump from 119.203.59.159
Dec 15 10:01:13 web8 sshd\[22085\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.203.59.159
Dec 15 10:01:15 web8 sshd\[22085\]: Failed password for invalid user mysqldump from 119.203.59.159 port 41234 ssh2
Dec 15 10:07:42 web8 sshd\[25327\]: Invalid user menegon from 119.203.59.159
Dec 15 10:07:42 web8 sshd\[25327\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.203.59.159
2019-12-15 19:35:19
148.66.135.178 attackspam
Dec 15 04:44:31 ny01 sshd[15438]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.66.135.178
Dec 15 04:44:32 ny01 sshd[15438]: Failed password for invalid user mehrzad from 148.66.135.178 port 56148 ssh2
Dec 15 04:50:58 ny01 sshd[16047]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.66.135.178
2019-12-15 19:47:37
106.12.42.95 attackspam
SSH brutforce
2019-12-15 20:00:18
185.41.187.164 attackbotsspam
Portscan or hack attempt detected by psad/fwsnort
2019-12-15 19:42:43
81.4.123.26 attackspambots
Dec 14 22:47:10 server sshd\[30331\]: Failed password for invalid user niyana from 81.4.123.26 port 58430 ssh2
Dec 15 14:21:22 server sshd\[23767\]: Invalid user zhouh from 81.4.123.26
Dec 15 14:21:22 server sshd\[23767\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=81.4.123.26 
Dec 15 14:21:24 server sshd\[23767\]: Failed password for invalid user zhouh from 81.4.123.26 port 59370 ssh2
Dec 15 14:27:36 server sshd\[25554\]: Invalid user squid from 81.4.123.26
Dec 15 14:27:36 server sshd\[25554\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=81.4.123.26 
...
2019-12-15 19:49:18

Recently Reported IPs

139.180.142.201 139.180.142.143 139.180.142.215 139.180.142.163
139.180.142.243 139.180.142.235 139.180.141.77 139.180.142.250
118.233.52.2 139.180.142.252 139.180.142.40 139.180.142.58
139.180.142.70 139.180.143.218 139.180.143.160 139.180.143.214
139.180.143.206 139.180.143.115 139.180.143.245 139.180.143.161