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

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

;; QUESTION SECTION:
;13.244.99.41.			IN	A

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

;; Query time: 23 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 21 06:28:50 CST 2022
;; MSG SIZE  rcvd: 105
Host info
41.99.244.13.in-addr.arpa domain name pointer ec2-13-244-99-41.af-south-1.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
41.99.244.13.in-addr.arpa	name = ec2-13-244-99-41.af-south-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
36.90.208.173 attack
2020-02-13T02:47:02.272Z CLOSE host=36.90.208.173 port=60260 fd=4 time=20.013 bytes=31
...
2020-03-13 04:51:07
89.248.174.213 attack
Mar 12 21:30:24 debian-2gb-nbg1-2 kernel: \[6304160.885550\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=89.248.174.213 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=47857 PROTO=TCP SPT=44661 DPT=44030 WINDOW=1024 RES=0x00 SYN URGP=0
2020-03-13 04:45:59
36.92.56.213 attack
2019-10-31T01:53:29.937Z CLOSE host=36.92.56.213 port=49346 fd=4 time=20.019 bytes=27
...
2020-03-13 04:44:57
45.55.231.94 attackspambots
2020-03-12T20:01:02.176432abusebot-2.cloudsearch.cf sshd[9199]: Invalid user user0 from 45.55.231.94 port 56180
2020-03-12T20:01:02.184215abusebot-2.cloudsearch.cf sshd[9199]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.55.231.94
2020-03-12T20:01:02.176432abusebot-2.cloudsearch.cf sshd[9199]: Invalid user user0 from 45.55.231.94 port 56180
2020-03-12T20:01:04.304026abusebot-2.cloudsearch.cf sshd[9199]: Failed password for invalid user user0 from 45.55.231.94 port 56180 ssh2
2020-03-12T20:06:08.966540abusebot-2.cloudsearch.cf sshd[9529]: Invalid user openerp from 45.55.231.94 port 44022
2020-03-12T20:06:08.976493abusebot-2.cloudsearch.cf sshd[9529]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.55.231.94
2020-03-12T20:06:08.966540abusebot-2.cloudsearch.cf sshd[9529]: Invalid user openerp from 45.55.231.94 port 44022
2020-03-12T20:06:10.765760abusebot-2.cloudsearch.cf sshd[9529]: Failed password f
...
2020-03-13 04:38:44
175.173.23.116 attack
firewall-block, port(s): 23/tcp
2020-03-13 04:44:20
222.186.31.204 attack
Mar 12 21:19:16 plex sshd[21929]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.31.204  user=root
Mar 12 21:19:18 plex sshd[21929]: Failed password for root from 222.186.31.204 port 45475 ssh2
2020-03-13 04:35:39
185.36.81.23 attack
Mar 12 21:18:14 srv01 postfix/smtpd\[20405\]: warning: unknown\[185.36.81.23\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Mar 12 21:23:01 srv01 postfix/smtpd\[5880\]: warning: unknown\[185.36.81.23\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Mar 12 21:24:23 srv01 postfix/smtpd\[5880\]: warning: unknown\[185.36.81.23\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Mar 12 21:24:53 srv01 postfix/smtpd\[23466\]: warning: unknown\[185.36.81.23\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Mar 12 21:26:17 srv01 postfix/smtpd\[5880\]: warning: unknown\[185.36.81.23\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-03-13 04:32:13
41.230.122.248 attackspam
2020-02-18T23:25:05.828Z CLOSE host=41.230.122.248 port=6205 fd=4 time=20.012 bytes=27
...
2020-03-13 04:31:31
116.117.157.69 attackbots
$f2bV_matches_ltvn
2020-03-13 04:42:58
41.221.146.138 attackbots
2020-01-10T22:15:46.776Z CLOSE host=41.221.146.138 port=45576 fd=4 time=20.020 bytes=25
...
2020-03-13 04:32:54
51.38.71.36 attackbots
SSH Brute-Force reported by Fail2Ban
2020-03-13 04:41:48
206.189.148.203 attackspambots
SSH authentication failure x 6 reported by Fail2Ban
...
2020-03-13 04:45:34
220.182.9.74 attackspambots
suspicious action Thu, 12 Mar 2020 09:28:18 -0300
2020-03-13 04:18:50
222.186.175.220 attackbotsspam
Mar 12 21:27:34 MainVPS sshd[2242]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.220  user=root
Mar 12 21:27:36 MainVPS sshd[2242]: Failed password for root from 222.186.175.220 port 60182 ssh2
Mar 12 21:27:49 MainVPS sshd[2242]: error: maximum authentication attempts exceeded for root from 222.186.175.220 port 60182 ssh2 [preauth]
Mar 12 21:27:34 MainVPS sshd[2242]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.220  user=root
Mar 12 21:27:36 MainVPS sshd[2242]: Failed password for root from 222.186.175.220 port 60182 ssh2
Mar 12 21:27:49 MainVPS sshd[2242]: error: maximum authentication attempts exceeded for root from 222.186.175.220 port 60182 ssh2 [preauth]
Mar 12 21:27:52 MainVPS sshd[3168]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.220  user=root
Mar 12 21:27:54 MainVPS sshd[3168]: Failed password for root from 222.186.175.220 port 61218 ss
2020-03-13 04:33:54
178.171.102.142 attackbotsspam
Chat Spam
2020-03-13 04:38:09

Recently Reported IPs

13.244.169.18 13.246.35.115 13.246.0.137 13.248.132.76
13.248.141.25 13.248.136.15 13.248.141.89 13.248.155.14
13.248.155.183 13.248.155.91 13.248.155.34 13.248.159.25
13.248.159.201 13.248.161.93 13.248.162.114 13.248.162.186
13.248.164.50 13.248.163.94 13.248.165.164 13.248.165.251