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.40
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3294
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;139.180.142.40.			IN	A

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

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

Non-authoritative answer:
40.142.180.139.in-addr.arpa	name = 139.180.142.40.vultr.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
175.167.11.239 attackspam
Jun 23 01:10:40 mercury kernel: [UFW ALLOW] IN=eth0 OUT= MAC=f2:3c:91:bc:4d:f8:84:78:ac:5a:1a:41:08:00 SRC=175.167.11.239 DST=109.74.200.221 LEN=32 TOS=0x00 PREC=0x00 TTL=50 ID=0 DF PROTO=UDP SPT=123 DPT=123 LEN=12 
...
2019-06-23 15:04:29
203.198.185.113 attackspam
Jun 23 05:23:13 yabzik sshd[30348]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.198.185.113
Jun 23 05:23:15 yabzik sshd[30348]: Failed password for invalid user user from 203.198.185.113 port 44263 ssh2
Jun 23 05:24:54 yabzik sshd[30651]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.198.185.113
2019-06-23 15:44:20
180.76.108.110 attackbots
Jan 31 01:37:18 vtv3 sshd\[7347\]: Invalid user wildfly from 180.76.108.110 port 52660
Jan 31 01:37:18 vtv3 sshd\[7347\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.76.108.110
Jan 31 01:37:20 vtv3 sshd\[7347\]: Failed password for invalid user wildfly from 180.76.108.110 port 52660 ssh2
Jan 31 01:42:47 vtv3 sshd\[8832\]: Invalid user owen from 180.76.108.110 port 56910
Jan 31 01:42:47 vtv3 sshd\[8832\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.76.108.110
Apr 14 23:51:01 vtv3 sshd\[13724\]: Invalid user deploy. from 180.76.108.110 port 58514
Apr 14 23:51:01 vtv3 sshd\[13724\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.76.108.110
Apr 14 23:51:03 vtv3 sshd\[13724\]: Failed password for invalid user deploy. from 180.76.108.110 port 58514 ssh2
Apr 14 23:53:14 vtv3 sshd\[14584\]: Invalid user h3lpd3sk from 180.76.108.110 port 51648
Apr 14 23:53:14 vtv3 sshd\[
2019-06-23 15:45:22
82.119.111.122 attackbots
Automatic report - Web App Attack
2019-06-23 15:15:38
154.8.223.253 attackbots
Jun 23 00:05:34 ip-172-31-1-72 sshd\[29776\]: Invalid user steam from 154.8.223.253
Jun 23 00:05:34 ip-172-31-1-72 sshd\[29776\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=154.8.223.253
Jun 23 00:05:36 ip-172-31-1-72 sshd\[29776\]: Failed password for invalid user steam from 154.8.223.253 port 52646 ssh2
Jun 23 00:09:47 ip-172-31-1-72 sshd\[30000\]: Invalid user kuai from 154.8.223.253
Jun 23 00:09:47 ip-172-31-1-72 sshd\[30000\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=154.8.223.253
2019-06-23 15:50:29
212.200.167.152 attack
8080/tcp
[2019-06-22]1pkt
2019-06-23 15:19:10
218.37.227.7 attack
ports scanning
2019-06-23 15:36:20
196.1.99.12 attackbots
IP attempted unauthorised action
2019-06-23 15:42:51
205.204.85.29 attackbots
Jun 23 03:38:55 atlassian sshd[22674]: Invalid user helpdesk from 205.204.85.29 port 45888
Jun 23 03:38:56 atlassian sshd[22674]: Failed password for invalid user helpdesk from 205.204.85.29 port 45888 ssh2
Jun 23 03:38:55 atlassian sshd[22674]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=205.204.85.29
Jun 23 03:38:55 atlassian sshd[22674]: Invalid user helpdesk from 205.204.85.29 port 45888
Jun 23 03:38:56 atlassian sshd[22674]: Failed password for invalid user helpdesk from 205.204.85.29 port 45888 ssh2
2019-06-23 15:27:17
217.67.186.42 attack
Unauthorized connection attempt from IP address 217.67.186.42 on Port 445(SMB)
2019-06-23 14:56:14
107.170.237.222 attackspambots
firewall-block, port(s): 25/tcp
2019-06-23 15:36:36
42.230.35.169 attackspambots
5500/tcp
[2019-06-22]1pkt
2019-06-23 14:57:17
201.103.57.96 attackbotsspam
port scan and connect, tcp 80 (http)
2019-06-23 15:04:59
140.143.193.52 attackbots
Automatic report - Web App Attack
2019-06-23 15:11:09
5.188.62.5 attackspam
21/tcp...
[2019-04-26/06-22]41pkt,2pt.(tcp)
2019-06-23 15:35:14

Recently Reported IPs

139.180.142.252 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 139.180.143.20 139.180.143.37
118.233.57.44 139.180.143.89 139.180.144.126 139.180.144.122
139.180.143.39 139.180.144.102 139.180.144.157 139.180.144.188