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

;; QUESTION SECTION:
;13.52.40.132.			IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 11:25:02 CST 2022
;; MSG SIZE  rcvd: 105
Host info
132.40.52.13.in-addr.arpa domain name pointer ec2-13-52-40-132.us-west-1.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
132.40.52.13.in-addr.arpa	name = ec2-13-52-40-132.us-west-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
139.162.75.112 attack
Jan  3 11:03:07 nginx sshd[8402]: Connection from 139.162.75.112 port 60480 on 10.23.102.80 port 22
Jan  3 11:03:07 nginx sshd[8402]: Did not receive identification string from 139.162.75.112
2020-01-03 19:58:22
47.74.231.192 attackbotsspam
Invalid user pouhyet from 47.74.231.192 port 33718
2020-01-03 19:49:43
82.200.226.226 attackbotsspam
$f2bV_matches
2020-01-03 20:08:56
78.128.113.178 attackbots
20 attempts against mh-misbehave-ban on sonic.magehost.pro
2020-01-03 20:04:32
69.221.136.157 attack
400 BAD REQUEST
2020-01-03 19:43:25
139.155.20.146 attack
Jan  3 07:53:25 ks10 sshd[19417]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.155.20.146 
Jan  3 07:53:27 ks10 sshd[19417]: Failed password for invalid user nnnnn from 139.155.20.146 port 45126 ssh2
...
2020-01-03 20:03:07
5.188.84.230 attackbotsspam
0,30-02/34 [bc02/m206] PostRequest-Spammer scoring: maputo01_x2b
2020-01-03 19:51:12
189.170.31.45 attackbots
1578050485 - 01/03/2020 12:21:25 Host: 189.170.31.45/189.170.31.45 Port: 445 TCP Blocked
2020-01-03 19:33:32
2400:6180:0:d1::4c4:a001 attack
[munged]::443 2400:6180:0:d1::4c4:a001 - - [03/Jan/2020:09:04:45 +0100] "POST /[munged]: HTTP/1.1" 200 6188 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
[munged]::443 2400:6180:0:d1::4c4:a001 - - [03/Jan/2020:09:04:54 +0100] "POST /[munged]: HTTP/1.1" 200 6171 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2020-01-03 20:01:27
49.232.4.101 attack
Jan  3 06:06:59 dedicated sshd[2341]: Invalid user nrv from 49.232.4.101 port 55182
2020-01-03 19:44:28
5.135.179.178 attackspam
SSH Brute-Force reported by Fail2Ban
2020-01-03 19:47:36
116.108.233.61 attack
Unauthorized connection attempt detected from IP address 116.108.233.61 to port 445
2020-01-03 19:46:38
61.7.133.221 attackbots
20/1/2@23:45:23: FAIL: Alarm-Network address from=61.7.133.221
20/1/2@23:45:23: FAIL: Alarm-Network address from=61.7.133.221
...
2020-01-03 19:32:00
166.62.32.32 attackbotsspam
xmlrpc attack
2020-01-03 19:52:42
36.92.208.133 attackbotsspam
Attempt to attack host OS, exploiting network vulnerabilities, on 03-01-2020 04:45:11.
2020-01-03 19:40:06

Recently Reported IPs

13.52.239.70 13.52.37.231 13.52.41.140 13.52.47.185
13.52.48.154 13.52.34.165 13.52.51.179 13.52.69.132
13.52.68.41 13.52.84.170 13.52.79.119 13.52.88.245
13.52.95.246 13.52.95.111 13.53.102.118 13.53.149.7
13.53.186.181 13.53.200.232 13.53.228.127 13.53.70.220