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

;; QUESTION SECTION:
;122.250.2.239.			IN	A

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

;; Query time: 10 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jan 22 17:30:32 CST 2025
;; MSG SIZE  rcvd: 106
Host info
239.2.250.122.in-addr.arpa domain name pointer cwnet002239.c-able.ne.jp.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
239.2.250.122.in-addr.arpa	name = cwnet002239.c-able.ne.jp.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
46.149.191.201 attackspambots
Port 1433 Scan
2019-11-13 18:13:10
113.181.161.222 attackspam
MultiHost/MultiPort Probe, Scan, Hack -
2019-11-13 18:02:59
37.0.147.152 attackbots
TCP Port Scanning
2019-11-13 18:19:04
182.61.33.47 attack
2019-11-13T10:06:06.954268abusebot-5.cloudsearch.cf sshd\[23957\]: Invalid user pn from 182.61.33.47 port 53048
2019-11-13 18:08:19
187.205.215.122 attack
Automatic report - Port Scan Attack
2019-11-13 17:51:26
157.230.109.166 attackspambots
2019-11-13T07:25:49.756086abusebot-8.cloudsearch.cf sshd\[2691\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.230.109.166  user=root
2019-11-13 18:10:11
106.12.46.104 attack
SSHScan
2019-11-13 18:09:23
5.45.6.66 attackspam
Nov 13 10:21:06 ns382633 sshd\[17223\]: Invalid user bonza from 5.45.6.66 port 57176
Nov 13 10:21:06 ns382633 sshd\[17223\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.45.6.66
Nov 13 10:21:09 ns382633 sshd\[17223\]: Failed password for invalid user bonza from 5.45.6.66 port 57176 ssh2
Nov 13 10:40:15 ns382633 sshd\[20952\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.45.6.66  user=root
Nov 13 10:40:17 ns382633 sshd\[20952\]: Failed password for root from 5.45.6.66 port 60176 ssh2
2019-11-13 17:56:13
178.242.57.235 attackspam
" "
2019-11-13 18:21:55
182.61.110.113 attack
Nov 13 08:39:17 icinga sshd[11809]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.110.113 
Nov 13 08:39:19 icinga sshd[11809]: Failed password for invalid user dylan from 182.61.110.113 port 57698 ssh2
Nov 13 08:46:30 icinga sshd[18860]: Failed password for root from 182.61.110.113 port 57325 ssh2
...
2019-11-13 17:52:52
200.60.60.84 attack
2019-11-13T09:38:26.761577abusebot-5.cloudsearch.cf sshd\[23778\]: Invalid user chelsy from 200.60.60.84 port 37497
2019-11-13 18:06:13
59.25.197.158 attackspam
2019-11-13T06:25:28.758540abusebot-5.cloudsearch.cf sshd\[22589\]: Invalid user robert from 59.25.197.158 port 38372
2019-11-13 17:54:41
54.37.139.235 attack
Too many connections or unauthorized access detected from Arctic banned ip
2019-11-13 18:16:07
186.133.187.59 attack
TCP Port Scanning
2019-11-13 18:12:12
110.105.179.0 attack
MultiHost/MultiPort Probe, Scan, Hack -
2019-11-13 18:05:55

Recently Reported IPs

243.69.27.159 85.114.27.127 43.60.88.169 230.187.39.216
240.65.142.189 81.251.233.115 55.252.203.183 46.84.211.32
141.125.213.123 166.82.206.238 8.88.52.45 116.226.53.244
226.39.217.94 5.231.20.55 242.216.30.216 131.101.187.104
63.113.62.84 100.36.163.80 71.116.143.96 87.26.177.104