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

;; QUESTION SECTION:
;13.229.134.152.			IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 27 17:05:58 CST 2022
;; MSG SIZE  rcvd: 107
Host info
152.134.229.13.in-addr.arpa domain name pointer ec2-13-229-134-152.ap-southeast-1.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
152.134.229.13.in-addr.arpa	name = ec2-13-229-134-152.ap-southeast-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
85.248.227.163 attack
02/17/2020-05:57:34.181863 85.248.227.163 Protocol: 6 ET TOR Known Tor Exit Node Traffic group 83
2020-02-17 16:32:13
180.241.47.190 attackspam
20/2/16@23:57:30: FAIL: Alarm-Network address from=180.241.47.190
...
2020-02-17 16:37:11
84.228.102.23 attackbotsspam
Automatic report - Port Scan Attack
2020-02-17 16:41:34
141.98.80.71 attackspambots
Feb 17 01:51:55 firewall sshd[4421]: Invalid user admin from 141.98.80.71
Feb 17 01:51:57 firewall sshd[4421]: Failed password for invalid user admin from 141.98.80.71 port 60178 ssh2
Feb 17 01:57:36 firewall sshd[4633]: Invalid user admin from 141.98.80.71
...
2020-02-17 16:26:55
173.194.73.27 attackbotsspam
SSH login attempts.
2020-02-17 16:09:59
123.134.121.41 attackbots
SSH login attempts.
2020-02-17 16:13:11
182.253.235.178 attackspambots
1581915465 - 02/17/2020 05:57:45 Host: 182.253.235.178/182.253.235.178 Port: 445 TCP Blocked
2020-02-17 16:15:18
106.12.5.77 attack
$f2bV_matches
2020-02-17 16:19:11
52.41.25.158 attackspam
SSH login attempts.
2020-02-17 16:52:03
70.226.21.36 attack
SSH login attempts.
2020-02-17 16:28:23
149.56.45.87 attackbotsspam
Feb 17 05:57:47 v22019058497090703 sshd[8377]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=149.56.45.87
Feb 17 05:57:48 v22019058497090703 sshd[8377]: Failed password for invalid user testuser from 149.56.45.87 port 43422 ssh2
...
2020-02-17 16:10:49
182.74.114.30 attack
1581915439 - 02/17/2020 05:57:19 Host: 182.74.114.30/182.74.114.30 Port: 445 TCP Blocked
2020-02-17 16:49:49
156.96.116.53 spam
[2020/02/17 16:00:56] [156.96.116.53:2101-0] User default@luxnetcorp.com.tw AUTH fails.
[2020/02/17 16:01:58] [156.96.116.53:2100-0] User default@luxnetcorp.com.tw AUTH fails.
[2020/02/17 16:01:59] [156.96.116.53:2098-0] User default@luxnetcorp.com.tw AUTH fails.
[2020/02/17 16:02:00] [156.96.116.53:2103-0] User default@luxnetcorp.com.tw AUTH fails.
[2020/02/17 16:02:02] [156.96.116.53:2098-0] User default@luxnetcorp.com.tw AUTH fails.
2020-02-17 16:44:57
222.186.175.151 attack
$f2bV_matches
2020-02-17 16:28:49
180.241.46.162 attackspam
20/2/17@00:58:07: FAIL: Alarm-Network address from=180.241.46.162
20/2/17@00:58:07: FAIL: Alarm-Network address from=180.241.46.162
...
2020-02-17 16:34:40

Recently Reported IPs

13.229.132.142 13.229.131.229 13.229.134.175 13.229.132.180
13.229.134.197 13.229.135.105 13.229.134.92 13.229.134.67
13.229.134.210 13.229.135.180 13.229.135.7 13.229.135.89
13.229.136.203 13.229.135.235 13.229.136.27 13.229.136.8
13.229.136.59 13.229.136.47 13.229.157.145 13.229.157.132