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

;; QUESTION SECTION:
;13.52.80.151.			IN	A

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

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

Non-authoritative answer:
151.80.52.13.in-addr.arpa	name = ec2-13-52-80-151.us-west-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
198.211.120.59 attackspam
12/30/2019-22:42:32.011917 198.211.120.59 Protocol: 17 ET INFO Session Traversal Utilities for NAT (STUN Binding Response)
2019-12-31 05:46:04
40.77.167.81 attack
Automatic report - Banned IP Access
2019-12-31 05:14:39
85.104.112.200 attackbotsspam
Honeypot attack, port: 23, PTR: 85.104.112.200.dynamic.ttnet.com.tr.
2019-12-31 05:27:01
217.21.193.74 attackspambots
Portscan or hack attempt detected by psad/fwsnort
2019-12-31 05:12:34
192.99.244.225 attackbots
Lines containing failures of 192.99.244.225
Dec 29 07:33:13 keyhelp sshd[29320]: Invalid user michelussi from 192.99.244.225 port 39762
Dec 29 07:33:13 keyhelp sshd[29320]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.99.244.225
Dec 29 07:33:15 keyhelp sshd[29320]: Failed password for invalid user michelussi from 192.99.244.225 port 39762 ssh2
Dec 29 07:33:17 keyhelp sshd[29320]: Received disconnect from 192.99.244.225 port 39762:11: Bye Bye [preauth]
Dec 29 07:33:17 keyhelp sshd[29320]: Disconnected from invalid user michelussi 192.99.244.225 port 39762 [preauth]
Dec 30 21:10:12 keyhelp sshd[21716]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.99.244.225  user=lp
Dec 30 21:10:13 keyhelp sshd[21716]: Failed password for lp from 192.99.244.225 port 32816 ssh2
Dec 30 21:10:15 keyhelp sshd[21716]: Received disconnect from 192.99.244.225 port 32816:11: Bye Bye [preauth]
Dec 30 21:10........
------------------------------
2019-12-31 05:40:59
157.7.184.37 attackbotsspam
WordPress login Brute force / Web App Attack on client site.
2019-12-31 05:13:26
117.48.208.71 attack
Unauthorized connection attempt detected from IP address 117.48.208.71 to port 22
2019-12-31 05:31:06
140.143.199.89 attackspambots
2019-12-30T20:53:05.036303shield sshd\[21582\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.199.89  user=root
2019-12-30T20:53:07.172070shield sshd\[21582\]: Failed password for root from 140.143.199.89 port 41474 ssh2
2019-12-30T20:56:33.354315shield sshd\[22153\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.199.89  user=sync
2019-12-30T20:56:35.710916shield sshd\[22153\]: Failed password for sync from 140.143.199.89 port 43732 ssh2
2019-12-30T21:00:36.368459shield sshd\[22778\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.199.89  user=root
2019-12-31 05:12:14
51.37.130.84 attackbots
SSH bruteforce (Triggered fail2ban)
2019-12-31 05:34:40
106.13.72.95 attackbots
Dec 30 21:36:13 haigwepa sshd[22294]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.72.95 
Dec 30 21:36:15 haigwepa sshd[22294]: Failed password for invalid user sanjavier from 106.13.72.95 port 51366 ssh2
...
2019-12-31 05:31:37
202.51.178.126 attackbotsspam
proto=tcp  .  spt=41312  .  dpt=25  .     (Found on   Dark List de Dec 30)     (441)
2019-12-31 05:34:09
1.201.140.126 attackspam
2019-12-30T20:49:54.410476shield sshd\[20979\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.201.140.126  user=root
2019-12-30T20:49:56.992711shield sshd\[20979\]: Failed password for root from 1.201.140.126 port 60324 ssh2
2019-12-30T20:53:11.010742shield sshd\[21594\]: Invalid user guest from 1.201.140.126 port 46915
2019-12-30T20:53:11.014850shield sshd\[21594\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.201.140.126
2019-12-30T20:53:12.974799shield sshd\[21594\]: Failed password for invalid user guest from 1.201.140.126 port 46915 ssh2
2019-12-31 05:48:51
89.35.235.51 attack
Unauthorized connection attempt detected from IP address 89.35.235.51 to port 1433
2019-12-31 05:28:43
172.246.250.82 attack
Dec 30 21:12:59 debian-2gb-nbg1-2 kernel: \[1389484.335183\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=172.246.250.82 DST=195.201.40.59 LEN=40 TOS=0x08 PREC=0x20 TTL=240 ID=63790 PROTO=TCP SPT=55637 DPT=1433 WINDOW=1024 RES=0x00 SYN URGP=0
2019-12-31 05:26:37
105.21.40.54 attackspam
proto=tcp  .  spt=55888  .  dpt=25  .     (Found on   Blocklist de  Dec 30)     (438)
2019-12-31 05:41:55

Recently Reported IPs

13.52.80.96 13.52.80.176 13.52.81.218 13.52.82.60
13.52.97.126 13.52.97.138 13.52.85.215 13.52.97.233
13.52.97.68 13.52.98.217 13.52.98.127 13.52.81.198
13.52.97.43 211.191.129.167 13.56.127.88 13.56.140.0
13.56.140.99 13.56.145.104 13.56.140.163 13.56.140.182