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

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.162.108.129 attackbots
Icarus honeypot on github
2020-09-01 07:48:04
139.162.108.62 attack
Port scan denied
2020-08-31 18:04:19
139.162.108.129 attackbotsspam
Tried our host z.
2020-08-29 08:30:25
139.162.108.53 attackspam
firewall-block, port(s): 80/tcp
2020-08-20 01:45:23
139.162.108.129 attackbotsspam
Icarus honeypot on github
2020-07-24 17:09:30
139.162.108.62 attack
Port scan denied
2020-07-14 01:12:17
139.162.108.129 attackbots
TCP port 3389: Scan and connection
2020-07-13 15:37:12
139.162.108.129 attackbots
Automatic report - Banned IP Access
2020-07-09 15:52:20
139.162.108.62 attackspam
Jul  5 05:52:16 debian-2gb-nbg1-2 kernel: \[16179752.059756\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=139.162.108.62 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=241 ID=54321 PROTO=TCP SPT=43236 DPT=8089 WINDOW=65535 RES=0x00 SYN URGP=0
2020-07-05 16:16:02
139.162.108.129 attackspam
TCP port 3389: Scan and connection
2020-06-26 14:33:42
139.162.108.129 attack
Unauthorized connection attempt detected from IP address 139.162.108.129 to port 3306 [T]
2020-06-24 01:49:19
139.162.108.129 attackbots
TCP port 3306: Scan and connection
2020-06-15 13:56:48
139.162.108.129 attack
Automatic report - Banned IP Access
2020-05-06 08:48:20
139.162.108.62 attackbotsspam
Fail2Ban Ban Triggered
2020-04-21 05:50:36
139.162.108.62 attackspambots
Hits on port : 8089
2020-04-05 08:27:10
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 139.162.108.45
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 41034
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;139.162.108.45.			IN	A

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

;; Query time: 20 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 27 12:35:13 CST 2022
;; MSG SIZE  rcvd: 107
Host info
45.108.162.139.in-addr.arpa domain name pointer li1592-45.members.linode.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
45.108.162.139.in-addr.arpa	name = li1592-45.members.linode.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
191.255.17.115 attack
20/2/15@08:53:34: FAIL: Alarm-Network address from=191.255.17.115
...
2020-02-15 22:53:19
125.25.213.21 attack
1581774822 - 02/15/2020 14:53:42 Host: 125.25.213.21/125.25.213.21 Port: 23 TCP Blocked
2020-02-15 22:42:38
212.251.232.194 attackbotsspam
Jan  7 10:21:35 ms-srv sshd[27185]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.251.232.194
Jan  7 10:21:37 ms-srv sshd[27185]: Failed password for invalid user ftpuser from 212.251.232.194 port 58426 ssh2
2020-02-15 22:37:36
212.237.3.8 attack
Dec 26 14:40:49 ms-srv sshd[39407]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.237.3.8
Dec 26 14:40:51 ms-srv sshd[39407]: Failed password for invalid user admin from 212.237.3.8 port 36820 ssh2
2020-02-15 22:46:08
168.232.130.173 attack
Feb 15 03:53:14 web9 sshd\[18802\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.232.130.173  user=root
Feb 15 03:53:16 web9 sshd\[18802\]: Failed password for root from 168.232.130.173 port 48851 ssh2
Feb 15 03:53:18 web9 sshd\[18802\]: Failed password for root from 168.232.130.173 port 48851 ssh2
Feb 15 03:53:28 web9 sshd\[18802\]: Failed password for root from 168.232.130.173 port 48851 ssh2
Feb 15 03:53:37 web9 sshd\[18866\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.232.130.173  user=root
2020-02-15 22:46:28
58.27.99.112 attackbotsspam
Feb 15 15:13:37 sso sshd[28231]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.27.99.112
Feb 15 15:13:39 sso sshd[28231]: Failed password for invalid user bryan from 58.27.99.112 port 45430 ssh2
...
2020-02-15 22:54:05
182.16.110.190 attackbotsspam
Feb 15 15:40:09 silence02 sshd[11132]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.16.110.190
Feb 15 15:40:11 silence02 sshd[11132]: Failed password for invalid user hadoop from 182.16.110.190 port 39216 ssh2
Feb 15 15:43:34 silence02 sshd[11286]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.16.110.190
2020-02-15 22:44:58
158.51.124.251 attackspam
158.51.124.251 has been banned for [spam]
...
2020-02-15 23:30:14
212.224.126.116 attackspam
Jan 28 16:46:54 ms-srv sshd[31201]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.224.126.116
Jan 28 16:46:56 ms-srv sshd[31201]: Failed password for invalid user usuario from 212.224.126.116 port 53420 ssh2
2020-02-15 23:01:02
212.237.54.236 attackspambots
Nov  7 04:42:34 ms-srv sshd[9915]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.237.54.236
Nov  7 04:42:37 ms-srv sshd[9915]: Failed password for invalid user pw from 212.237.54.236 port 52562 ssh2
2020-02-15 22:43:26
217.182.74.125 attackspambots
Feb 15 05:10:51 auw2 sshd\[25409\]: Invalid user cstrike from 217.182.74.125
Feb 15 05:10:51 auw2 sshd\[25409\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.ip-217-182-74.eu
Feb 15 05:10:52 auw2 sshd\[25409\]: Failed password for invalid user cstrike from 217.182.74.125 port 51900 ssh2
Feb 15 05:13:59 auw2 sshd\[25664\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.ip-217-182-74.eu  user=root
Feb 15 05:14:01 auw2 sshd\[25664\]: Failed password for root from 217.182.74.125 port 53346 ssh2
2020-02-15 23:16:04
134.236.160.231 attack
DATE:2020-02-15 14:53:14, IP:134.236.160.231, PORT:telnet Telnet brute force auth on honeypot server (honey-neo-dc)
2020-02-15 23:20:11
50.236.62.30 attackbots
Feb 15 15:26:36 srv-ubuntu-dev3 sshd[121318]: Invalid user hadoop from 50.236.62.30
Feb 15 15:26:36 srv-ubuntu-dev3 sshd[121318]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=50.236.62.30
Feb 15 15:26:36 srv-ubuntu-dev3 sshd[121318]: Invalid user hadoop from 50.236.62.30
Feb 15 15:26:38 srv-ubuntu-dev3 sshd[121318]: Failed password for invalid user hadoop from 50.236.62.30 port 48938 ssh2
Feb 15 15:29:54 srv-ubuntu-dev3 sshd[121586]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=50.236.62.30  user=root
Feb 15 15:29:56 srv-ubuntu-dev3 sshd[121586]: Failed password for root from 50.236.62.30 port 35518 ssh2
Feb 15 15:33:18 srv-ubuntu-dev3 sshd[121854]: Invalid user andy from 50.236.62.30
Feb 15 15:33:18 srv-ubuntu-dev3 sshd[121854]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=50.236.62.30
Feb 15 15:33:18 srv-ubuntu-dev3 sshd[121854]: Invalid user andy from 50.2
...
2020-02-15 22:35:50
212.164.191.142 attack
Sep  7 15:06:23 ms-srv sshd[6556]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.164.191.142
Sep  7 15:06:26 ms-srv sshd[6556]: Failed password for invalid user admin from 212.164.191.142 port 34999 ssh2
2020-02-15 23:27:00
77.40.3.64 attackspam
failed_logins
2020-02-15 22:56:39

Recently Reported IPs

139.162.131.15 139.162.132.65 139.162.130.216 139.162.132.205
139.162.138.205 139.162.135.83 139.162.133.189 139.162.135.213
139.162.139.243 139.162.140.121 139.162.141.152 139.162.141.251
139.162.142.26 139.162.142.232 139.129.209.222 139.129.209.6
139.129.212.119 139.129.201.149 139.129.210.131 139.129.226.52