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

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

;; QUESTION SECTION:
;138.121.25.69.			IN	A

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

;; Query time: 114 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 07:22:16 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 69.25.121.138.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 69.25.121.138.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
94.140.114.17 attackbotsspam
[Mon May 11 11:18:28.446478 2020] [:error] [pid 23098:tid 140213493257984] [client 94.140.114.17:443] [client 94.140.114.17] ModSecurity: Access denied with code 403 (phase 1). Match of "within %{tx.allowed_http_versions}" against "REQUEST_PROTOCOL" required. [file "/etc/modsecurity/owasp-modsecurity-crs-3.2.0/rules/REQUEST-920-PROTOCOL-ENFORCEMENT.conf"] [line "972"] [id "920430"] [msg "HTTP protocol version is not allowed by policy"] [data "HTTP/1.0"] [severity "CRITICAL"] [ver "OWASP_CRS/3.2.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-protocol"] [tag "OWASP_CRS"] [tag "OWASP_CRS/POLICY/PROTOCOL_NOT_ALLOWED"] [tag "WASCTC/WASC-21"] [tag "OWASP_TOP_10/A6"] [tag "PCI/6.5.10"] [hostname "karangploso.jatim.bmkg.go.id"] [uri "/"] [unique_id "XrjSFJOY0tIJkGtidjyfxwAAAhw"]
...
2020-05-11 14:11:37
85.172.11.101 attackspam
SSH Brute-Force attacks
2020-05-11 14:10:41
40.70.83.19 attackspam
$f2bV_matches
2020-05-11 14:14:07
149.129.33.182 attackbots
" "
2020-05-11 14:11:22
103.65.195.163 attackbotsspam
May 11 05:53:30 buvik sshd[24101]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.65.195.163
May 11 05:53:32 buvik sshd[24101]: Failed password for invalid user derrick from 103.65.195.163 port 35598 ssh2
May 11 05:54:36 buvik sshd[24248]: Invalid user user from 103.65.195.163
...
2020-05-11 14:05:31
220.187.224.194 attackspam
CN_MAINT-CHINANET-ZJ_<177>1589169292 [1:2010935:3] ET SCAN Suspicious inbound to MSSQL port 1433 [Classification: Potentially Bad Traffic] [Priority: 2]:  {TCP} 220.187.224.194:23456
2020-05-11 13:49:03
77.23.10.115 attackbots
Invalid user haproxy from 77.23.10.115 port 43644
2020-05-11 13:39:02
104.248.230.14 attackbots
May 11 05:56:15 scw-6657dc sshd[15630]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.230.14
May 11 05:56:15 scw-6657dc sshd[15630]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.230.14
May 11 05:56:18 scw-6657dc sshd[15630]: Failed password for invalid user nagios from 104.248.230.14 port 59372 ssh2
...
2020-05-11 14:15:58
116.56.134.14 attackbotsspam
2020-05-11T05:00:15.292699shield sshd\[4551\]: Invalid user kush from 116.56.134.14 port 55380
2020-05-11T05:00:15.296606shield sshd\[4551\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.56.134.14
2020-05-11T05:00:16.943986shield sshd\[4551\]: Failed password for invalid user kush from 116.56.134.14 port 55380 ssh2
2020-05-11T05:04:50.059358shield sshd\[5186\]: Invalid user git from 116.56.134.14 port 50603
2020-05-11T05:04:50.063592shield sshd\[5186\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.56.134.14
2020-05-11 13:41:30
103.87.214.100 attackspambots
srv02 Mass scanning activity detected Target: 3591  ..
2020-05-11 13:32:56
144.217.83.201 attack
*Port Scan* detected from 144.217.83.201 (CA/Canada/Quebec/Montreal (Ville-Marie)/201.ip-144-217-83.net). 4 hits in the last 10 seconds
2020-05-11 13:32:39
190.85.140.93 attackspambots
$f2bV_matches
2020-05-11 13:55:20
191.255.47.54 attackbots
Port probing on unauthorized port 8080
2020-05-11 13:33:26
177.128.104.207 attackbotsspam
May 11 16:09:54 localhost sshd[1014106]: Invalid user alan from 177.128.104.207 port 33928
...
2020-05-11 14:15:20
118.70.72.103 attackbots
May 11 05:52:53 ns382633 sshd\[8643\]: Invalid user deploy from 118.70.72.103 port 44058
May 11 05:52:53 ns382633 sshd\[8643\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.70.72.103
May 11 05:52:55 ns382633 sshd\[8643\]: Failed password for invalid user deploy from 118.70.72.103 port 44058 ssh2
May 11 06:04:43 ns382633 sshd\[10633\]: Invalid user odin from 118.70.72.103 port 33536
May 11 06:04:43 ns382633 sshd\[10633\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.70.72.103
2020-05-11 13:39:18

Recently Reported IPs

138.121.25.67 138.121.25.198 138.121.25.86 118.174.69.52
138.121.27.102 138.121.27.181 138.121.27.49 118.174.69.56
138.121.28.129 138.121.28.132 138.121.28.122 138.121.28.105
138.121.28.137 138.121.28.144 138.121.28.177 138.121.28.155
138.121.29.116 138.121.29.123 118.174.69.61 138.121.29.135