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

;; QUESTION SECTION:
;13.211.214.49.			IN	A

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

;; Query time: 21 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 27 17:02:01 CST 2022
;; MSG SIZE  rcvd: 106
Host info
49.214.211.13.in-addr.arpa domain name pointer ec2-13-211-214-49.ap-southeast-2.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
49.214.211.13.in-addr.arpa	name = ec2-13-211-214-49.ap-southeast-2.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
139.162.161.163 attackspambots
Honeypot hit.
2019-11-09 16:09:53
60.176.150.138 attack
Nov  9 09:07:09 dedicated sshd[17236]: Invalid user nemesis123 from 60.176.150.138 port 58300
Nov  9 09:07:09 dedicated sshd[17236]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=60.176.150.138 
Nov  9 09:07:09 dedicated sshd[17236]: Invalid user nemesis123 from 60.176.150.138 port 58300
Nov  9 09:07:11 dedicated sshd[17236]: Failed password for invalid user nemesis123 from 60.176.150.138 port 58300 ssh2
Nov  9 09:10:54 dedicated sshd[17823]: Invalid user garbo from 60.176.150.138 port 24295
2019-11-09 16:14:43
200.169.223.98 attackbots
2019-11-09T08:03:52.933443abusebot-5.cloudsearch.cf sshd\[10244\]: Invalid user oq from 200.169.223.98 port 38362
2019-11-09 16:19:47
83.110.200.239 attackbotsspam
Caught in portsentry honeypot
2019-11-09 16:13:22
209.17.96.34 attackspambots
Connection by 209.17.96.34 on port: 3000 got caught by honeypot at 11/9/2019 5:27:52 AM
2019-11-09 16:11:28
184.30.210.217 attackspam
11/09/2019-08:52:44.467032 184.30.210.217 Protocol: 6 SURICATA TLS invalid record/traffic
2019-11-09 16:14:04
200.54.255.253 attackbots
Nov  9 07:23:35 serwer sshd\[13418\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.54.255.253  user=root
Nov  9 07:23:36 serwer sshd\[13418\]: Failed password for root from 200.54.255.253 port 45934 ssh2
Nov  9 07:28:02 serwer sshd\[13853\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.54.255.253  user=admin
...
2019-11-09 16:02:46
80.91.176.139 attackspam
$f2bV_matches
2019-11-09 16:32:23
167.250.29.203 attackspambots
Automatic report - Port Scan Attack
2019-11-09 16:15:03
148.235.57.184 attack
Nov  9 08:26:09 ArkNodeAT sshd\[15284\]: Invalid user ftp from 148.235.57.184
Nov  9 08:26:09 ArkNodeAT sshd\[15284\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.235.57.184
Nov  9 08:26:10 ArkNodeAT sshd\[15284\]: Failed password for invalid user ftp from 148.235.57.184 port 33544 ssh2
2019-11-09 16:25:34
157.245.180.87 attack
2019-11-09T06:27:02Z - RDP login failed multiple times. (157.245.180.87)
2019-11-09 16:40:37
125.124.143.62 attack
Nov  9 09:05:18 dedicated sshd[16946]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.124.143.62  user=root
Nov  9 09:05:19 dedicated sshd[16946]: Failed password for root from 125.124.143.62 port 54590 ssh2
2019-11-09 16:07:32
78.122.160.118 attack
5x Failed Password
2019-11-09 16:06:26
182.50.130.8 attack
Automatic report - XMLRPC Attack
2019-11-09 16:16:15
82.221.105.7 attack
82.221.105.7 was recorded 5 times by 4 hosts attempting to connect to the following ports: 3388,32400,7547,21379,5560. Incident counter (4h, 24h, all-time): 5, 25, 109
2019-11-09 16:30:21

Recently Reported IPs

13.211.239.8 13.211.234.15 13.211.79.139 13.211.33.93
13.212.1.104 13.211.33.250 13.212.1.122 13.211.59.50
13.212.1.14 13.211.62.249 13.212.1.117 13.212.1.139
13.211.91.94 13.211.81.69 13.212.1.17 13.212.1.190
13.212.1.198 13.212.1.236 13.212.1.250 13.212.1.156