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

;; QUESTION SECTION:
;106.139.23.241.			IN	A

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

;; Query time: 22 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Nov 23 10:55:15 CST 2023
;; MSG SIZE  rcvd: 107
Host info
241.23.139.106.in-addr.arpa domain name pointer KD106139023241.au-net.ne.jp.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
241.23.139.106.in-addr.arpa	name = KD106139023241.au-net.ne.jp.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
89.205.5.98 attack
Request: "GET / HTTP/1.1"
2019-06-22 06:55:18
191.17.189.172 attack
Request: "GET / HTTP/1.1" Request: "GET / HTTP/1.1"
2019-06-22 06:45:30
188.166.229.205 attackspambots
Invalid user oper from 188.166.229.205 port 62341
2019-06-22 06:27:58
184.105.247.195 attack
Bad Request: "GET / HTTP/1.1"
2019-06-22 06:23:29
58.242.83.28 attackbots
Jun 22 00:41:08 core01 sshd\[29628\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.242.83.28  user=root
Jun 22 00:41:09 core01 sshd\[29628\]: Failed password for root from 58.242.83.28 port 57024 ssh2
...
2019-06-22 06:42:37
171.229.231.177 attack
37215/tcp
[2019-06-21]1pkt
2019-06-22 06:35:33
117.63.143.119 attackspambots
23/tcp
[2019-06-21]1pkt
2019-06-22 06:27:20
200.250.25.213 attackspam
Automatic report - SSH Brute-Force Attack
2019-06-22 06:42:00
81.22.45.251 attackspambots
21.06.2019 22:18:03 Connection to port 5916 blocked by firewall
2019-06-22 06:45:49
109.201.152.23 attackbotsspam
Bad Bot Request: "HEAD / HTTP/1.1" Agent: "Mozilla/5.0 (compatible; Uptimebot/1.0;  http://www.uptime.com/uptimebot)"
2019-06-22 06:21:24
101.64.24.109 attackspambots
Request: "POST /wp-login.php HTTP/1.1" Request: "POST /wp-login.php HTTP/1.1" Request: "POST /wp-login.php HTTP/1.1" Request: "POST /wp-login.php HTTP/1.1"
2019-06-22 06:30:20
142.44.211.229 attackbots
Jun 21 22:16:05 lnxweb61 sshd[19885]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.44.211.229
Jun 21 22:16:05 lnxweb61 sshd[19885]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.44.211.229
2019-06-22 06:26:51
46.209.216.233 attack
Jun 21 22:03:40 localhost sshd\[5264\]: Invalid user hu from 46.209.216.233 port 35724
Jun 21 22:03:40 localhost sshd\[5264\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.209.216.233
Jun 21 22:03:42 localhost sshd\[5264\]: Failed password for invalid user hu from 46.209.216.233 port 35724 ssh2
2019-06-22 06:49:01
180.248.14.16 attackbotsspam
Request: "GET / HTTP/1.1"
2019-06-22 06:33:28
45.79.7.213 attackspambots
Bad Bot Bad Request: "GET /api/v1 HTTP/1.1" Agent: "python-requests/2.21.0" Bad Bot Bad Request: "GET /api/v1 HTTP/1.1" Agent: "python-requests/2.21.0"
2019-06-22 06:13:46

Recently Reported IPs

106.139.141.239 106.139.126.17 106.139.49.118 106.139.132.231
106.139.139.127 106.139.121.181 106.139.177.211 106.138.81.240
106.139.122.97 106.138.66.166 106.138.64.199 106.139.238.120
106.138.53.48 106.139.217.96 106.138.92.11 106.139.188.8
106.139.136.103 106.139.178.181 106.138.35.25 106.138.77.166