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: Seattle

Region: Washington

Country: United States

Internet Service Provider: unknown

Hostname: unknown

Organization: Amazon.com, Inc.

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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;54.240.13.20.			IN	A

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

;; Query time: 0 msec
;; SERVER: 67.207.67.3#53(67.207.67.3)
;; WHEN: Wed May 08 20:35:56 +08 2019
;; MSG SIZE  rcvd: 116

Host info
20.13.240.54.in-addr.arpa domain name pointer a13-20.smtp-out.amazonses.com.
Nslookup info:
Server:		67.207.67.3
Address:	67.207.67.3#53

Non-authoritative answer:
20.13.240.54.in-addr.arpa	name = a13-20.smtp-out.amazonses.com.

Authoritative answers can be found from:

Related IP info:
Related comments:
IP Type Details Datetime
218.92.0.189 attackspambots
03/08/2020-01:21:07.980593 218.92.0.189 Protocol: 6 ET SCAN Potential SSH Scan
2020-03-08 14:22:34
218.84.160.126 attackbots
1583643445 - 03/08/2020 11:57:25 Host: 218.84.160.126/218.84.160.126 Port: 8080 TCP Blocked
...
2020-03-08 14:34:36
112.85.42.187 attack
Mar  8 05:58:07 srv206 sshd[20273]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.187  user=root
Mar  8 05:58:10 srv206 sshd[20273]: Failed password for root from 112.85.42.187 port 27127 ssh2
...
2020-03-08 14:04:56
36.75.155.135 attackspambots
20/3/7@23:57:58: FAIL: Alarm-Network address from=36.75.155.135
20/3/7@23:57:58: FAIL: Alarm-Network address from=36.75.155.135
...
2020-03-08 14:17:19
51.75.23.214 attackspam
CMS (WordPress or Joomla) login attempt.
2020-03-08 14:32:19
158.69.204.172 attackspam
Mar  7 18:54:24 web1 sshd\[13490\]: Invalid user server from 158.69.204.172
Mar  7 18:54:24 web1 sshd\[13490\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=158.69.204.172
Mar  7 18:54:26 web1 sshd\[13490\]: Failed password for invalid user server from 158.69.204.172 port 55176 ssh2
Mar  7 18:57:22 web1 sshd\[13761\]: Invalid user rustserver from 158.69.204.172
Mar  7 18:57:22 web1 sshd\[13761\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=158.69.204.172
2020-03-08 14:36:06
37.123.136.188 attackspam
Mar  8 07:27:46 dcd-gentoo sshd[18164]: Invalid user admin from 37.123.136.188 port 36248
Mar  8 07:27:48 dcd-gentoo sshd[18164]: error: PAM: Authentication failure for illegal user admin from 37.123.136.188
Mar  8 07:27:46 dcd-gentoo sshd[18164]: Invalid user admin from 37.123.136.188 port 36248
Mar  8 07:27:48 dcd-gentoo sshd[18164]: error: PAM: Authentication failure for illegal user admin from 37.123.136.188
Mar  8 07:27:46 dcd-gentoo sshd[18164]: Invalid user admin from 37.123.136.188 port 36248
Mar  8 07:27:48 dcd-gentoo sshd[18164]: error: PAM: Authentication failure for illegal user admin from 37.123.136.188
Mar  8 07:27:48 dcd-gentoo sshd[18164]: Failed keyboard-interactive/pam for invalid user admin from 37.123.136.188 port 36248 ssh2
...
2020-03-08 14:35:13
165.227.26.69 attackbots
Mar  8 05:58:02 vpn01 sshd[5751]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.227.26.69
Mar  8 05:58:03 vpn01 sshd[5751]: Failed password for invalid user 123qqq from 165.227.26.69 port 51182 ssh2
...
2020-03-08 14:11:20
218.92.0.179 attack
web-1 [ssh] SSH Attack
2020-03-08 14:03:49
222.186.139.55 attackspambots
SASL broute force
2020-03-08 14:03:12
49.234.43.39 attackbots
Mar  8 05:50:38 ns382633 sshd\[30376\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.43.39  user=root
Mar  8 05:50:40 ns382633 sshd\[30376\]: Failed password for root from 49.234.43.39 port 57788 ssh2
Mar  8 05:58:34 ns382633 sshd\[31363\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.43.39  user=root
Mar  8 05:58:36 ns382633 sshd\[31363\]: Failed password for root from 49.234.43.39 port 48806 ssh2
Mar  8 06:02:00 ns382633 sshd\[32071\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.43.39  user=root
2020-03-08 14:10:28
213.32.111.52 attackspambots
Mar  8 06:10:58 localhost sshd\[11136\]: Invalid user pi from 213.32.111.52
Mar  8 06:10:58 localhost sshd\[11136\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.32.111.52
Mar  8 06:11:00 localhost sshd\[11136\]: Failed password for invalid user pi from 213.32.111.52 port 34110 ssh2
Mar  8 06:17:46 localhost sshd\[11386\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.32.111.52  user=root
Mar  8 06:17:48 localhost sshd\[11386\]: Failed password for root from 213.32.111.52 port 52912 ssh2
...
2020-03-08 14:15:47
61.53.232.2 attack
" "
2020-03-08 14:27:02
2.139.209.78 attackbots
SSH Brute-Forcing (server1)
2020-03-08 14:17:47
62.210.185.4 attackspam
Automatic report - XMLRPC Attack
2020-03-08 14:25:03

Recently Reported IPs

107.7.82.138 175.79.195.131 5.9.56.170 101.9.65.89
201.43.38.77 149.5.126.104 54.174.52.110 120.17.254.182
188.166.123.14 65.158.217.25 115.203.238.98 103.76.185.50
191.252.12.40 159.253.34.164 44.244.11.201 51.15.149.128
113.9.108.112 156.67.115.5 212.31.98.139 142.93.236.69