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

;; QUESTION SECTION:
;41.195.194.211.			IN	A

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

;; Query time: 16 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Jan 24 21:23:52 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 211.194.195.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 211.194.195.41.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
167.114.24.187 attackspambots
Fail2Ban Ban Triggered
2020-02-13 01:11:47
14.177.99.174 attack
Feb 12 14:24:46 mxgate1 postfix/postscreen[27996]: CONNECT from [14.177.99.174]:26162 to [176.31.12.44]:25
Feb 12 14:24:46 mxgate1 postfix/dnsblog[27997]: addr 14.177.99.174 listed by domain zen.spamhaus.org as 127.0.0.4
Feb 12 14:24:46 mxgate1 postfix/dnsblog[27997]: addr 14.177.99.174 listed by domain zen.spamhaus.org as 127.0.0.3
Feb 12 14:24:46 mxgate1 postfix/dnsblog[27997]: addr 14.177.99.174 listed by domain zen.spamhaus.org as 127.0.0.11
Feb 12 14:24:46 mxgate1 postfix/dnsblog[27998]: addr 14.177.99.174 listed by domain cbl.abuseat.org as 127.0.0.2
Feb 12 14:24:46 mxgate1 postfix/dnsblog[28000]: addr 14.177.99.174 listed by domain bl.spamcop.net as 127.0.0.2
Feb 12 14:24:46 mxgate1 postfix/dnsblog[28001]: addr 14.177.99.174 listed by domain b.barracudacentral.org as 127.0.0.2
Feb 12 14:24:52 mxgate1 postfix/postscreen[27996]: DNSBL rank 5 for [14.177.99.174]:26162
Feb 12 14:24:54 mxgate1 postfix/tlsproxy[28145]: CONNECT from [14.177.99.174]:26162
Feb x@x


........
------------------------------------
2020-02-13 01:22:41
59.127.27.45 attackspam
20/2/12@08:43:27: FAIL: Alarm-Telnet address from=59.127.27.45
20/2/12@08:43:27: FAIL: Alarm-Telnet address from=59.127.27.45
...
2020-02-13 01:51:28
192.99.36.166 attackbotsspam
20 attempts against mh-misbehave-ban on sand
2020-02-13 01:52:18
105.154.74.152 attackspambots
[Tue Feb 11 11:40:48 2020] [error] [client 105.154.74.152] client sent HTTP/1.1 request without hostname (see RFC2616 section 14.23): /
2020-02-13 01:38:37
192.241.229.232 attackspambots
SIP/5060 Probe, BF, Hack -
2020-02-13 01:32:04
86.11.179.221 attackspambots
[Mon Feb 10 10:38:48 2020] [error] [client 86.11.179.221] client sent HTTP/1.1 request without hostname (see RFC2616 section 14.23): /
2020-02-13 01:45:13
45.234.116.2 attackbots
Received: from maerskline.com (45.234.116.2) Wed, 12 Feb 2020 14:23:07
From: Maersk Notification 
To: <>
Subject: Maersk : Arrival Notice ready for Bill of Lading 969812227
Date: Wed, 12 Feb 2020 11:21:29 -0300
Message-ID: <20200212112129@maerskline.com>
Return-Path: notification@maerskline.com
X-MS-Exchange-Organization-PRD: maerskline.com
Received-SPF: SoftFail (domain of transitioning notification@maerskline.com discourages use of 45.234.116.2 as permitted sender)
OrigIP:45.234.116.2
2020-02-13 01:47:19
186.212.65.168 attackbots
Automatic report - Port Scan Attack
2020-02-13 01:12:45
79.132.176.142 attackspambots
Feb 12 07:11:58 ingram sshd[8906]: Invalid user pi from 79.132.176.142
Feb 12 07:11:58 ingram sshd[8906]: Failed none for invalid user pi from 79.132.176.142 port 49298 ssh2
Feb 12 07:11:59 ingram sshd[8909]: Invalid user pi from 79.132.176.142
Feb 12 07:11:59 ingram sshd[8909]: Failed none for invalid user pi from 79.132.176.142 port 49304 ssh2
Feb 12 07:11:59 ingram sshd[8906]: Failed password for invalid user pi from 79.132.176.142 port 49298 ssh2
Feb 12 07:11:59 ingram sshd[8909]: Failed password for invalid user pi from 79.132.176.142 port 49304 ssh2


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=79.132.176.142
2020-02-13 01:40:04
113.107.244.124 attackspam
Feb 12 16:09:09 legacy sshd[4477]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.107.244.124
Feb 12 16:09:11 legacy sshd[4477]: Failed password for invalid user student02 from 113.107.244.124 port 59168 ssh2
Feb 12 16:13:45 legacy sshd[4683]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.107.244.124
...
2020-02-13 01:26:16
2.136.134.161 attackspam
MultiHost/MultiPort Probe, Scan, Hack -
2020-02-13 01:16:58
184.185.236.93 attackbotsspam
(imapd) Failed IMAP login from 184.185.236.93 (US/United States/-): 1 in the last 3600 secs
2020-02-13 01:31:00
119.81.213.101 attackbots
Feb 12 14:14:53 yesfletchmain sshd\[28554\]: Invalid user sariah from 119.81.213.101 port 52900
Feb 12 14:14:54 yesfletchmain sshd\[28554\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.81.213.101
Feb 12 14:14:56 yesfletchmain sshd\[28554\]: Failed password for invalid user sariah from 119.81.213.101 port 52900 ssh2
Feb 12 14:17:05 yesfletchmain sshd\[28597\]: Invalid user Jewel from 119.81.213.101 port 44970
Feb 12 14:17:05 yesfletchmain sshd\[28597\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.81.213.101
...
2020-02-13 01:47:59
36.155.113.199 attack
SSH bruteforce
2020-02-13 01:08:52

Recently Reported IPs

87.14.35.216 140.199.97.28 176.146.167.227 199.184.69.71
161.185.196.35 31.13.43.214 242.211.224.192 168.79.111.193
177.153.64.108 175.138.114.75 231.149.30.160 186.110.216.73
14.196.4.246 179.216.139.102 143.233.206.176 86.194.54.231
53.193.87.137 251.106.134.75 175.165.208.158 127.123.175.248