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

;; QUESTION SECTION:
;13.52.235.40.			IN	A

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

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

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

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
31.41.218.24 attack
11/23/2019-19:35:30.834910 31.41.218.24 Protocol: 6 ET SCAN NMAP -sS window 1024
2019-11-24 09:08:42
213.32.91.71 attackbots
213.32.91.71 - - \[23/Nov/2019:23:43:15 +0100\] "POST /wp-login.php HTTP/1.0" 200 4128 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
213.32.91.71 - - \[23/Nov/2019:23:43:16 +0100\] "POST /wp-login.php HTTP/1.0" 200 3955 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
213.32.91.71 - - \[23/Nov/2019:23:43:16 +0100\] "POST /xmlrpc.php HTTP/1.0" 200 736 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
2019-11-24 09:04:45
23.25.133.82 attackbotsspam
RDP Bruteforce
2019-11-24 09:43:04
132.248.52.241 attackspam
Nov 24 02:03:07 vps666546 sshd\[26234\]: Invalid user hatty from 132.248.52.241 port 52569
Nov 24 02:03:07 vps666546 sshd\[26234\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.248.52.241
Nov 24 02:03:09 vps666546 sshd\[26234\]: Failed password for invalid user hatty from 132.248.52.241 port 52569 ssh2
Nov 24 02:11:48 vps666546 sshd\[26729\]: Invalid user tarique from 132.248.52.241 port 44378
Nov 24 02:11:48 vps666546 sshd\[26729\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.248.52.241
...
2019-11-24 09:35:28
150.223.10.13 attackbotsspam
2019-11-24T01:21:15.705163abusebot-6.cloudsearch.cf sshd\[14515\]: Invalid user apache from 150.223.10.13 port 39230
2019-11-24 09:35:12
2604:a880:800:c1::16c:b001 attackbots
xmlrpc attack
2019-11-24 09:41:18
148.240.238.91 attackbotsspam
2019-11-24T01:22:28.554766shield sshd\[21721\]: Invalid user alohalani from 148.240.238.91 port 39490
2019-11-24T01:22:28.560475shield sshd\[21721\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.240.238.91
2019-11-24T01:22:30.634034shield sshd\[21721\]: Failed password for invalid user alohalani from 148.240.238.91 port 39490 ssh2
2019-11-24T01:29:28.154103shield sshd\[23227\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.240.238.91  user=root
2019-11-24T01:29:30.553837shield sshd\[23227\]: Failed password for root from 148.240.238.91 port 48692 ssh2
2019-11-24 09:37:16
112.113.118.19 attack
badbot
2019-11-24 09:16:37
122.51.83.37 attackspam
Nov 23 14:53:16 auw2 sshd\[10902\]: Invalid user elder from 122.51.83.37
Nov 23 14:53:16 auw2 sshd\[10902\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.83.37
Nov 23 14:53:18 auw2 sshd\[10902\]: Failed password for invalid user elder from 122.51.83.37 port 48948 ssh2
Nov 23 15:00:47 auw2 sshd\[11492\]: Invalid user diesner from 122.51.83.37
Nov 23 15:00:47 auw2 sshd\[11492\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.83.37
2019-11-24 09:23:19
129.211.104.34 attackspambots
Nov 23 23:42:31 serwer sshd\[25421\]: Invalid user server from 129.211.104.34 port 45828
Nov 23 23:42:31 serwer sshd\[25421\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.211.104.34
Nov 23 23:42:33 serwer sshd\[25421\]: Failed password for invalid user server from 129.211.104.34 port 45828 ssh2
...
2019-11-24 09:36:34
167.99.203.202 attack
Nov 24 02:18:25 meumeu sshd[31930]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.203.202 
Nov 24 02:18:27 meumeu sshd[31930]: Failed password for invalid user test from 167.99.203.202 port 43032 ssh2
Nov 24 02:26:43 meumeu sshd[769]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.203.202 
...
2019-11-24 09:34:55
119.41.167.125 attackbots
11/23/2019-17:42:53.095928 119.41.167.125 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2019-11-24 09:23:55
79.166.145.169 attackspambots
Telnet Server BruteForce Attack
2019-11-24 09:15:56
95.213.177.122 attackspambots
95.213.177.122 was recorded 40 times by 10 hosts attempting to connect to the following ports: 65531,3128,8080,8000,8888,8118,9050,1080,8081,32525. Incident counter (4h, 24h, all-time): 40, 94, 5073
2019-11-24 09:39:06
128.199.125.95 attack
Invalid user manhat from 128.199.125.95 port 60069
2019-11-24 09:31:06

Recently Reported IPs

13.52.235.239 13.52.235.19 13.52.235.251 13.52.235.8
13.52.237.55 214.59.11.155 13.52.237.170 13.52.238.113
13.52.237.156 13.52.238.145 13.52.238.80 13.52.240.105
13.52.240.123 13.52.240.17 13.52.240.176 13.52.240.253
13.52.242.242 13.52.240.49 13.52.242.246 13.52.24.180