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: Cape Town

Region: Western Cape

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

;; QUESTION SECTION:
;13.244.7.197.			IN	A

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

;; Query time: 36 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 09 19:36:28 CST 2025
;; MSG SIZE  rcvd: 105
Host info
197.7.244.13.in-addr.arpa domain name pointer ec2-13-244-7-197.af-south-1.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
197.7.244.13.in-addr.arpa	name = ec2-13-244-7-197.af-south-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
185.242.5.46 attackbots
 TCP (SYN) 185.242.5.46:57239 -> port 53, len 44
2020-07-01 16:50:37
36.111.184.80 attack
$f2bV_matches
2020-07-01 16:23:27
106.75.119.202 attack
Invalid user rena from 106.75.119.202 port 35340
2020-07-01 16:45:15
181.168.137.94 attack
Zyxel NAS devices command injection attempt
Source IP address: 181.168.137.94 (94-137-168-181.fibertel.com.ar)
2020-07-01 16:05:06
160.20.205.8 attackspam
Icarus honeypot on github
2020-07-01 16:18:32
212.64.29.136 attack
Jun 30 11:19:23 ns382633 sshd\[13377\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.64.29.136  user=root
Jun 30 11:19:26 ns382633 sshd\[13377\]: Failed password for root from 212.64.29.136 port 37848 ssh2
Jun 30 11:29:16 ns382633 sshd\[15291\]: Invalid user test1 from 212.64.29.136 port 54334
Jun 30 11:29:16 ns382633 sshd\[15291\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.64.29.136
Jun 30 11:29:18 ns382633 sshd\[15291\]: Failed password for invalid user test1 from 212.64.29.136 port 54334 ssh2
2020-07-01 16:37:06
45.145.66.112 attackspam
scans 3 times in preceeding hours on the ports (in chronological order) 3306 3013 3168
2020-07-01 16:45:58
91.185.237.206 attack
 TCP (SYN) 91.185.237.206:31234 -> port 23, len 44
2020-07-01 16:00:43
45.162.216.10 attack
Multiple SSH authentication failures from 45.162.216.10
2020-07-01 16:51:48
139.59.230.44 attack
Invalid user usuario from 139.59.230.44 port 41600
2020-07-01 16:02:11
114.33.159.252 attack
unauthorized connection attempt
2020-07-01 16:28:31
139.59.45.45 attackbotsspam
SCAN: Host Sweep CloudCIX Reconnaissance Scan Detected, PTR: PTR record not found
2020-07-01 16:05:59
111.229.204.204 attackspambots
Unauthorized connection attempt detected from IP address 111.229.204.204 to port 5818
2020-07-01 16:41:14
103.205.26.147 attack
2020-06-30T23:59:13.128826hostname sshd[27862]: Invalid user smb from 103.205.26.147 port 39670
2020-06-30T23:59:14.986357hostname sshd[27862]: Failed password for invalid user smb from 103.205.26.147 port 39670 ssh2
2020-07-01T00:01:27.105060hostname sshd[28904]: Invalid user pd from 103.205.26.147 port 58444
...
2020-07-01 16:26:22
189.12.72.118 attackspambots
unauthorized connection attempt
2020-07-01 16:29:07

Recently Reported IPs

185.25.30.35 128.142.227.150 52.48.158.111 143.78.221.101
173.210.144.139 46.219.108.2 139.114.92.122 145.15.93.191
249.211.152.141 97.206.124.42 162.221.253.64 230.62.203.182
51.87.186.201 30.135.210.237 81.10.37.193 160.33.111.173
168.225.12.188 73.19.20.218 36.191.251.95 50.99.52.92