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

;; QUESTION SECTION:
;13.244.125.100.			IN	A

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

;; Query time: 13 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 10 04:29:31 CST 2025
;; MSG SIZE  rcvd: 107
Host info
100.125.244.13.in-addr.arpa domain name pointer ec2-13-244-125-100.af-south-1.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
100.125.244.13.in-addr.arpa	name = ec2-13-244-125-100.af-south-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
200.89.174.176 attackspam
Nov 17 05:52:08 vpn01 sshd[28424]: Failed password for root from 200.89.174.176 port 44666 ssh2
...
2019-11-17 13:50:15
183.164.226.156 attackspambots
badbot
2019-11-17 14:14:01
67.211.209.151 attack
67.211.209.151 was recorded 5 times by 5 hosts attempting to connect to the following ports: 3390,3389. Incident counter (4h, 24h, all-time): 5, 10, 10
2019-11-17 13:44:43
104.131.189.116 attackbotsspam
Nov 17 01:53:18 firewall sshd[8038]: Failed password for news from 104.131.189.116 port 34990 ssh2
Nov 17 01:57:10 firewall sshd[8133]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.131.189.116  user=root
Nov 17 01:57:12 firewall sshd[8133]: Failed password for root from 104.131.189.116 port 45328 ssh2
...
2019-11-17 14:01:03
190.136.174.171 attackbots
[Sun Nov 17 02:05:53.059016 2019] [:error] [pid 150796] [client 190.136.174.171:61000] [client 190.136.174.171] ModSecurity: Access denied with code 403 (phase 2). Operator GE matched 5 at TX:anomaly_score. [file "/usr/share/modsecurity-crs/rules/REQUEST-949-BLOCKING-EVALUATION.conf"] [line "91"] [id "949110"] [msg "Inbound Anomaly Score Exceeded (Total Score: 8)"] [severity "CRITICAL"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-generic"] [hostname "ws24vmsma01.ufn.edu.br"] [uri "/"] [unique_id "XdDVMZfCSfBi0H2qEVSw4wAAAAE"]
...
2019-11-17 13:41:46
115.159.237.89 attackbotsspam
Nov 17 06:53:32 srv-ubuntu-dev3 sshd[80027]: Invalid user kenzo from 115.159.237.89
Nov 17 06:53:32 srv-ubuntu-dev3 sshd[80027]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.159.237.89
Nov 17 06:53:32 srv-ubuntu-dev3 sshd[80027]: Invalid user kenzo from 115.159.237.89
Nov 17 06:53:34 srv-ubuntu-dev3 sshd[80027]: Failed password for invalid user kenzo from 115.159.237.89 port 60298 ssh2
Nov 17 06:58:22 srv-ubuntu-dev3 sshd[80350]: Invalid user janca from 115.159.237.89
Nov 17 06:58:22 srv-ubuntu-dev3 sshd[80350]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.159.237.89
Nov 17 06:58:22 srv-ubuntu-dev3 sshd[80350]: Invalid user janca from 115.159.237.89
Nov 17 06:58:24 srv-ubuntu-dev3 sshd[80350]: Failed password for invalid user janca from 115.159.237.89 port 40110 ssh2
Nov 17 07:03:07 srv-ubuntu-dev3 sshd[80710]: Invalid user nfs from 115.159.237.89
...
2019-11-17 14:12:02
107.182.187.34 attackspambots
Automatic report - Banned IP Access
2019-11-17 13:53:53
66.249.65.218 attackspam
Automatic report - Banned IP Access
2019-11-17 14:11:05
110.246.11.204 attackbots
badbot
2019-11-17 13:57:45
80.82.65.40 attack
80.82.65.40 was recorded 5 times by 1 hosts attempting to connect to the following ports: 15616,15615,15605,15612,15620. Incident counter (4h, 24h, all-time): 5, 770, 8106
2019-11-17 13:41:08
35.199.154.128 attackspam
Nov 17 06:59:50 MK-Soft-VM3 sshd[16347]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=35.199.154.128 
Nov 17 06:59:52 MK-Soft-VM3 sshd[16347]: Failed password for invalid user chynena from 35.199.154.128 port 59340 ssh2
...
2019-11-17 14:23:11
185.143.223.137 attackbotsspam
185.143.223.137 was recorded 5 times by 3 hosts attempting to connect to the following ports: 34491,34702,34918,34879,34564. Incident counter (4h, 24h, all-time): 5, 69, 178
2019-11-17 14:14:23
2408:84e4:446:308d:38dd:6529:de48:c68d attackspambots
badbot
2019-11-17 13:41:29
80.211.30.166 attack
Nov 17 06:58:16 vmanager6029 sshd\[30374\]: Invalid user dilly from 80.211.30.166 port 60810
Nov 17 06:58:16 vmanager6029 sshd\[30374\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.211.30.166
Nov 17 06:58:18 vmanager6029 sshd\[30374\]: Failed password for invalid user dilly from 80.211.30.166 port 60810 ssh2
2019-11-17 14:04:37
185.76.34.87 attackspam
Invalid user ts3user from 185.76.34.87 port 52932
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.76.34.87
Failed password for invalid user ts3user from 185.76.34.87 port 52932 ssh2
Invalid user guest from 185.76.34.87 port 60976
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.76.34.87
2019-11-17 14:12:31

Recently Reported IPs

132.20.79.141 147.33.33.54 241.218.20.199 196.61.24.240
198.101.117.227 6.148.170.97 137.9.187.195 243.236.251.112
218.195.89.148 204.191.249.36 206.87.252.61 142.30.169.9
72.101.249.180 140.219.91.147 122.224.47.215 107.69.36.99
249.91.191.134 240.214.73.145 73.211.175.38 172.122.178.110