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

;; QUESTION SECTION:
;13.52.219.54.			IN	A

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

;; Query time: 27 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 27 12:06:35 CST 2022
;; MSG SIZE  rcvd: 105
Host info
54.219.52.13.in-addr.arpa domain name pointer ec2-13-52-219-54.us-west-1.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
54.219.52.13.in-addr.arpa	name = ec2-13-52-219-54.us-west-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
77.232.128.87 attackbotsspam
SSH Brute-Forcing (server2)
2020-03-12 03:10:42
185.47.65.30 attackspam
k+ssh-bruteforce
2020-03-12 03:12:42
190.186.22.187 attack
suspicious action Wed, 11 Mar 2020 16:19:36 -0300
2020-03-12 03:28:39
223.247.129.84 attackspam
Mar 11 20:05:22 ns382633 sshd\[3281\]: Invalid user sundapeng from 223.247.129.84 port 42552
Mar 11 20:05:22 ns382633 sshd\[3281\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=223.247.129.84
Mar 11 20:05:24 ns382633 sshd\[3281\]: Failed password for invalid user sundapeng from 223.247.129.84 port 42552 ssh2
Mar 11 20:19:17 ns382633 sshd\[5769\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=223.247.129.84  user=root
Mar 11 20:19:18 ns382633 sshd\[5769\]: Failed password for root from 223.247.129.84 port 39766 ssh2
2020-03-12 03:41:15
181.49.132.18 attackbotsspam
Mar 12 00:13:32 gw1 sshd[11548]: Failed password for root from 181.49.132.18 port 49538 ssh2
...
2020-03-12 03:24:57
222.186.30.187 attackbotsspam
Mar 11 20:41:09 vps691689 sshd[30044]: Failed password for root from 222.186.30.187 port 14675 ssh2
Mar 11 20:41:11 vps691689 sshd[30044]: Failed password for root from 222.186.30.187 port 14675 ssh2
Mar 11 20:41:13 vps691689 sshd[30044]: Failed password for root from 222.186.30.187 port 14675 ssh2
...
2020-03-12 03:41:50
167.71.84.7 attackbotsspam
suspicious action Wed, 11 Mar 2020 16:19:22 -0300
2020-03-12 03:40:12
36.85.232.128 attackbots
SSH bruteforce more then 50 syn to 22 port per 10 seconds.
2020-03-12 03:33:36
122.226.238.10 attack
Honeypot attack, port: 445, PTR: PTR record not found
2020-03-12 02:58:17
188.215.42.47 attack
Mar 11 11:40:17 jane sshd[11856]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.215.42.47 
Mar 11 11:40:19 jane sshd[11856]: Failed password for invalid user  from 188.215.42.47 port 27017 ssh2
...
2020-03-12 03:09:54
139.199.34.54 attackbots
Automatic report - SSH Brute-Force Attack
2020-03-12 03:37:11
148.70.24.20 attackspam
Invalid user administrator from 148.70.24.20 port 39976
2020-03-12 03:07:30
218.92.0.190 attackbotsspam
03/11/2020-15:22:05.712077 218.92.0.190 Protocol: 6 ET SCAN Potential SSH Scan
2020-03-12 03:22:41
83.97.20.49 attack
firewall-block, port(s): 444/tcp, 1234/tcp, 4444/tcp, 8291/tcp, 9100/tcp
2020-03-12 03:12:12
34.84.243.185 attackbotsspam
SSH Brute-Forcing (server1)
2020-03-12 03:38:22

Recently Reported IPs

13.52.219.126 13.52.219.244 13.52.219.155 13.52.219.205
13.52.218.38 13.52.219.40 13.52.220.101 13.52.220.59
13.52.220.119 13.52.220.128 13.52.221.65 13.52.231.134
13.52.230.182 13.52.231.28 13.52.235.128 13.52.235.107
13.52.231.230 13.52.235.188 13.52.235.239 13.52.235.40