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.154.12 attack
[Mon Sep 28 13:39:51 2020] - DDoS Attack From IP: 139.162.154.12 Port: 54504
2020-09-29 06:47:46
139.162.154.12 attack
18246/tcp 5900/tcp 5222/tcp...
[2020-08-03/09-27]12pkt,12pt.(tcp)
2020-09-28 23:15:19
139.162.154.12 attackspam
18246/tcp 5900/tcp 5222/tcp...
[2020-08-03/09-27]12pkt,12pt.(tcp)
2020-09-28 15:19:21
139.162.152.16 attackbotsspam
20 attempts against mh_ha-misbehave-ban on ship
2020-09-14 00:39:14
139.162.152.16 attackspambots
20 attempts against mh_ha-misbehave-ban on ship
2020-09-13 16:27:42
139.162.152.16 attackspambots
22 attempts against mh-misbehave-ban on pluto
2020-09-02 02:07:37
139.162.155.176 attackspambots
Aug 22 04:39:00 localhost postfix/smtpd[1958767]: lost connection after CONNECT from 139.162.155.176.li.binaryedge.ninja[139.162.155.176]
Aug 22 04:39:00 localhost postfix/smtpd[1958769]: lost connection after CONNECT from 139.162.155.176.li.binaryedge.ninja[139.162.155.176]
Aug 22 04:39:01 localhost postfix/smtpd[1958767]: lost connection after CONNECT from 139.162.155.176.li.binaryedge.ninja[139.162.155.176]
Aug 22 04:39:01 localhost postfix/smtpd[1958769]: lost connection after CONNECT from 139.162.155.176.li.binaryedge.ninja[139.162.155.176]
Aug 22 04:39:04 localhost postfix/smtpd[1958767]: lost connection after CONNECT from 139.162.155.176.li.binaryedge.ninja[139.162.155.176]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=139.162.155.176
2020-08-27 15:55:20
139.162.154.12 attackbots
 TCP (SYN) 139.162.154.12:53206 -> port 27017, len 44
2020-08-07 05:11:49
139.162.152.36 attack
Port probing on unauthorized port 8888
2020-07-25 14:06:44
139.162.152.36 attack
SSH Server BruteForce Attack
2020-06-16 04:45:49
139.162.155.176 attackbotsspam
port scan and connect, tcp 9200 (elasticsearch)
2020-06-09 03:53:27
139.162.159.187 attackspam
firewall-block, port(s): 80/tcp
2020-03-27 04:56:54
139.162.158.125 attackspambots
trying to access non-authorized port
2020-03-09 01:21:11
139.162.153.48 attack
Unauthorized connection attempt detected from IP address 139.162.153.48 to port 135 [J]
2020-03-01 04:41:07
139.162.158.11 attackspam
Dec 14 23:17:10 hosting sshd[18174]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=li1425-11.members.linode.com  user=root
Dec 14 23:17:12 hosting sshd[18174]: Failed password for root from 139.162.158.11 port 51804 ssh2
...
2019-12-15 06:18:17
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 139.162.15.86
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 52959
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;139.162.15.86.			IN	A

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

;; Query time: 16 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 12:00:26 CST 2022
;; MSG SIZE  rcvd: 106
Host info
86.15.162.139.in-addr.arpa domain name pointer sgas1.armadaservers.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
86.15.162.139.in-addr.arpa	name = sgas1.armadaservers.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
91.126.201.245 attackbotsspam
Unauthorized connection attempt detected from IP address 91.126.201.245 to port 5555
2020-04-12 23:53:50
103.35.119.238 attack
Unauthorized connection attempt detected from IP address 103.35.119.238 to port 1433
2020-04-12 23:50:53
125.138.64.28 attackbotsspam
Unauthorized connection attempt detected from IP address 125.138.64.28 to port 81
2020-04-12 23:49:00
190.134.22.146 attack
Unauthorized connection attempt detected from IP address 190.134.22.146 to port 23
2020-04-12 23:38:36
218.154.181.253 attackbotsspam
Unauthorized connection attempt detected from IP address 218.154.181.253 to port 23
2020-04-13 00:12:43
100.2.131.143 attackbots
Unauthorized connection attempt detected from IP address 100.2.131.143 to port 81
2020-04-12 23:51:39
189.27.238.100 attackspambots
Unauthorized connection attempt detected from IP address 189.27.238.100 to port 23
2020-04-13 00:22:42
189.156.93.253 attack
Unauthorized connection attempt detected from IP address 189.156.93.253 to port 8089
2020-04-13 00:20:56
201.140.212.85 attackspam
Unauthorized connection attempt detected from IP address 201.140.212.85 to port 80
2020-04-13 00:15:54
5.54.228.73 attackspam
Unauthorized connection attempt detected from IP address 5.54.228.73 to port 23
2020-04-13 00:10:45
5.235.200.195 attack
Unauthorized connection attempt detected from IP address 5.235.200.195 to port 80
2020-04-13 00:09:59
84.0.135.126 attackspambots
Unauthorized connection attempt detected from IP address 84.0.135.126 to port 8080
2020-04-12 23:58:23
150.109.230.219 attackbots
Unauthorized connection attempt detected from IP address 150.109.230.219 to port 1091
2020-04-12 23:48:05
14.174.184.147 attack
This ip keep flooting my server with port 445, smal power of ddos 100 mbs
2020-04-13 00:22:22
201.170.135.88 attackspambots
Unauthorized connection attempt detected from IP address 201.170.135.88 to port 23
2020-04-13 00:14:50

Recently Reported IPs

139.162.146.87 139.162.152.62 139.162.150.204 139.162.151.243
139.162.153.238 139.162.155.120 139.162.154.66 139.162.157.119
139.162.153.107 139.162.16.131 139.162.16.176 139.162.158.162
139.162.16.21 139.162.16.83 139.162.16.216 139.162.16.163
139.162.160.224 139.162.163.163 139.162.161.44 139.162.163.23