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

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

;; QUESTION SECTION:
;106.39.150.139.			IN	A

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

;; Query time: 60 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 07 12:36:14 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 139.150.39.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.150.39.106.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
218.92.0.148 attackbots
Feb 17 05:59:43 vps647732 sshd[12999]: Failed password for root from 218.92.0.148 port 31014 ssh2
Feb 17 05:59:55 vps647732 sshd[12999]: error: maximum authentication attempts exceeded for root from 218.92.0.148 port 31014 ssh2 [preauth]
...
2020-02-17 13:00:11
222.186.173.180 attackspam
Fail2Ban Ban Triggered (2)
2020-02-17 13:09:29
159.89.165.99 attack
Feb 16 22:23:19 thevastnessof sshd[9042]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.165.99
...
2020-02-17 10:44:18
112.85.42.227 attackbotsspam
Feb 16 21:14:36 NPSTNNYC01T sshd[9179]: Failed password for root from 112.85.42.227 port 46349 ssh2
Feb 16 21:18:10 NPSTNNYC01T sshd[9256]: Failed password for root from 112.85.42.227 port 49457 ssh2
...
2020-02-17 10:28:03
67.229.93.31 attackspambots
67.229.93.31 was recorded 5 times by 4 hosts attempting to connect to the following ports: 11211. Incident counter (4h, 24h, all-time): 5, 18, 126
2020-02-17 10:30:56
58.250.27.18 attack
02/16/2020-23:23:34.723952 58.250.27.18 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2020-02-17 10:33:40
185.232.67.6 attackspambots
Feb 17 03:05:54 dedicated sshd[6790]: Invalid user admin from 185.232.67.6 port 57534
2020-02-17 10:43:12
201.237.63.253 attackbotsspam
Unauthorized connection attempt detected from IP address 201.237.63.253 to port 445
2020-02-17 13:17:58
138.68.234.162 attack
Feb 17 01:17:19 server sshd\[1678\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.234.162  user=root
Feb 17 01:17:21 server sshd\[1678\]: Failed password for root from 138.68.234.162 port 35718 ssh2
Feb 17 01:23:30 server sshd\[2820\]: Invalid user wch from 138.68.234.162
Feb 17 01:23:30 server sshd\[2820\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.234.162 
Feb 17 01:23:32 server sshd\[2820\]: Failed password for invalid user wch from 138.68.234.162 port 46056 ssh2
...
2020-02-17 10:34:51
211.20.188.210 attackbots
SSH login attempts.
2020-02-17 13:17:30
45.143.221.37 attack
02/16/2020-23:59:51.760888 45.143.221.37 Protocol: 17 ET SCAN Sipvicious Scan
2020-02-17 13:05:45
180.76.247.6 attackspambots
$f2bV_matches
2020-02-17 10:47:01
103.89.91.253 attackbots
Multiple SSH login attempts.
2020-02-17 10:47:33
195.158.30.215 attackbotsspam
$f2bV_matches
2020-02-17 13:09:59
123.58.177.49 attackbotsspam
SSH login attempts.
2020-02-17 13:10:54

Recently Reported IPs

213.170.247.184 115.242.248.226 45.126.21.75 202.152.33.130
62.85.21.77 187.178.167.177 174.61.96.86 161.132.238.218
187.110.244.248 191.240.114.132 115.97.140.14 175.193.97.249
73.62.115.186 198.199.75.14 197.61.30.199 62.122.96.35
193.164.16.175 200.194.5.226 75.85.188.228 187.188.172.117