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

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

;; QUESTION SECTION:
;106.188.194.139.		IN	A

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

;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Jan 24 13:05:17 CST 2025
;; MSG SIZE  rcvd: 108
Host info
Host 139.194.188.106.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 139.194.188.106.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
122.242.155.219 attack
Telnet Server BruteForce Attack
2019-07-31 02:48:48
111.231.133.173 attackbots
Jul 30 18:36:07 ubuntu-2gb-nbg1-dc3-1 sshd[32170]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.231.133.173
Jul 30 18:36:09 ubuntu-2gb-nbg1-dc3-1 sshd[32170]: Failed password for invalid user liang from 111.231.133.173 port 38600 ssh2
...
2019-07-31 02:29:00
139.59.180.53 attackspam
2019-07-30T17:51:36.067839stark.klein-stark.info sshd\[22737\]: Invalid user ubuntu from 139.59.180.53 port 53306
2019-07-30T17:51:36.072480stark.klein-stark.info sshd\[22737\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.180.53
2019-07-30T17:51:37.978791stark.klein-stark.info sshd\[22737\]: Failed password for invalid user ubuntu from 139.59.180.53 port 53306 ssh2
...
2019-07-31 02:40:37
122.54.111.227 attackspambots
8291/tcp
[2019-07-30]1pkt
2019-07-31 02:45:28
34.76.76.224 attack
firewall-block, port(s): 8888/tcp
2019-07-31 02:18:01
180.125.174.221 attackbotsspam
52869/tcp
[2019-07-30]1pkt
2019-07-31 03:02:26
112.85.42.72 attackbots
SSH invalid-user multiple login attempts
2019-07-31 02:40:59
104.155.52.215 attackspam
5900/tcp
[2019-07-30]1pkt
2019-07-31 02:28:03
14.234.164.152 attackbotsspam
445/tcp
[2019-07-30]1pkt
2019-07-31 02:40:16
46.166.190.146 attack
¯\_(ツ)_/¯
2019-07-31 03:08:43
61.162.188.254 attack
1433/tcp 1433/tcp
[2019-07-30]2pkt
2019-07-31 02:35:30
45.119.153.29 attackspambots
Jul 30 14:16:28 tux-35-217 sshd\[29802\]: Invalid user netscreen from 45.119.153.29 port 51634
Jul 30 14:16:29 tux-35-217 sshd\[29802\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.119.153.29
Jul 30 14:16:31 tux-35-217 sshd\[29802\]: Failed password for invalid user netscreen from 45.119.153.29 port 51634 ssh2
Jul 30 14:16:36 tux-35-217 sshd\[29804\]: Invalid user misp from 45.119.153.29 port 52005
Jul 30 14:16:37 tux-35-217 sshd\[29804\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.119.153.29
...
2019-07-31 02:49:15
86.99.119.138 attack
Bot ignores robot.txt restrictions
2019-07-31 03:08:09
85.209.0.115 attack
Port scan on 18 port(s): 10737 15300 17954 19323 21802 22523 23175 28469 28759 33733 33791 35717 37836 38095 39299 53596 56026 58342
2019-07-31 02:19:24
106.52.25.204 attackbots
DATE:2019-07-30 17:56:23, IP:106.52.25.204, PORT:ssh SSH brute force auth (thor)
2019-07-31 03:09:39

Recently Reported IPs

139.149.93.227 100.228.215.206 14.199.210.80 85.68.79.75
96.3.241.38 65.112.188.71 238.215.152.147 214.136.8.35
205.217.147.115 93.248.78.99 43.112.102.55 34.232.237.138
153.3.190.99 231.11.240.12 56.82.129.65 91.231.52.106
140.65.102.244 230.126.132.38 212.205.232.148 49.58.255.220