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

;; QUESTION SECTION:
;41.23.134.34.			IN	A

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

;; Query time: 9 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 17 19:25:13 CST 2025
;; MSG SIZE  rcvd: 105
Host info
34.134.23.41.in-addr.arpa domain name pointer vc-41-23-134-34.umts.vodacom.co.za.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
34.134.23.41.in-addr.arpa	name = vc-41-23-134-34.umts.vodacom.co.za.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
27.203.168.188 attackbotsspam
Unauthorized connection attempt detected from IP address 27.203.168.188 to port 23 [J]
2020-02-04 15:49:27
101.51.72.204 attackbots
unauthorized connection attempt
2020-02-04 15:25:38
125.224.17.184 attackspam
unauthorized connection attempt
2020-02-04 15:28:29
118.97.31.218 attackbotsspam
Unauthorized connection attempt detected from IP address 118.97.31.218 to port 445
2020-02-04 15:54:09
124.219.105.17 attackspam
unauthorized connection attempt
2020-02-04 16:04:07
109.185.229.134 attack
unauthorized connection attempt
2020-02-04 15:32:56
115.238.62.154 attackbotsspam
Feb  4 01:52:56 plusreed sshd[30462]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.238.62.154  user=root
Feb  4 01:52:57 plusreed sshd[30462]: Failed password for root from 115.238.62.154 port 27359 ssh2
...
2020-02-04 15:36:15
120.132.124.237 attackspambots
Feb  3 21:17:36 auw2 sshd\[16778\]: Invalid user avahi from 120.132.124.237
Feb  3 21:17:36 auw2 sshd\[16778\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.132.124.237
Feb  3 21:17:38 auw2 sshd\[16778\]: Failed password for invalid user avahi from 120.132.124.237 port 47390 ssh2
Feb  3 21:20:29 auw2 sshd\[17082\]: Invalid user dummy from 120.132.124.237
Feb  3 21:20:29 auw2 sshd\[17082\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.132.124.237
2020-02-04 15:44:24
202.29.213.206 attackbots
20/2/3@23:55:08: FAIL: Alarm-Network address from=202.29.213.206
...
2020-02-04 15:43:25
176.59.139.97 attackspambots
1580792095 - 02/04/2020 05:54:55 Host: 176.59.139.97/176.59.139.97 Port: 445 TCP Blocked
2020-02-04 15:53:12
14.187.136.189 attackspam
unauthorized connection attempt
2020-02-04 15:20:29
218.92.0.207 attackspam
2020-02-04T02:35:16.519279vostok sshd\[4341\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.207  user=root | Triggered by Fail2Ban at Vostok web server
2020-02-04 15:50:15
222.186.30.76 attack
SSH authentication failure x 6 reported by Fail2Ban
...
2020-02-04 15:41:49
222.186.15.166 attackspam
Feb  4 08:30:49 vpn01 sshd[18255]: Failed password for root from 222.186.15.166 port 53060 ssh2
Feb  4 08:30:51 vpn01 sshd[18255]: Failed password for root from 222.186.15.166 port 53060 ssh2
...
2020-02-04 15:35:42
123.10.0.89 attackspambots
unauthorized connection attempt
2020-02-04 15:44:08

Recently Reported IPs

169.38.210.249 149.40.178.133 169.239.15.122 241.158.197.184
254.60.178.50 167.75.173.103 188.148.106.208 217.243.34.246
167.162.28.50 213.214.185.15 216.70.29.26 57.187.84.65
235.231.213.91 95.249.143.213 12.247.55.110 220.42.202.22
137.186.137.159 228.90.210.232 137.211.221.243 206.143.119.227