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: South Africa

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

;; QUESTION SECTION:
;129.232.138.56.			IN	A

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

;; Query time: 24 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 04:50:19 CST 2022
;; MSG SIZE  rcvd: 107
Host info
56.138.232.129.in-addr.arpa domain name pointer dedi607.jnb2.host-h.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
56.138.232.129.in-addr.arpa	name = dedi607.jnb2.host-h.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
106.12.113.223 attackbots
Invalid user tecnici from 106.12.113.223 port 46772
2019-11-01 04:12:21
106.13.32.106 attack
2019-10-30 17:57:57,561 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 106.13.32.106
2019-10-30 18:22:13,617 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 106.13.32.106
2019-10-30 18:45:18,592 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 106.13.32.106
2019-10-30 19:07:04,864 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 106.13.32.106
2019-10-30 19:27:57,936 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 106.13.32.106
2019-10-30 17:57:57,561 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 106.13.32.106
2019-10-30 18:22:13,617 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 106.13.32.106
2019-10-30 18:45:18,592 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 106.13.32.106
2019-10-30 19:07:04,864 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 106.13.32.106
2019-10-30 19:27:57,936 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 106.13.32.106
2019-10-30 17:57:57,561 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 106.13.32.106
2019-10-30 1
2019-11-01 04:10:10
41.77.145.14 attack
Unauthorized connection attempt from IP address 41.77.145.14 on Port 445(SMB)
2019-11-01 04:40:53
92.63.194.148 attackbots
10/31/2019-21:15:48.231457 92.63.194.148 Protocol: 6 ET DROP Dshield Block Listed Source group 1
2019-11-01 04:34:14
162.209.225.90 attack
[ThuOct3112:57:23.1536112019][:error][pid24150:tid47654458226432][client162.209.225.90:57172][client162.209.225.90]ModSecurity:Accessdeniedwithcode403\(phase2\).Patternmatch"\(\?:\\\\\\\\\(chr\?\\\\\\\\\(\?[0-9]{1\,3}\?\\\\\\\\\)\|\?=\?f\(\?:open\|write\)\?\\\\\\\\\(\|\\\\\\\\b\(\?:passthru\|serialize\|php_uname\|phpinfo\|shell_exec\|preg_\\\\\\\\w \|mysql_query\|exec\|eval\|base64_decode\|decode_base64\|rot13\|base64_url_decode\|gz\(\?:inflate\|decode\|uncompress\)\|strrev\|zlib_\\\\\\\\w \)\\\\\\\\b\?\(\?..."atARGS:admin.[file"/usr/local/apache.ea3/conf/modsec_rules/10_asl_rules.conf"][line"767"][id"340095"][rev"53"][msg"Atomicorp.comWAFRules:AttackBlocked-PHPfunctioninArgument-thismaybeanattack."][data"die\(@md5\,ARGS:admin"][severity"CRITICAL"][hostname"148.251.104.81"][uri"/5168fb94/admin.php"][unique_id"XbrMI8oEtBiITytShBu9ngAAAAo"][ThuOct3112:57:23.5074682019][:error][pid24410:tid47654456125184][client162.209.225.90:57306][client162.209.225.90]ModSecurity:Accessdeniedwithcode403\(
2019-11-01 04:09:29
197.254.7.178 attack
postfix
2019-11-01 04:08:01
106.13.98.148 attack
Oct 31 21:14:41 server sshd\[30155\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.98.148  user=root
Oct 31 21:14:43 server sshd\[30155\]: Failed password for root from 106.13.98.148 port 48410 ssh2
Oct 31 21:39:34 server sshd\[3097\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.98.148  user=root
Oct 31 21:39:36 server sshd\[3097\]: Failed password for root from 106.13.98.148 port 45800 ssh2
Oct 31 21:43:58 server sshd\[4144\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.98.148  user=nagios
...
2019-11-01 04:07:32
179.233.31.10 attackspambots
Oct 31 18:04:18 work-partkepr sshd\[5559\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.233.31.10  user=root
Oct 31 18:04:20 work-partkepr sshd\[5559\]: Failed password for root from 179.233.31.10 port 20918 ssh2
...
2019-11-01 04:13:01
36.110.50.217 attackspam
2019-10-31T20:15:43.868954abusebot-5.cloudsearch.cf sshd\[3937\]: Invalid user elena from 36.110.50.217 port 53224
2019-11-01 04:38:49
49.231.222.9 attackbotsspam
Unauthorized connection attempt from IP address 49.231.222.9 on Port 445(SMB)
2019-11-01 04:41:23
92.53.90.179 attackbots
Port scan on 5 port(s): 5797 5975 6035 6179 6226
2019-11-01 04:42:00
134.175.151.155 attackbotsspam
Oct 31 21:06:52 sd-53420 sshd\[1467\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.151.155  user=root
Oct 31 21:06:54 sd-53420 sshd\[1467\]: Failed password for root from 134.175.151.155 port 49118 ssh2
Oct 31 21:11:13 sd-53420 sshd\[1818\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.151.155  user=root
Oct 31 21:11:15 sd-53420 sshd\[1818\]: Failed password for root from 134.175.151.155 port 59260 ssh2
Oct 31 21:15:39 sd-53420 sshd\[2167\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.151.155  user=root
...
2019-11-01 04:40:05
222.186.175.202 attackbots
Oct 31 21:27:03 MK-Soft-Root1 sshd[17153]: Failed password for root from 222.186.175.202 port 18790 ssh2
Oct 31 21:27:08 MK-Soft-Root1 sshd[17153]: Failed password for root from 222.186.175.202 port 18790 ssh2
...
2019-11-01 04:30:55
24.104.74.26 attack
Unauthorized connection attempt from IP address 24.104.74.26 on Port 445(SMB)
2019-11-01 04:39:35
103.101.163.144 attackbotsspam
2019-10-30 04:55:26,908 fail2ban.actions        \[1884\]: NOTICE  \[Postifx_Ban\] Ban 103.101.163.144
2019-10-30 04:56:50,265 fail2ban.actions        \[1884\]: NOTICE  \[plesk-postfix\] Ban 103.101.163.144
2019-10-30 05:04:27,902 fail2ban.actions        \[1884\]: NOTICE  \[Postifx_Ban\] Ban 103.101.163.144
2019-10-30 05:09:39,962 fail2ban.actions        \[1884\]: NOTICE  \[plesk-postfix\] Ban 103.101.163.144
2019-10-30 05:13:34,914 fail2ban.actions        \[1884\]: NOTICE  \[Postifx_Ban\] Ban 103.101.163.144
2019-10-30 04:55:26,908 fail2ban.actions        \[1884\]: NOTICE  \[Postifx_Ban\] Ban 103.101.163.144
2019-10-30 04:56:50,265 fail2ban.actions        \[1884\]: NOTICE  \[plesk-postfix\] Ban 103.101.163.144
2019-10-30 05:04:27,902 fail2ban.actions        \[1884\]: NOTICE  \[Postifx_Ban\] Ban 103.101.163.144
2019-10-30 05:09:39,962 fail2ban.actions        \[1884\]: NOTICE  \[plesk-postfix\] Ban 103.101.163.144
2019-10-30 05:13:34,914 fail2ban.actions        \[1884\]: NOTICE  \[Postifx_Ban\] Ban 103.101.163.
2019-11-01 04:16:54

Recently Reported IPs

129.232.138.55 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 129.244.144.31 118.171.186.123
129.241.30.61 129.247.247.137 129.241.30.49 129.241.56.200