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

;; QUESTION SECTION:
;13.229.145.252.			IN	A

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

;; Query time: 16 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 27 11:54:31 CST 2022
;; MSG SIZE  rcvd: 107
Host info
252.145.229.13.in-addr.arpa domain name pointer ec2-13-229-145-252.ap-southeast-1.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
252.145.229.13.in-addr.arpa	name = ec2-13-229-145-252.ap-southeast-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
152.232.212.98 attackspam
[Tue Jan 21 11:37:31 2020] Failed password for r.r from 152.232.212.98 port 41250 ssh2
[Tue Jan 21 11:42:46 2020] Failed password for r.r from 152.232.212.98 port 57308 ssh2
[Tue Jan 21 11:44:40 2020] Failed password for invalid user soporte from 152.232.212.98 port 35124 ssh2
[Tue Jan 21 11:46:29 2020] Failed password for invalid user teste01 from 152.232.212.98 port 41175 ssh2


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=152.232.212.98
2020-01-21 20:20:26
89.46.238.146 attack
Unauthorized connection attempt detected from IP address 89.46.238.146 to port 80 [J]
2020-01-21 20:31:38
51.15.1.127 attackspambots
Unauthorized connection attempt detected from IP address 51.15.1.127 to port 8080 [J]
2020-01-21 20:33:10
138.255.186.237 attackspam
Unauthorized connection attempt detected from IP address 138.255.186.237 to port 8080 [J]
2020-01-21 20:48:49
118.103.253.145 attack
Unauthorized connection attempt detected from IP address 118.103.253.145 to port 80 [J]
2020-01-21 20:24:54
110.141.236.179 attackspam
Unauthorized connection attempt detected from IP address 110.141.236.179 to port 23 [J]
2020-01-21 20:27:55
170.130.187.30 attackbotsspam
Unauthorized connection attempt detected from IP address 170.130.187.30 to port 8444 [J]
2020-01-21 20:46:07
180.183.250.13 attackbotsspam
20/1/21@02:38:39: FAIL: Alarm-Network address from=180.183.250.13
20/1/21@02:38:40: FAIL: Alarm-Network address from=180.183.250.13
...
2020-01-21 20:18:04
188.170.121.218 attackspam
Unauthorized connection attempt detected from IP address 188.170.121.218 to port 23 [J]
2020-01-21 20:17:40
217.58.61.49 attackspam
Unauthorized connection attempt detected from IP address 217.58.61.49 to port 80 [J]
2020-01-21 20:39:59
147.158.209.210 attackbots
Unauthorized connection attempt detected from IP address 147.158.209.210 to port 8000 [J]
2020-01-21 20:21:45
212.3.187.215 attack
Unauthorized connection attempt detected from IP address 212.3.187.215 to port 23 [J]
2020-01-21 20:41:34
151.76.178.229 attackspambots
Unauthorized connection attempt detected from IP address 151.76.178.229 to port 80 [J]
2020-01-21 20:47:03
196.52.43.128 attackbots
Unauthorized connection attempt detected from IP address 196.52.43.128 to port 990 [J]
2020-01-21 20:15:30
119.246.88.21 attack
Unauthorized connection attempt detected from IP address 119.246.88.21 to port 5555 [J]
2020-01-21 20:24:21

Recently Reported IPs

13.229.146.222 13.229.147.240 13.229.146.60 13.229.146.72
13.229.148.134 13.229.148.156 13.229.148.176 13.229.148.164
13.229.148.255 13.229.148.22 13.229.148.230 13.229.148.44
13.229.148.16 13.229.148.76 13.229.148.86 13.229.149.112
13.229.150.130 13.229.150.165 13.229.149.255 13.229.150.230