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

Region: Tokyo

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

;; QUESTION SECTION:
;123.225.50.1.			IN	A

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

;; Query time: 32 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Mar 09 10:57:35 CST 2025
;; MSG SIZE  rcvd: 105
Host info
1.50.225.123.in-addr.arpa domain name pointer p7849002-ipoefx.ipoe.ocn.ne.jp.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
1.50.225.123.in-addr.arpa	name = p7849002-ipoefx.ipoe.ocn.ne.jp.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
185.176.27.178 attack
Sep 26 22:54:01 mc1 kernel: \[817679.475331\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=185.176.27.178 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=244 ID=13489 PROTO=TCP SPT=47456 DPT=7177 WINDOW=1024 RES=0x00 SYN URGP=0 
Sep 26 22:54:30 mc1 kernel: \[817707.945028\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=185.176.27.178 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=244 ID=39998 PROTO=TCP SPT=47456 DPT=5197 WINDOW=1024 RES=0x00 SYN URGP=0 
Sep 26 23:00:29 mc1 kernel: \[818066.626409\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=185.176.27.178 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=244 ID=44760 PROTO=TCP SPT=47456 DPT=5768 WINDOW=1024 RES=0x00 SYN URGP=0 
...
2019-09-27 05:20:17
123.207.16.33 attack
Sep 26 11:19:45 hiderm sshd\[30279\]: Invalid user fa from 123.207.16.33
Sep 26 11:19:45 hiderm sshd\[30279\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.207.16.33
Sep 26 11:19:47 hiderm sshd\[30279\]: Failed password for invalid user fa from 123.207.16.33 port 45496 ssh2
Sep 26 11:23:35 hiderm sshd\[30621\]: Invalid user admin from 123.207.16.33
Sep 26 11:23:35 hiderm sshd\[30621\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.207.16.33
2019-09-27 05:38:17
59.99.161.68 attack
Attempt to attack host OS, exploiting network vulnerabilities, on 26-09-2019 14:15:29.
2019-09-27 05:14:23
189.51.101.126 attackbotsspam
proto=tcp  .  spt=38005  .  dpt=25  .     (Listed on    dnsbl-sorbs plus abuseat-org and barracuda)     (362)
2019-09-27 05:08:51
157.245.106.178 attack
RDP Bruteforce
2019-09-27 05:24:58
189.46.3.9 attackbots
IP Ban Report : https://help-dysk.pl/wordpress-firewall-plugins/ip/189.46.3.9/ 
 BR - 1H : (770)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : BR 
 NAME ASN : ASN27699 
 
 IP : 189.46.3.9 
 
 CIDR : 189.46.0.0/16 
 
 PREFIX COUNT : 267 
 
 UNIQUE IP COUNT : 6569728 
 
 
 WYKRYTE ATAKI Z ASN27699 :  
  1H - 17 
  3H - 40 
  6H - 75 
 12H - 127 
 24H - 257 
 
 INFO : Port Scan TELNET Detected and Blocked by ADMIN  - data recovery
2019-09-27 05:31:25
45.82.153.42 attackbotsspam
09/26/2019-23:23:32.875042 45.82.153.42 Protocol: 6 ET CINS Active Threat Intelligence Poor Reputation IP group 44
2019-09-27 05:41:24
113.23.54.141 attackspam
Unauthorized connection attempt from IP address 113.23.54.141 on Port 445(SMB)
2019-09-27 05:09:18
93.189.101.5 attack
Sep 26 23:15:53 iago sshd[30600]: Invalid user admin from 93.189.101.5
Sep 26 23:15:53 iago sshd[30600]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=93.189.101.5 


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=93.189.101.5
2019-09-27 05:40:56
185.200.118.55 attackspam
" "
2019-09-27 05:29:13
18.207.218.200 attack
Sep 26 11:19:46 sachi sshd\[17086\]: Invalid user tester from 18.207.218.200
Sep 26 11:19:46 sachi sshd\[17086\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ec2-18-207-218-200.compute-1.amazonaws.com
Sep 26 11:19:48 sachi sshd\[17086\]: Failed password for invalid user tester from 18.207.218.200 port 43962 ssh2
Sep 26 11:23:28 sachi sshd\[17375\]: Invalid user opyu from 18.207.218.200
Sep 26 11:23:28 sachi sshd\[17375\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ec2-18-207-218-200.compute-1.amazonaws.com
2019-09-27 05:44:33
103.1.251.7 attackbotsspam
" "
2019-09-27 05:20:04
175.19.218.230 attackspambots
Unauthorised access (Sep 27) SRC=175.19.218.230 LEN=40 TTL=49 ID=50439 TCP DPT=8080 WINDOW=31753 SYN 
Unauthorised access (Sep 26) SRC=175.19.218.230 LEN=40 TTL=49 ID=55068 TCP DPT=8080 WINDOW=42292 SYN
2019-09-27 05:45:19
222.186.52.89 attackspam
2019-09-26T21:40:07.710014abusebot-8.cloudsearch.cf sshd\[3901\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.52.89  user=root
2019-09-27 05:43:37
218.92.0.208 attackbotsspam
Sep 26 22:05:58 eventyay sshd[19593]: Failed password for root from 218.92.0.208 port 37828 ssh2
Sep 26 22:06:38 eventyay sshd[19599]: Failed password for root from 218.92.0.208 port 17640 ssh2
...
2019-09-27 05:23:30

Recently Reported IPs

67.253.42.82 74.134.227.179 225.204.100.120 171.171.188.15
218.240.194.1 38.21.133.227 219.195.117.180 49.143.210.125
224.199.143.119 250.246.226.44 240.183.148.184 17.209.240.76
243.123.118.175 173.27.196.248 163.188.202.20 218.188.25.60
235.191.124.7 91.29.16.207 134.8.9.89 55.62.205.244