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

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 <<>> 194.139.189.169
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 27303
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;194.139.189.169.		IN	A

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

;; Query time: 80 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Jan 31 14:46:18 CST 2020
;; MSG SIZE  rcvd: 119
Host info
Host 169.189.139.194.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 169.189.139.194.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
104.238.120.74 attack
Automatic report - XMLRPC Attack
2019-12-02 22:26:34
138.68.27.177 attackspam
Dec  2 21:11:45 webhost01 sshd[6450]: Failed password for news from 138.68.27.177 port 38772 ssh2
...
2019-12-02 22:24:29
123.206.174.26 attackspambots
Dec  2 14:17:34 venus sshd\[19252\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.206.174.26  user=lp
Dec  2 14:17:35 venus sshd\[19252\]: Failed password for lp from 123.206.174.26 port 38650 ssh2
Dec  2 14:27:07 venus sshd\[19479\]: Invalid user info from 123.206.174.26 port 48186
Dec  2 14:27:07 venus sshd\[19479\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.206.174.26
...
2019-12-02 22:41:46
124.156.172.11 attackspam
2019-12-02T15:27:11.481076centos sshd\[13536\]: Invalid user bouroncle from 124.156.172.11 port 56856
2019-12-02T15:27:11.486144centos sshd\[13536\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=124.156.172.11
2019-12-02T15:27:13.625189centos sshd\[13536\]: Failed password for invalid user bouroncle from 124.156.172.11 port 56856 ssh2
2019-12-02 22:44:31
167.172.24.169 attackbots
Dec  2 09:53:42 linuxvps sshd\[2360\]: Invalid user merdem from 167.172.24.169
Dec  2 09:53:42 linuxvps sshd\[2360\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.172.24.169
Dec  2 09:53:44 linuxvps sshd\[2360\]: Failed password for invalid user merdem from 167.172.24.169 port 52770 ssh2
Dec  2 09:59:29 linuxvps sshd\[5983\]: Invalid user ekrem from 167.172.24.169
Dec  2 09:59:29 linuxvps sshd\[5983\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.172.24.169
2019-12-02 23:05:57
101.207.113.73 attackbotsspam
Dec  2 15:46:08 mail sshd\[32286\]: Invalid user guest from 101.207.113.73
Dec  2 15:46:08 mail sshd\[32286\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.207.113.73
Dec  2 15:46:10 mail sshd\[32286\]: Failed password for invalid user guest from 101.207.113.73 port 51062 ssh2
...
2019-12-02 23:00:06
45.55.188.133 attackbots
fail2ban
2019-12-02 22:42:34
159.89.177.46 attackspam
$f2bV_matches_ltvn
2019-12-02 22:54:05
182.61.105.104 attackbotsspam
Dec  2 17:24:53 server sshd\[23762\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.105.104  user=root
Dec  2 17:24:55 server sshd\[23762\]: Failed password for root from 182.61.105.104 port 55104 ssh2
Dec  2 17:36:01 server sshd\[27108\]: Invalid user kaist from 182.61.105.104
Dec  2 17:36:01 server sshd\[27108\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.105.104 
Dec  2 17:36:03 server sshd\[27108\]: Failed password for invalid user kaist from 182.61.105.104 port 50422 ssh2
...
2019-12-02 22:38:06
1.53.159.234 attackspam
2019-12-02 07:36:14 H=(ns320877.ip-91-121-173.eu) [1.53.159.234]:61104 I=[192.147.25.65]:25 F= rejected RCPT : RBL: found in thrukfz5b56tq6xao6odgdyjrq.zen.dq.spamhaus.net (127.0.0.4, 127.0.0.10) (https://www.spamhaus.org/query/ip/1.53.159.234)
2019-12-02 07:36:15 H=(ns320877.ip-91-121-173.eu) [1.53.159.234]:61104 I=[192.147.25.65]:25 F= rejected RCPT : RBL: found in thrukfz5b56tq6xao6odgdyjrq.zen.dq.spamhaus.net (127.0.0.10, 127.0.0.4) (https://www.spamhaus.org/query/ip/1.53.159.234)
2019-12-02 07:36:15 H=(ns320877.ip-91-121-173.eu) [1.53.159.234]:61104 I=[192.147.25.65]:25 F= rejected RCPT : RBL: found in thrukfz5b56tq6xao6odgdyjrq.zen.dq.spamhaus.net (127.0.0.10, 127.0.0.4) (https://www.spamhaus.org/query/ip/1.53.159.234)
...
2019-12-02 22:57:10
71.6.233.47 attack
Automatic report - Port Scan Attack
2019-12-02 22:46:29
186.214.229.220 attackspam
Automatic report - Port Scan Attack
2019-12-02 22:51:20
39.99.34.179 attack
Looking for resource vulnerabilities
2019-12-02 22:30:24
94.250.249.198 attackbotsspam
Too many connections or unauthorized access detected from Arctic banned ip
2019-12-02 22:42:19
103.6.196.39 attack
Automatic report - XMLRPC Attack
2019-12-02 22:34:41

Recently Reported IPs

183.92.249.27 14.102.92.72 170.130.205.108 36.90.130.168
171.119.99.68 188.169.142.196 42.218.251.107 146.45.202.191
187.62.191.3 157.230.249.58 93.170.135.79 36.89.106.69
14.29.247.69 94.74.162.48 240.138.158.227 250.40.73.45
85.224.238.197 220.17.79.192 235.46.63.81 249.65.98.251