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 of America (the)

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

;; QUESTION SECTION:
;52.22.132.40.			IN	A

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

;; Query time: 11 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 28 10:04:47 CST 2025
;; MSG SIZE  rcvd: 105
Host info
40.132.22.52.in-addr.arpa domain name pointer ec2-52-22-132-40.compute-1.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
40.132.22.52.in-addr.arpa	name = ec2-52-22-132-40.compute-1.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
218.80.245.54 attackbotsspam
Unauthorised access (Oct 13) SRC=218.80.245.54 LEN=44 TOS=0x10 PREC=0x40 TTL=240 ID=8459 TCP DPT=445 WINDOW=1024 SYN
2019-10-14 05:23:57
110.19.120.104 attack
port scan and connect, tcp 23 (telnet)
2019-10-14 05:16:16
222.186.180.41 attackbots
10/13/2019-16:51:25.857431 222.186.180.41 Protocol: 6 ET SCAN Potential SSH Scan
2019-10-14 04:52:24
168.194.140.130 attackbotsspam
Feb  9 20:31:51 dillonfme sshd\[32117\]: Invalid user shubham from 168.194.140.130 port 54936
Feb  9 20:31:51 dillonfme sshd\[32117\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.194.140.130
Feb  9 20:31:53 dillonfme sshd\[32117\]: Failed password for invalid user shubham from 168.194.140.130 port 54936 ssh2
Feb  9 20:38:13 dillonfme sshd\[32292\]: Invalid user chen from 168.194.140.130 port 46088
Feb  9 20:38:13 dillonfme sshd\[32292\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.194.140.130
...
2019-10-14 04:52:47
167.99.77.94 attack
Mar 12 18:56:21 yesfletchmain sshd\[24884\]: User root from 167.99.77.94 not allowed because not listed in AllowUsers
Mar 12 18:56:21 yesfletchmain sshd\[24884\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.77.94  user=root
Mar 12 18:56:23 yesfletchmain sshd\[24884\]: Failed password for invalid user root from 167.99.77.94 port 49892 ssh2
Mar 12 19:01:24 yesfletchmain sshd\[25031\]: User root from 167.99.77.94 not allowed because not listed in AllowUsers
Mar 12 19:01:24 yesfletchmain sshd\[25031\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.77.94  user=root
...
2019-10-14 05:18:10
223.220.159.78 attack
Oct 13 22:29:47 legacy sshd[32027]: Failed password for root from 223.220.159.78 port 19019 ssh2
Oct 13 22:34:07 legacy sshd[32178]: Failed password for root from 223.220.159.78 port 57639 ssh2
...
2019-10-14 04:48:00
168.167.30.198 attackspambots
May 11 08:45:31 yesfletchmain sshd\[18194\]: Invalid user ftp01 from 168.167.30.198 port 59185
May 11 08:45:31 yesfletchmain sshd\[18194\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.167.30.198
May 11 08:45:33 yesfletchmain sshd\[18194\]: Failed password for invalid user ftp01 from 168.167.30.198 port 59185 ssh2
May 11 08:54:24 yesfletchmain sshd\[18364\]: Invalid user dave from 168.167.30.198 port 44537
May 11 08:54:24 yesfletchmain sshd\[18364\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.167.30.198
...
2019-10-14 05:08:04
5.189.140.141 attackspam
abasicmove.de 5.189.140.141 \[13/Oct/2019:22:15:48 +0200\] "POST /wp-login.php HTTP/1.1" 200 5757 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
abasicmove.de 5.189.140.141 \[13/Oct/2019:22:15:49 +0200\] "POST /wp-login.php HTTP/1.1" 200 5697 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
2019-10-14 05:13:06
58.162.140.172 attack
Oct 14 00:00:28 sauna sshd[170248]: Failed password for root from 58.162.140.172 port 48394 ssh2
...
2019-10-14 05:13:59
103.60.126.80 attackbotsspam
2019-10-13T20:48:35.050086abusebot-5.cloudsearch.cf sshd\[11705\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.60.126.80  user=root
2019-10-14 04:51:38
168.194.205.49 attackbots
Mar  8 19:54:50 dillonfme sshd\[29012\]: User root from 168.194.205.49 not allowed because not listed in AllowUsers
Mar  8 19:54:50 dillonfme sshd\[29012\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.194.205.49  user=root
Mar  8 19:54:52 dillonfme sshd\[29012\]: Failed password for invalid user root from 168.194.205.49 port 35912 ssh2
Mar  8 20:00:33 dillonfme sshd\[29125\]: Invalid user contact from 168.194.205.49 port 45758
Mar  8 20:00:33 dillonfme sshd\[29125\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.194.205.49
...
2019-10-14 04:44:49
59.13.139.42 attack
Oct 13 22:15:59 host sshd\[36263\]: Invalid user stacee from 59.13.139.42 port 40966
Oct 13 22:15:59 host sshd\[36263\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.13.139.42
...
2019-10-14 05:06:38
222.186.175.155 attack
web-1 [ssh] SSH Attack
2019-10-14 04:53:19
168.195.176.105 attackspambots
Apr 16 23:44:32 yesfletchmain sshd\[29064\]: Invalid user Else from 168.195.176.105 port 47809
Apr 16 23:44:32 yesfletchmain sshd\[29064\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.195.176.105
Apr 16 23:44:34 yesfletchmain sshd\[29064\]: Failed password for invalid user Else from 168.195.176.105 port 47809 ssh2
Apr 16 23:47:44 yesfletchmain sshd\[29144\]: Invalid user pk from 168.195.176.105 port 59713
Apr 16 23:47:44 yesfletchmain sshd\[29144\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.195.176.105
...
2019-10-14 04:44:15
168.194.163.138 attack
Mar 13 17:06:41 yesfletchmain sshd\[6015\]: Invalid user ts3 from 168.194.163.138 port 6357
Mar 13 17:06:41 yesfletchmain sshd\[6015\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.194.163.138
Mar 13 17:06:44 yesfletchmain sshd\[6015\]: Failed password for invalid user ts3 from 168.194.163.138 port 6357 ssh2
Mar 13 17:12:09 yesfletchmain sshd\[6267\]: Invalid user user from 168.194.163.138 port 43284
Mar 13 17:12:09 yesfletchmain sshd\[6267\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.194.163.138
...
2019-10-14 04:47:43

Recently Reported IPs

68.5.102.252 22.189.102.32 65.86.18.243 84.216.176.107
143.4.200.215 106.244.149.36 149.34.67.21 2.89.3.31
135.232.154.74 86.223.201.132 191.245.80.245 157.43.210.234
211.99.178.50 232.90.220.170 149.109.139.152 227.126.239.236
156.76.88.151 120.108.228.25 139.72.47.97 194.234.238.245