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

Region: Gauteng

Country: South Africa

Internet Service Provider: Vodacom

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

;; QUESTION SECTION:
;41.30.164.40.			IN	A

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

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Aug 05 13:10:19 CST 2022
;; MSG SIZE  rcvd: 105
Host info
40.164.30.41.in-addr.arpa domain name pointer vc-gp-s-41-30-164-40.umts.vodacom.co.za.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
40.164.30.41.in-addr.arpa	name = vc-gp-s-41-30-164-40.umts.vodacom.co.za.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
134.175.225.94 attack
2019-07-12T18:41:52.257931  sshd[32689]: Invalid user james from 134.175.225.94 port 40570
2019-07-12T18:41:52.273305  sshd[32689]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.225.94
2019-07-12T18:41:52.257931  sshd[32689]: Invalid user james from 134.175.225.94 port 40570
2019-07-12T18:41:54.350098  sshd[32689]: Failed password for invalid user james from 134.175.225.94 port 40570 ssh2
2019-07-12T18:49:09.304728  sshd[303]: Invalid user yyy from 134.175.225.94 port 41214
...
2019-07-13 01:22:06
198.245.49.37 attack
Jul 12 19:19:37 eventyay sshd[22565]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=198.245.49.37
Jul 12 19:19:38 eventyay sshd[22565]: Failed password for invalid user prueba from 198.245.49.37 port 36516 ssh2
Jul 12 19:24:36 eventyay sshd[23857]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=198.245.49.37
...
2019-07-13 01:26:31
190.8.80.42 attackspambots
Jul 12 19:18:33 mail sshd\[29865\]: Invalid user git from 190.8.80.42 port 34522
Jul 12 19:18:33 mail sshd\[29865\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.8.80.42
Jul 12 19:18:35 mail sshd\[29865\]: Failed password for invalid user git from 190.8.80.42 port 34522 ssh2
Jul 12 19:25:05 mail sshd\[30888\]: Invalid user prueba from 190.8.80.42 port 36810
Jul 12 19:25:05 mail sshd\[30888\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.8.80.42
2019-07-13 01:43:29
218.92.0.154 attack
2019-07-12T18:12:17.881624centos sshd\[28350\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.154  user=root
2019-07-12T18:12:19.949019centos sshd\[28350\]: Failed password for root from 218.92.0.154 port 26508 ssh2
2019-07-12T18:12:22.892616centos sshd\[28350\]: Failed password for root from 218.92.0.154 port 26508 ssh2
2019-07-13 01:49:58
185.74.4.189 attack
Jul 12 18:56:57 vps647732 sshd[23663]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.74.4.189
Jul 12 18:56:59 vps647732 sshd[23663]: Failed password for invalid user minecraft from 185.74.4.189 port 36068 ssh2
...
2019-07-13 01:04:18
149.56.44.47 attackspam
2019-07-12T18:58:44.8445781240 sshd\[14404\]: Invalid user admin from 149.56.44.47 port 43426
2019-07-12T18:58:44.8523481240 sshd\[14404\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=149.56.44.47
2019-07-12T18:58:46.8586871240 sshd\[14404\]: Failed password for invalid user admin from 149.56.44.47 port 43426 ssh2
...
2019-07-13 01:14:46
142.93.18.15 attackspam
Jul 12 13:43:06 plusreed sshd[8029]: Invalid user sambaup from 142.93.18.15
...
2019-07-13 01:47:14
106.13.104.94 attackspambots
Brute force attempt
2019-07-13 01:19:06
37.34.177.134 attackbotsspam
Automated report - ssh fail2ban:
Jul 12 12:12:11 wrong password, user=ww, port=44970, ssh2
Jul 12 12:46:29 authentication failure 
Jul 12 12:46:32 wrong password, user=ts, port=46314, ssh2
2019-07-13 01:46:24
84.217.220.68 attack
SSH/22 Probe, BF, Hack -
2019-07-13 01:24:25
177.87.68.136 attackbotsspam
mail.log:Jun 30 12:04:00 mail postfix/smtpd[27180]: warning: unknown[177.87.68.136]: SASL PLAIN authentication failed: authentication failure
2019-07-13 01:24:55
168.228.151.215 attackspam
failed_logins
2019-07-13 01:31:31
5.8.45.2 attack
Automatic report - Web App Attack
2019-07-13 01:02:20
103.112.213.133 attackbotsspam
Jul 12 12:16:39 andromeda postfix/smtpd\[39999\]: warning: unknown\[103.112.213.133\]: SASL CRAM-MD5 authentication failed: authentication failure
Jul 12 12:16:39 andromeda postfix/smtpd\[39999\]: warning: unknown\[103.112.213.133\]: SASL PLAIN authentication failed: authentication failure
Jul 12 12:16:40 andromeda postfix/smtpd\[39999\]: warning: unknown\[103.112.213.133\]: SASL LOGIN authentication failed: authentication failure
Jul 12 12:16:42 andromeda postfix/smtpd\[40092\]: warning: unknown\[103.112.213.133\]: SASL CRAM-MD5 authentication failed: authentication failure
Jul 12 12:16:42 andromeda postfix/smtpd\[40092\]: warning: unknown\[103.112.213.133\]: SASL PLAIN authentication failed: authentication failure
2019-07-13 01:35:55
186.113.126.4 attackspam
Unauthorized connection attempt from IP address 186.113.126.4 on Port 445(SMB)
2019-07-13 01:03:40

Recently Reported IPs

80.66.66.21 185.71.65.15 185.71.65.7 43.171.137.210
74.105.47.237 142.4.193.191 32.25.241.70 197.243.22.12
193.200.183.126 138.166.157.121 180.100.181.216 81.10.155.187
22.247.30.121 45.58.154.183 151.177.55.187 165.222.193.247
183.181.94.214 176.228.47.149 166.80.145.168 247.6.134.75