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: United States

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

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

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

;; Query time: 25 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jul 27 17:15:23 CST 2020
;; MSG SIZE  rcvd: 117
Host info
107.72.208.13.in-addr.arpa domain name pointer ec2-13-208-72-107.ap-northeast-3.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
107.72.208.13.in-addr.arpa	name = ec2-13-208-72-107.ap-northeast-3.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
1.53.137.12 attack
IP was detected trying to Brute-Force SSH, FTP, Web Apps or Hacking.
2019-12-05 03:15:50
2.238.193.59 attackspambots
SSH authentication failure x 6 reported by Fail2Ban
...
2019-12-05 03:04:51
193.70.88.213 attackbotsspam
2019-12-04T14:04:59.437062abusebot-3.cloudsearch.cf sshd\[16193\]: Invalid user grenz from 193.70.88.213 port 34478
2019-12-05 03:02:48
51.38.186.47 attackspam
Dec  4 19:26:30 vps666546 sshd\[21144\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.38.186.47  user=root
Dec  4 19:26:31 vps666546 sshd\[21144\]: Failed password for root from 51.38.186.47 port 58030 ssh2
Dec  4 19:32:54 vps666546 sshd\[21472\]: Invalid user meldia from 51.38.186.47 port 40662
Dec  4 19:32:54 vps666546 sshd\[21472\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.38.186.47
Dec  4 19:32:56 vps666546 sshd\[21472\]: Failed password for invalid user meldia from 51.38.186.47 port 40662 ssh2
...
2019-12-05 02:50:59
148.70.246.130 attackspambots
[ssh] SSH attack
2019-12-05 03:01:00
54.38.36.244 attackbots
54.38.36.244 - - \[04/Dec/2019:13:27:24 +0100\] "POST /wp-login.php HTTP/1.0" 200 6655 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
54.38.36.244 - - \[04/Dec/2019:13:27:26 +0100\] "POST /wp-login.php HTTP/1.0" 200 6493 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
54.38.36.244 - - \[04/Dec/2019:13:27:28 +0100\] "POST /wp-login.php HTTP/1.0" 200 6492 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
2019-12-05 02:55:29
165.227.69.39 attack
20 attempts against mh-ssh on cloud.magehost.pro
2019-12-05 03:27:16
118.32.223.14 attackbotsspam
SSH Bruteforce attempt
2019-12-05 02:57:01
182.254.135.14 attackspam
Dec  4 15:27:01 vmanager6029 sshd\[10516\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.254.135.14  user=lp
Dec  4 15:27:03 vmanager6029 sshd\[10516\]: Failed password for lp from 182.254.135.14 port 42456 ssh2
Dec  4 15:35:06 vmanager6029 sshd\[10727\]: Invalid user wv from 182.254.135.14 port 50108
Dec  4 15:35:06 vmanager6029 sshd\[10727\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.254.135.14
2019-12-05 03:00:04
202.215.36.230 attack
Dec  4 20:12:07 markkoudstaal sshd[522]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.215.36.230
Dec  4 20:12:08 markkoudstaal sshd[522]: Failed password for invalid user oyao from 202.215.36.230 port 55950 ssh2
Dec  4 20:18:57 markkoudstaal sshd[1245]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.215.36.230
2019-12-05 03:26:29
111.231.66.135 attack
Dec  4 19:14:25 server sshd\[30518\]: Invalid user lindseth from 111.231.66.135
Dec  4 19:14:25 server sshd\[30518\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.231.66.135 
Dec  4 19:14:27 server sshd\[30518\]: Failed password for invalid user lindseth from 111.231.66.135 port 58124 ssh2
Dec  4 19:25:28 server sshd\[1544\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.231.66.135  user=root
Dec  4 19:25:31 server sshd\[1544\]: Failed password for root from 111.231.66.135 port 38206 ssh2
...
2019-12-05 03:21:08
89.248.174.3 attack
ET DROP Dshield Block Listed Source group 1 - port: 4500 proto: TCP cat: Misc Attack
2019-12-05 02:53:12
181.44.68.66 attackspam
2019-12-04T19:03:05.522648abusebot-5.cloudsearch.cf sshd\[31225\]: Invalid user lee from 181.44.68.66 port 48875
2019-12-05 03:20:13
113.174.35.55 attackspam
Automatic report - Port Scan Attack
2019-12-05 03:02:00
200.149.231.50 attackbots
Dec  4 18:58:03 h2177944 sshd\[22890\]: Invalid user vyse from 200.149.231.50 port 46926
Dec  4 18:58:03 h2177944 sshd\[22890\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.149.231.50
Dec  4 18:58:05 h2177944 sshd\[22890\]: Failed password for invalid user vyse from 200.149.231.50 port 46926 ssh2
Dec  4 19:04:53 h2177944 sshd\[23539\]: Invalid user kaspon from 200.149.231.50 port 58146
...
2019-12-05 02:54:48

Recently Reported IPs

225.195.81.225 220.134.171.82 106.54.200.220 149.3.124.113
78.162.121.115 1.55.228.98 238.78.53.11 210.211.118.225
25.89.149.139 31.142.3.72 148.72.158.112 177.118.146.104
114.67.254.244 172.125.142.199 103.90.203.182 202.65.218.250
113.184.71.35 139.59.87.130 5.25.137.102 50.103.5.45