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

;; QUESTION SECTION:
;119.138.225.45.			IN	A

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

;; Query time: 21 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 12:04:45 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 45.225.138.119.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 45.225.138.119.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
14.48.55.239 attack
Unauthorized connection attempt detected from IP address 14.48.55.239 to port 23
2020-04-13 01:31:01
12.188.20.242 attack
Unauthorized connection attempt detected from IP address 12.188.20.242 to port 8089
2020-04-13 01:32:13
1.251.0.135 attackbotsspam
Apr 12 18:19:14 ovpn sshd\[31265\]: Invalid user pi from 1.251.0.135
Apr 12 18:19:14 ovpn sshd\[31264\]: Invalid user pi from 1.251.0.135
Apr 12 18:19:15 ovpn sshd\[31264\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.251.0.135
Apr 12 18:19:15 ovpn sshd\[31265\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.251.0.135
Apr 12 18:19:17 ovpn sshd\[31264\]: Failed password for invalid user pi from 1.251.0.135 port 45327 ssh2
Apr 12 18:19:17 ovpn sshd\[31265\]: Failed password for invalid user pi from 1.251.0.135 port 19951 ssh2
2020-04-13 01:33:47
59.24.189.168 attackspam
Unauthorized connection attempt detected from IP address 59.24.189.168 to port 23
2020-04-13 01:24:13
2.143.208.190 attackbots
Unauthorized connection attempt detected from IP address 2.143.208.190 to port 23
2020-04-13 01:33:27
45.238.208.3 attackspam
Unauthorized connection attempt detected from IP address 45.238.208.3 to port 23
2020-04-13 01:26:21
162.243.130.171 attackspam
Unauthorized connection attempt detected from IP address 162.243.130.171 to port 9042
2020-04-13 01:51:22
121.161.99.72 attackbotsspam
Unauthorized connection attempt detected from IP address 121.161.99.72 to port 23
2020-04-13 01:10:58
183.109.34.41 attack
Unauthorized connection attempt detected from IP address 183.109.34.41 to port 23
2020-04-13 01:45:39
162.210.42.30 attackbots
Unauthorized connection attempt detected from IP address 162.210.42.30 to port 23
2020-04-13 01:51:52
95.244.222.32 attackbots
Unauthorized connection attempt detected from IP address 95.244.222.32 to port 26
2020-04-13 01:15:32
80.17.57.197 attack
Unauthorized connection attempt detected from IP address 80.17.57.197 to port 23
2020-04-13 01:21:08
87.197.156.95 attack
Unauthorized connection attempt detected from IP address 87.197.156.95 to port 23
2020-04-13 01:18:06
95.85.182.246 attack
Unauthorized connection attempt detected from IP address 95.85.182.246 to port 23
2020-04-13 01:16:07
187.17.175.241 attackbots
Automatic report - Port Scan Attack
2020-04-13 01:43:38

Recently Reported IPs

119.138.225.43 119.138.225.47 119.138.225.5 119.138.225.51
119.138.225.54 119.138.225.57 119.138.225.58 119.138.225.60
119.138.225.62 119.138.225.65 119.138.225.68 119.138.225.7
119.138.225.72 119.139.35.12 119.140.160.112 119.140.160.122
119.140.160.129 119.140.160.132 119.140.160.135 119.140.160.137