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:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 139.162.135.213
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 14203
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;139.162.135.213.		IN	A

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

;; Query time: 62 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 27 12:35:15 CST 2022
;; MSG SIZE  rcvd: 108
Host info
213.135.162.139.in-addr.arpa domain name pointer oma.savviihq.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
213.135.162.139.in-addr.arpa	name = oma.savviihq.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
222.124.18.155 attack
suspicious action Sat, 22 Feb 2020 10:11:09 -0300
2020-02-22 21:12:47
145.239.82.11 attackbots
Feb 22 14:13:58 tuxlinux sshd[17063]: Invalid user q3 from 145.239.82.11 port 40266
Feb 22 14:13:58 tuxlinux sshd[17063]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=145.239.82.11 
Feb 22 14:13:58 tuxlinux sshd[17063]: Invalid user q3 from 145.239.82.11 port 40266
Feb 22 14:13:58 tuxlinux sshd[17063]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=145.239.82.11 
Feb 22 14:13:58 tuxlinux sshd[17063]: Invalid user q3 from 145.239.82.11 port 40266
Feb 22 14:13:58 tuxlinux sshd[17063]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=145.239.82.11 
Feb 22 14:13:59 tuxlinux sshd[17063]: Failed password for invalid user q3 from 145.239.82.11 port 40266 ssh2
...
2020-02-22 21:27:52
54.37.156.188 attack
Feb 22 10:33:43 host sshd[39787]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.ip-54-37-156.eu  user=root
Feb 22 10:33:45 host sshd[39787]: Failed password for root from 54.37.156.188 port 41930 ssh2
...
2020-02-22 21:01:34
198.108.67.90 attack
ET DROP Dshield Block Listed Source group 1 - port: 9236 proto: TCP cat: Misc Attack
2020-02-22 21:14:01
163.172.158.205 attack
2020-02-22T06:14:03.380727-07:00 suse-nuc sshd[20447]: Invalid user sito from 163.172.158.205 port 38646
...
2020-02-22 21:25:51
198.108.67.81 attackbotsspam
ET DROP Dshield Block Listed Source group 1 - port: 20001 proto: TCP cat: Misc Attack
2020-02-22 21:15:04
212.95.137.151 attackspambots
1582377235 - 02/22/2020 14:13:55 Host: 212.95.137.151/212.95.137.151 Port: 22 TCP Blocked
2020-02-22 21:30:46
201.41.148.228 attackbotsspam
Feb 22 13:27:30 server sshd\[2686\]: Invalid user guest from 201.41.148.228
Feb 22 13:27:30 server sshd\[2686\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.41.148.228 
Feb 22 13:27:32 server sshd\[2686\]: Failed password for invalid user guest from 201.41.148.228 port 55440 ssh2
Feb 22 13:41:23 server sshd\[5111\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.41.148.228  user=root
Feb 22 13:41:25 server sshd\[5111\]: Failed password for root from 201.41.148.228 port 35045 ssh2
...
2020-02-22 21:03:45
163.172.178.153 attackspambots
SSH Brute Force
2020-02-22 21:05:40
222.186.175.23 attack
Feb 22 14:20:02 MK-Soft-Root1 sshd[7718]: Failed password for root from 222.186.175.23 port 25768 ssh2
Feb 22 14:20:04 MK-Soft-Root1 sshd[7718]: Failed password for root from 222.186.175.23 port 25768 ssh2
...
2020-02-22 21:21:16
31.165.88.36 attack
SSH Brute Force
2020-02-22 21:12:20
5.135.94.191 attack
3x Failed Password
2020-02-22 21:20:22
198.108.67.60 attackbotsspam
Port 8002 scan denied
2020-02-22 21:15:32
198.108.67.91 attack
Port 20184 scan denied
2020-02-22 21:13:39
185.176.27.102 attack
scans 5 times in preceeding hours on the ports (in chronological order) 17099 17098 17099 17194 17192 resulting in total of 39 scans from 185.176.27.0/24 block.
2020-02-22 21:17:43

Recently Reported IPs

139.162.133.189 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 139.129.229.166 139.129.191.23 139.129.212.199
139.129.193.94 139.129.220.253 139.129.231.5 139.129.216.254