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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;41.1.72.166.			IN	A

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

;; Query time: 73 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat May 16 06:02:43 CST 2020
;; MSG SIZE  rcvd: 115
Host info
Host 166.72.1.41.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 166.72.1.41.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
162.243.131.164 attack
GPL DNS named version attempt - port: 53 proto: UDP cat: Attempted Information Leak
2020-07-05 21:31:38
89.248.172.85 attackbots
 TCP (SYN) 89.248.172.85:44922 -> port 4302, len 44
2020-07-05 21:55:54
219.138.66.239 attackbots
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2020-07-05 21:42:25
103.219.112.1 attackspam
" "
2020-07-05 21:33:19
23.105.215.254 attackspam
Jul  5 14:34:31 ns392434 sshd[11052]: Invalid user feng from 23.105.215.254 port 39944
Jul  5 14:34:31 ns392434 sshd[11052]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=23.105.215.254
Jul  5 14:34:31 ns392434 sshd[11052]: Invalid user feng from 23.105.215.254 port 39944
Jul  5 14:34:33 ns392434 sshd[11052]: Failed password for invalid user feng from 23.105.215.254 port 39944 ssh2
Jul  5 14:45:47 ns392434 sshd[11271]: Invalid user bet from 23.105.215.254 port 55132
Jul  5 14:45:47 ns392434 sshd[11271]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=23.105.215.254
Jul  5 14:45:47 ns392434 sshd[11271]: Invalid user bet from 23.105.215.254 port 55132
Jul  5 14:45:49 ns392434 sshd[11271]: Failed password for invalid user bet from 23.105.215.254 port 55132 ssh2
Jul  5 14:53:44 ns392434 sshd[11401]: Invalid user gcl from 23.105.215.254 port 51042
2020-07-05 21:23:27
85.209.0.131 attackspambots
ET SCAN Potential SSH Scan - port: 22 proto: TCP cat: Attempted Information Leak
2020-07-05 21:35:33
52.229.160.94 attackbots
ET CINS Active Threat Intelligence Poor Reputation IP group 39 - port: 19932 proto: TCP cat: Misc Attack
2020-07-05 21:38:38
167.114.3.158 attackbots
Jul  5 19:22:40 itv-usvr-02 sshd[17120]: Invalid user solange from 167.114.3.158 port 48530
Jul  5 19:22:40 itv-usvr-02 sshd[17120]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.114.3.158
Jul  5 19:22:40 itv-usvr-02 sshd[17120]: Invalid user solange from 167.114.3.158 port 48530
Jul  5 19:22:43 itv-usvr-02 sshd[17120]: Failed password for invalid user solange from 167.114.3.158 port 48530 ssh2
Jul  5 19:26:42 itv-usvr-02 sshd[17332]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.114.3.158  user=root
Jul  5 19:26:43 itv-usvr-02 sshd[17332]: Failed password for root from 167.114.3.158 port 56180 ssh2
2020-07-05 21:50:32
45.120.69.97 attack
Jul  5 14:48:36 gestao sshd[2076]: Failed password for root from 45.120.69.97 port 51230 ssh2
Jul  5 14:52:18 gestao sshd[2137]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.120.69.97 
Jul  5 14:52:20 gestao sshd[2137]: Failed password for invalid user ubuntu from 45.120.69.97 port 48832 ssh2
...
2020-07-05 22:03:37
164.155.64.106 attackspambots
Unauthorized connection attempt detected from IP address 164.155.64.106 to port 1433 [T]
2020-07-05 21:31:16
120.31.61.215 attackbotsspam
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2020-07-05 21:52:50
220.163.15.100 attackbotsspam
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2020-07-05 21:41:58
59.63.163.165 attack
" "
2020-07-05 22:01:46
185.156.73.38 attackbotsspam
probes 92 times on the port 10000 10001 10033 11011 11111 13389 13390 2000 20000 20002 20089 22022 23389 23390 23456 30089 3089 33001 3333 33391 33392 33399 3344 3380 3381 3385 3387 33889 3389 33893 33895 33897 33898 33899 3390 3391 3393 3394 3395 3396 3397 3398 3399 4000 40000 40004 4004 4040 4089 4321 43389 44044 44444 4489 50000 50001 5005 50089 5050 5089 53390 54321 5555 55555 6000 60000 60001 6006 63389 6666 6689 7000 7007 7070 7089 7789 8080 8089 8888 8899 8933 8989 9000 9009 9089 9090 9833 9999 resulting in total of 105 scans from 185.156.72.0/22 block.
2020-07-05 21:29:10
52.255.149.196 attackbots
Fail2Ban Ban Triggered
2020-07-05 22:02:11

Recently Reported IPs

116.103.60.207 148.166.79.83 64.90.228.144 126.77.213.155
191.6.35.129 184.203.137.3 64.224.190.219 91.8.1.114
196.90.121.123 114.239.207.220 217.76.174.90 120.16.192.94
2.253.40.195 37.159.126.249 112.155.77.99 83.204.217.126
104.194.11.180 49.215.237.242 95.245.93.89 207.63.118.203