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: Ashburn

Region: Virginia

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

;; QUESTION SECTION:
;54.152.48.12.			IN	A

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

;; Query time: 11 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 13 10:29:55 CST 2025
;; MSG SIZE  rcvd: 105
Host info
12.48.152.54.in-addr.arpa domain name pointer ec2-54-152-48-12.compute-1.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
12.48.152.54.in-addr.arpa	name = ec2-54-152-48-12.compute-1.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
134.175.28.156 attackspam
Brute force SMTP login attempted.
...
2019-08-10 06:25:05
39.82.165.124 attack
Aug  9 15:39:54 spiceship sshd\[43705\]: Invalid user admin from 39.82.165.124
Aug  9 15:39:54 spiceship sshd\[43705\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=39.82.165.124
...
2019-08-10 06:02:58
184.105.247.216 attack
firewall-block, port(s): 5900/tcp
2019-08-10 06:28:55
179.214.189.101 attackbotsspam
Aug 10 00:28:09 server sshd\[31542\]: Invalid user blog from 179.214.189.101 port 48020
Aug 10 00:28:09 server sshd\[31542\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.214.189.101
Aug 10 00:28:10 server sshd\[31542\]: Failed password for invalid user blog from 179.214.189.101 port 48020 ssh2
Aug 10 00:33:53 server sshd\[5884\]: Invalid user service from 179.214.189.101 port 40362
Aug 10 00:33:53 server sshd\[5884\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.214.189.101
2019-08-10 05:46:35
124.65.140.42 attack
Reported by AbuseIPDB proxy server.
2019-08-10 06:23:38
198.108.67.127 attackspambots
firewall-block, port(s): 443/tcp
2019-08-10 06:05:09
134.209.116.148 attackbots
Brute force SMTP login attempted.
...
2019-08-10 05:58:08
134.209.10.41 attackspambots
Brute force SMTP login attempted.
...
2019-08-10 06:03:34
198.108.67.57 attackspam
firewall-block, port(s): 95/tcp
2019-08-10 06:11:04
134.175.59.235 attack
Triggered by Fail2Ban at Vostok web server
2019-08-10 06:14:53
190.144.3.138 attackspambots
(sshd) Failed SSH login from 190.144.3.138 (-): 5 in the last 3600 secs
2019-08-10 06:11:28
167.250.90.211 attack
Autoban   167.250.90.211 AUTH/CONNECT
2019-08-10 06:13:37
202.67.46.232 attack
Attack, like DDOS, Brute-Force, Port Scan, Hack, etc.
2019-08-10 05:46:04
185.176.27.246 attack
08/09/2019-18:03:59.897783 185.176.27.246 Protocol: 6 ET SCAN NMAP -sS window 1024
2019-08-10 06:18:41
133.242.17.9 attackspambots
Aug  9 19:31:38 ks10 sshd[18307]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=133.242.17.9 
Aug  9 19:31:40 ks10 sshd[18307]: Failed password for invalid user edy from 133.242.17.9 port 36320 ssh2
...
2019-08-10 05:51:33

Recently Reported IPs

74.47.194.9 4.99.133.96 120.110.127.79 66.11.61.90
198.97.155.177 181.80.183.122 92.85.46.135 104.144.156.211
135.50.244.69 131.38.113.201 18.50.245.213 200.34.154.249
215.147.46.102 122.176.90.183 85.197.0.144 69.221.134.101
254.233.56.109 89.79.184.248 92.186.131.150 247.8.196.227