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.212.134 attackbotsspam
Automatic report - XMLRPC Attack
2020-04-05 12:52:56
139.180.212.134 attack
srv.marc-hoffrichter.de:80 139.180.212.134 - - [20/Feb/2020:05:54:08 +0100] "CONNECT 64.62.216.151:80 HTTP/1.0" 301 635 "-" "-"
2020-02-20 16:06:02
139.180.212.134 attack
Feb  7 23:39:03 debian-2gb-nbg1-2 kernel: \[3374384.412374\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=139.180.212.134 DST=195.201.40.59 LEN=52 TOS=0x00 PREC=0x00 TTL=116 ID=17460 DF PROTO=TCP SPT=55734 DPT=35 WINDOW=8192 RES=0x00 SYN URGP=0
2020-02-08 07:42:26
139.180.212.134 attackbotsspam
2020-01-18 01:08:58 SMTP protocol synchronization error \(input sent without waiting for greeting\): rejected connection from H=\[139.180.212.134\]:50978 I=\[193.107.88.166\]:25 input="CONNECT 104.25.136.22:80 HTTP/1."
2020-01-18 01:08:58 SMTP protocol synchronization error \(input sent without waiting for greeting\): rejected connection from H=\[139.180.212.134\]:50987 I=\[193.107.88.166\]:25 input="\004\001"
2020-01-18 01:08:58 SMTP protocol synchronization error \(input sent without waiting for greeting\): rejected connection from H=\[139.180.212.134\]:50994 I=\[193.107.88.166\]:25 input="\005\001"
2020-01-18 01:08:59 SMTP protocol synchronization error \(input sent without waiting for greeting\): rejected connection from H=\[139.180.212.134\]:50998 I=\[193.107.88.166\]:25 input="GET http://www.stopforumspam.com"
2020-01-18 01:08:59 SMTP protocol synchronization error \(input sent without waiting for greeting\): rejected connection from H=\[139.180.212.134\]:51009 I=\[193.107.88.166
...
2020-02-05 01:08:40
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 139.180.212.113
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 7069
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;139.180.212.113.		IN	A

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

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

Non-authoritative answer:
113.212.180.139.in-addr.arpa	name = 139.180.212.113.vultr.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
186.209.74.197 attack
May 29 10:32:28 sso sshd[18340]: Failed password for root from 186.209.74.197 port 34361 ssh2
May 29 10:57:23 sso sshd[21159]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.209.74.197
...
2020-05-29 18:01:36
95.216.76.116 attack
Attempts to probe web pages for vulnerable PHP or other applications
2020-05-29 18:04:48
106.13.233.5 attackspam
SSH Brute Force
2020-05-29 17:36:38
140.143.200.251 attackbotsspam
$f2bV_matches
2020-05-29 17:32:37
197.160.27.237 attack
Automatic report - XMLRPC Attack
2020-05-29 17:49:49
50.244.37.249 attackspambots
May 29 11:11:13 PorscheCustomer sshd[15195]: Failed password for root from 50.244.37.249 port 37802 ssh2
May 29 11:15:28 PorscheCustomer sshd[15283]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=50.244.37.249
May 29 11:15:30 PorscheCustomer sshd[15283]: Failed password for invalid user deanngaliq from 50.244.37.249 port 43598 ssh2
...
2020-05-29 17:28:44
185.176.27.42 attackspam
May 29 11:02:38 debian-2gb-nbg1-2 kernel: \[13001744.183915\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=185.176.27.42 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=48733 PROTO=TCP SPT=45548 DPT=8668 WINDOW=1024 RES=0x00 SYN URGP=0
2020-05-29 17:34:27
157.245.218.105 attackspam
Port scanning [2 denied]
2020-05-29 17:39:17
27.72.146.202 attack
20/5/28@23:49:51: FAIL: Alarm-Network address from=27.72.146.202
...
2020-05-29 17:57:09
188.11.67.165 attackspam
May 29 07:48:34 localhost sshd\[32341\]: Invalid user bbb from 188.11.67.165
May 29 07:48:34 localhost sshd\[32341\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.11.67.165
May 29 07:48:36 localhost sshd\[32341\]: Failed password for invalid user bbb from 188.11.67.165 port 44448 ssh2
May 29 07:55:09 localhost sshd\[368\]: Invalid user hadoop from 188.11.67.165
May 29 07:55:09 localhost sshd\[368\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.11.67.165
...
2020-05-29 17:51:37
52.170.90.207 attackbotsspam
spam
2020-05-29 17:58:03
185.102.219.19 attackspam
Fail2Ban Ban Triggered
HTTP Attempted Bot Registration
2020-05-29 17:57:33
185.220.101.193 attackspambots
May 29 04:48:10 r.ca sshd[9552]: Failed password for root from 185.220.101.193 port 8744 ssh2
2020-05-29 17:37:04
83.97.20.232 attack
" "
2020-05-29 17:45:07
195.128.96.92 attackspam
20/5/29@01:34:54: FAIL: Alarm-Network address from=195.128.96.92
20/5/29@01:34:55: FAIL: Alarm-Network address from=195.128.96.92
...
2020-05-29 17:32:19

Recently Reported IPs

139.180.211.67 139.180.212.13 139.180.212.133 139.180.212.208
139.180.212.249 139.180.212.215 139.180.212.235 139.180.212.253
139.180.212.34 139.180.212.76 139.180.212.52 139.180.213.137
139.180.212.87 118.238.6.59 139.180.213.165 139.180.213.176
139.180.213.18 139.180.213.210 139.180.213.208 139.180.213.177