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

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

;; QUESTION SECTION:
;129.232.138.225.		IN	A

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

;; Query time: 62 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 04:50:18 CST 2022
;; MSG SIZE  rcvd: 108
Host info
225.138.232.129.in-addr.arpa domain name pointer www127.jnb2.host-h.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
225.138.232.129.in-addr.arpa	name = www127.jnb2.host-h.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
79.9.171.88 attack
$f2bV_matches
2020-09-04 18:50:52
218.92.0.198 attackbots
2020-09-04T08:54:58.907746rem.lavrinenko.info sshd[22008]: refused connect from 218.92.0.198 (218.92.0.198)
2020-09-04T08:56:43.317411rem.lavrinenko.info sshd[22009]: refused connect from 218.92.0.198 (218.92.0.198)
2020-09-04T08:58:37.374136rem.lavrinenko.info sshd[22012]: refused connect from 218.92.0.198 (218.92.0.198)
2020-09-04T09:00:35.796710rem.lavrinenko.info sshd[22014]: refused connect from 218.92.0.198 (218.92.0.198)
2020-09-04T09:02:27.269610rem.lavrinenko.info sshd[22030]: refused connect from 218.92.0.198 (218.92.0.198)
...
2020-09-04 18:54:39
114.172.166.134 attackspam
Sep  3 18:47:50 pixelmemory sshd[3481509]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.172.166.134 
Sep  3 18:47:50 pixelmemory sshd[3481509]: Invalid user le from 114.172.166.134 port 60131
Sep  3 18:47:52 pixelmemory sshd[3481509]: Failed password for invalid user le from 114.172.166.134 port 60131 ssh2
Sep  3 18:50:50 pixelmemory sshd[3481873]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.172.166.134  user=root
Sep  3 18:50:51 pixelmemory sshd[3481873]: Failed password for root from 114.172.166.134 port 54326 ssh2
...
2020-09-04 19:18:39
165.90.239.203 attackbotsspam
Automatic report - Port Scan Attack
2020-09-04 18:55:03
106.13.71.1 attackspambots
2020-07-27 18:53:44,650 fail2ban.actions        [18606]: NOTICE  [sshd] Ban 106.13.71.1
2020-07-27 19:08:04,552 fail2ban.actions        [18606]: NOTICE  [sshd] Ban 106.13.71.1
2020-07-27 19:22:17,060 fail2ban.actions        [18606]: NOTICE  [sshd] Ban 106.13.71.1
2020-07-27 19:36:01,044 fail2ban.actions        [18606]: NOTICE  [sshd] Ban 106.13.71.1
2020-07-27 19:49:11,834 fail2ban.actions        [18606]: NOTICE  [sshd] Ban 106.13.71.1
...
2020-09-04 19:18:56
121.204.120.214 attack
Sep  3 21:21:54 m3 sshd[22254]: Failed password for r.r from 121.204.120.214 port 54144 ssh2
Sep  3 21:35:50 m3 sshd[23812]: Invalid user sispac from 121.204.120.214
Sep  3 21:35:53 m3 sshd[23812]: Failed password for invalid user sispac from 121.204.120.214 port 52848 ssh2


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=121.204.120.214
2020-09-04 19:07:06
36.89.18.217 attackspambots
Honeypot attack, port: 445, PTR: PTR record not found
2020-09-04 19:13:42
195.154.179.3 attackbotsspam
Sep  4 16:25:47 itv-usvr-01 sshd[23221]: Invalid user admin from 195.154.179.3
2020-09-04 18:53:21
182.150.57.34 attackbots
Sep  4 07:59:13 rocket sshd[21264]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.150.57.34
Sep  4 07:59:16 rocket sshd[21264]: Failed password for invalid user jur from 182.150.57.34 port 28086 ssh2
...
2020-09-04 19:19:55
42.104.109.194 attackspambots
Invalid user ftpadmin from 42.104.109.194 port 44964
2020-09-04 19:00:33
64.225.1.34 attackbotsspam
64.225.1.34 - - \[03/Sep/2020:18:43:15 +0200\] "GET / HTTP/1.0" 301 178 "-" "Mozilla/5.0 \(compatible\; NetcraftSurveyAgent/1.0\; +info@netcraft.com\)"
...
2020-09-04 19:20:32
104.206.128.30 attack
 TCP (SYN) 104.206.128.30:52745 -> port 1433, len 44
2020-09-04 19:13:25
51.68.11.203 attack
lee-0 : Trying access unauthorized files=>/administrator/components/com_akeeba/backup/akaccesscheck_29ae8bd63436636bf8313455aabe5f77.txt()
2020-09-04 19:19:27
47.74.3.113 attackspam
TCP ports : 13650 / 14534 / 24922 / 28538
2020-09-04 19:02:32
113.140.80.174 attackspam
Sep  4 09:08:42 h2646465 sshd[24146]: Invalid user market from 113.140.80.174
Sep  4 09:08:42 h2646465 sshd[24146]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.140.80.174
Sep  4 09:08:42 h2646465 sshd[24146]: Invalid user market from 113.140.80.174
Sep  4 09:08:44 h2646465 sshd[24146]: Failed password for invalid user market from 113.140.80.174 port 6350 ssh2
Sep  4 09:11:34 h2646465 sshd[24818]: Invalid user hbr from 113.140.80.174
Sep  4 09:11:34 h2646465 sshd[24818]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.140.80.174
Sep  4 09:11:34 h2646465 sshd[24818]: Invalid user hbr from 113.140.80.174
Sep  4 09:11:36 h2646465 sshd[24818]: Failed password for invalid user hbr from 113.140.80.174 port 21669 ssh2
Sep  4 09:12:30 h2646465 sshd[24876]: Invalid user testuser from 113.140.80.174
...
2020-09-04 19:11:37

Recently Reported IPs

118.171.185.35 129.232.138.229 129.232.138.37 129.232.138.244
129.232.138.63 129.232.138.55 129.232.138.56 129.232.138.75
129.232.138.78 129.232.138.8 118.171.185.51 129.232.138.80
129.232.143.208 129.232.144.114 118.171.185.56 92.156.70.166
118.171.185.86 118.171.186.112 118.171.186.115 118.171.186.121