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.118.185 attackspam
Auto Detect Rule!
proto TCP (SYN), 139.162.118.185:48116->gjan.info:22, len 40
2020-09-06 03:37:48
139.162.118.185 attack
[portscan] tcp/22 [SSH]
*(RWIN=65535)(09051147)
2020-09-05 19:16:50
139.162.118.185 attackbots
22/tcp 22/tcp 22/tcp...
[2020-05-19/07-20]73pkt,1pt.(tcp)
2020-07-20 19:48:41
139.162.118.251 attackbots
Jul 18 05:56:34 debian-2gb-nbg1-2 kernel: \[17303145.971912\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=139.162.118.251 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=241 ID=54321 PROTO=TCP SPT=57219 DPT=6379 WINDOW=65535 RES=0x00 SYN URGP=0
2020-07-18 12:10:02
139.162.118.185 attackspambots
 TCP (SYN) 139.162.118.185:55252 -> port 22, len 40
2020-07-11 04:44:40
139.162.118.251 attack
Port 6379 scan denied
2020-04-07 16:37:21
139.162.118.185 attackspam
Port 22 (SSH) access denied
2020-04-02 18:42:16
139.162.118.251 attackspam
firewall-block, port(s): 6379/tcp
2020-03-05 03:00:36
139.162.118.251 attack
unauthorized connection attempt
2020-02-26 20:05:58
139.162.118.251 attack
unauthorized connection attempt
2020-02-15 19:45:50
139.162.118.251 attack
6379/tcp 6379/tcp 6379/tcp...
[2019-12-11/2020-02-11]73pkt,1pt.(tcp)
2020-02-12 05:11:58
139.162.118.251 attack
firewall-block, port(s): 6379/tcp
2019-12-02 17:35:10
139.162.118.185 attackspam
MultiHost/MultiPort Probe, Scan, Hack -
2019-11-14 21:19:19
139.162.118.185 attackspam
Scanning random ports - tries to find possible vulnerable services
2019-09-09 08:38:35
139.162.118.185 attackbots
firewall-block, port(s): 22/tcp
2019-09-05 10:40:18
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 139.162.118.226
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 60181
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;139.162.118.226.		IN	A

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

;; Query time: 73 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 27 12:34:59 CST 2022
;; MSG SIZE  rcvd: 108
Host info
226.118.162.139.in-addr.arpa domain name pointer li1602-226.members.linode.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
226.118.162.139.in-addr.arpa	name = li1602-226.members.linode.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
212.90.191.162 attack
Unauthorized connection attempt from IP address 212.90.191.162 on Port 445(SMB)
2019-09-09 07:17:43
192.144.175.106 attackspambots
Sep  8 22:23:40 MK-Soft-VM6 sshd\[1779\]: Invalid user ubuntu from 192.144.175.106 port 59862
Sep  8 22:23:40 MK-Soft-VM6 sshd\[1779\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.144.175.106
Sep  8 22:23:42 MK-Soft-VM6 sshd\[1779\]: Failed password for invalid user ubuntu from 192.144.175.106 port 59862 ssh2
...
2019-09-09 07:01:14
183.134.65.22 attackspambots
$f2bV_matches
2019-09-09 06:58:50
49.159.21.154 attackbots
445/tcp 445/tcp 445/tcp...
[2019-07-14/09-08]8pkt,1pt.(tcp)
2019-09-09 07:21:08
118.24.19.178 attackspambots
Sep  9 01:07:01 vps01 sshd[7153]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.19.178
Sep  9 01:07:03 vps01 sshd[7153]: Failed password for invalid user 1qaz2wsx from 118.24.19.178 port 39542 ssh2
2019-09-09 07:08:09
217.61.20.173 attackbots
23/tcp 22/tcp...
[2019-08-25/09-08]145pkt,2pt.(tcp)
2019-09-09 06:50:13
186.88.130.123 attackspam
Unauthorized connection attempt from IP address 186.88.130.123 on Port 445(SMB)
2019-09-09 07:09:37
78.133.89.111 attack
2019-09-08T19:31:09.434409abusebot-3.cloudsearch.cf sshd\[8006\]: Invalid user admin from 78.133.89.111 port 65310
2019-09-09 06:48:15
14.247.178.89 attackspam
Unauthorized connection attempt from IP address 14.247.178.89 on Port 445(SMB)
2019-09-09 06:53:23
196.188.241.91 attackbots
Unauthorized connection attempt from IP address 196.188.241.91 on Port 445(SMB)
2019-09-09 07:07:14
79.60.107.11 attack
Unauthorized connection attempt from IP address 79.60.107.11 on Port 445(SMB)
2019-09-09 06:59:37
159.203.199.101 attackspam
SASL Brute Force
2019-09-09 06:56:58
89.151.178.9 attack
Unauthorized connection attempt from IP address 89.151.178.9 on Port 445(SMB)
2019-09-09 07:01:49
46.105.244.1 attack
Sep  8 18:30:53 TORMINT sshd\[15226\]: Invalid user postgres from 46.105.244.1
Sep  8 18:30:53 TORMINT sshd\[15226\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.105.244.1
Sep  8 18:30:55 TORMINT sshd\[15226\]: Failed password for invalid user postgres from 46.105.244.1 port 60803 ssh2
...
2019-09-09 06:52:59
198.143.155.141 attackspambots
444/tcp 123/udp 1723/tcp...
[2019-07-17/09-07]8pkt,6pt.(tcp),2pt.(udp)
2019-09-09 06:41:12

Recently Reported IPs

139.162.119.186 139.162.123.106 139.162.120.23 139.162.121.138
139.162.123.231 139.162.119.252 139.162.128.243 139.162.13.242
139.162.13.36 139.162.130.137 139.162.123.96 139.162.121.86
139.162.130.140 139.155.48.15 139.162.132.11 139.162.131.15
139.162.108.45 139.162.132.65 139.162.130.216 139.162.132.205