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

;; QUESTION SECTION:
;13.234.221.49.			IN	A

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

;; Query time: 63 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 27 12:01:42 CST 2022
;; MSG SIZE  rcvd: 106
Host info
49.221.234.13.in-addr.arpa domain name pointer ec2-13-234-221-49.ap-south-1.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
49.221.234.13.in-addr.arpa	name = ec2-13-234-221-49.ap-south-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
147.12.145.29 attackspam
Unauthorized connection attempt detected from IP address 147.12.145.29 to port 5555 [J]
2020-01-26 02:39:11
83.3.93.154 attackspam
Jan 25 18:42:36 MK-Soft-Root1 sshd[29717]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=83.3.93.154 
Jan 25 18:42:39 MK-Soft-Root1 sshd[29717]: Failed password for invalid user minecraft from 83.3.93.154 port 40324 ssh2
...
2020-01-26 02:45:31
61.143.152.3 attackspambots
Unauthorized connection attempt detected from IP address 61.143.152.3 to port 1433 [J]
2020-01-26 02:21:25
31.168.30.65 attack
Unauthorized connection attempt detected from IP address 31.168.30.65 to port 23 [J]
2020-01-26 02:26:37
70.15.249.67 attack
Unauthorized connection attempt detected from IP address 70.15.249.67 to port 23 [J]
2020-01-26 02:46:46
109.227.200.47 attack
Unauthorized connection attempt detected from IP address 109.227.200.47 to port 23 [J]
2020-01-26 02:41:57
1.52.237.19 attackspam
Unauthorized connection attempt detected from IP address 1.52.237.19 to port 23 [J]
2020-01-26 02:51:06
176.124.138.105 attackbots
Unauthorized connection attempt detected from IP address 176.124.138.105 to port 80 [J]
2020-01-26 02:36:15
210.61.41.87 attackbotsspam
Unauthorized connection attempt detected from IP address 210.61.41.87 to port 5555 [J]
2020-01-26 02:53:19
123.138.77.53 attackbots
Unauthorized connection attempt detected from IP address 123.138.77.53 to port 8118 [J]
2020-01-26 03:01:17
186.225.140.8 attackbots
Unauthorized connection attempt detected from IP address 186.225.140.8 to port 2220 [J]
2020-01-26 02:35:23
191.255.158.89 attackbotsspam
Unauthorized connection attempt detected from IP address 191.255.158.89 to port 23 [J]
2020-01-26 02:55:44
220.132.4.200 attackspam
Unauthorized connection attempt detected from IP address 220.132.4.200 to port 4567 [J]
2020-01-26 02:29:23
201.184.40.61 attackbots
Unauthorized connection attempt detected from IP address 201.184.40.61 to port 2323 [J]
2020-01-26 02:54:14
185.74.4.106 attack
Unauthorized connection attempt detected from IP address 185.74.4.106 to port 1433 [J]
2020-01-26 02:57:08

Recently Reported IPs

13.234.212.166 13.234.217.118 13.234.217.42 13.234.224.113
13.234.214.53 13.234.226.153 13.234.226.209 13.234.226.93
13.234.227.180 13.234.228.245 13.234.23.37 13.234.229.0
13.234.230.186 13.234.23.156 13.234.238.200 13.234.24.68
13.234.235.223 13.234.240.159 13.234.234.102 13.234.239.126