City: Ashburn
Region: Virginia
Country: United States
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2025, American Registry for Internet Numbers, Ltd.
#
# start
NetRange: 54.224.0.0 - 54.255.255.255
CIDR: 54.224.0.0/11
NetName: AMAZON-2011L
NetHandle: NET-54-224-0-0-1
Parent: NET54 (NET-54-0-0-0-0)
NetType: Direct Allocation
OriginAS:
Organization: Amazon Technologies Inc. (AT-88-Z)
RegDate: 2012-03-01
Updated: 2021-02-10
Comment: -----BEGIN CERTIFICATE-----MIICljCCAX4CCQDvS1je1Bd4uzANBgkqhkiG9w0BAQsFADANMQswCQYDVQQGEwJVUzAeFw0yMDA4MjYxODQ1NThaFw0yMTA4MjYxODQ1NThaMA0xCzAJBgNVBAYTAlVTMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA5geQJL7KoQhQLaTteXnFj0xsze15HgB9cpHPoL6khWVUthOg6AYCBHCcVJWeuEHuYGJcnrtW1tyLWpgfrxaw5E4ZtunSHElzO6BIp2u0215mbSGPQUt3TMR64nvXvEAY4qBP/p2+j0ud2eI47eA3s2ykFztEJPb7eZh8lVCGj5n2msRxeFiYwoB7/u3TDnW0/BwNLnJgyGkAWYUlk68hR10LHoBqGPezn7mPuiLHNa6JQP0WTYBz/80kS3m/4oZ7NS20PMieXqFjfYEgW6fPg7uJKhH3aYVVveZpBS5cRzm360HyT5hj1rUJh34nVCLMlvP+400w1wxr9buLnQzVlwIDAQABMA0GCSqGSIb3DQEBCwUAA4IBAQCZD7ERFb2LpeLdQgyji/ZqZ7lDXR8wq4m+ihMiqpPcwTVs1dfBfKDvZ4K6Ddyzkfd1NQYPWiV47nvqgJxwdISa7vN011RxBEGkYdJ8cNaRXW7aCGfQ8ZSQL6mbXsm4sbvDQNHiWJcdUB0KTzR/wpbXf9+24TbPGaOsZvfnKtd1lZhY5xFiOVCOdI59c/XyDH9aqOKNE0pOeATX55I3bU5PKeK5CM8oAtD2sFAQ956Uvj7/vFDs8QP3upzf53R+erSU10L1fTQBWHjNUCcf9wviS+U4hsaCcBZMlw6d5Q84GYX1tS+YwtA0Fv/NQcOWr9RJT+JVnpbyAxEyjI37XOqH-----END CERTIFICATE-----
Ref: https://rdap.arin.net/registry/ip/54.224.0.0
OrgName: Amazon Technologies Inc.
OrgId: AT-88-Z
Address: 410 Terry Ave N.
City: Seattle
StateProv: WA
PostalCode: 98109
Country: US
RegDate: 2011-12-08
Updated: 2024-01-24
Comment: All abuse reports MUST include:
Comment: * src IP
Comment: * dest IP (your IP)
Comment: * dest port
Comment: * Accurate date/timestamp and timezone of activity
Comment: * Intensity/frequency (short log extracts)
Comment: * Your contact details (phone and email) Without these we will be unable to identify the correct owner of the IP address at that point in time.
Ref: https://rdap.arin.net/registry/entity/AT-88-Z
OrgRoutingHandle: ARMP-ARIN
OrgRoutingName: AWS RPKI Management POC
OrgRoutingPhone: +1-206-555-0000
OrgRoutingEmail: aws-rpki-routing-poc@amazon.com
OrgRoutingRef: https://rdap.arin.net/registry/entity/ARMP-ARIN
OrgRoutingHandle: IPROU3-ARIN
OrgRoutingName: IP Routing
OrgRoutingPhone: +1-206-555-0000
OrgRoutingEmail: aws-routing-poc@amazon.com
OrgRoutingRef: https://rdap.arin.net/registry/entity/IPROU3-ARIN
OrgAbuseHandle: AEA8-ARIN
OrgAbuseName: Amazon EC2 Abuse
OrgAbusePhone: +1-206-555-0000
OrgAbuseEmail: trustandsafety@support.aws.com
OrgAbuseRef: https://rdap.arin.net/registry/entity/AEA8-ARIN
OrgNOCHandle: AANO1-ARIN
OrgNOCName: Amazon AWS Network Operations
OrgNOCPhone: +1-206-555-0000
OrgNOCEmail: amzn-noc-contact@amazon.com
OrgNOCRef: https://rdap.arin.net/registry/entity/AANO1-ARIN
OrgTechHandle: ANO24-ARIN
OrgTechName: Amazon EC2 Network Operations
OrgTechPhone: +1-206-555-0000
OrgTechEmail: amzn-noc-contact@amazon.com
OrgTechRef: https://rdap.arin.net/registry/entity/ANO24-ARIN
# end
# start
NetRange: 54.234.0.0 - 54.235.255.255
CIDR: 54.234.0.0/15
NetName: AMAZO-ZIAD2
NetHandle: NET-54-234-0-0-1
Parent: AMAZON-2011L (NET-54-224-0-0-1)
NetType: Reallocated
OriginAS:
Organization: Amazon.com, Inc. (AMAZO-4)
RegDate: 2012-11-30
Updated: 2012-11-30
Ref: https://rdap.arin.net/registry/ip/54.234.0.0
OrgName: Amazon.com, Inc.
OrgId: AMAZO-4
Address: Amazon Web Services, Inc.
Address: P.O. Box 81226
City: Seattle
StateProv: WA
PostalCode: 98108-1226
Country: US
RegDate: 2005-09-29
Updated: 2022-09-30
Comment: For details of this service please see
Comment: http://ec2.amazonaws.com
Ref: https://rdap.arin.net/registry/entity/AMAZO-4
OrgNOCHandle: AANO1-ARIN
OrgNOCName: Amazon AWS Network Operations
OrgNOCPhone: +1-206-555-0000
OrgNOCEmail: amzn-noc-contact@amazon.com
OrgNOCRef: https://rdap.arin.net/registry/entity/AANO1-ARIN
OrgRoutingHandle: ARMP-ARIN
OrgRoutingName: AWS RPKI Management POC
OrgRoutingPhone: +1-206-555-0000
OrgRoutingEmail: aws-rpki-routing-poc@amazon.com
OrgRoutingRef: https://rdap.arin.net/registry/entity/ARMP-ARIN
OrgRoutingHandle: IPROU3-ARIN
OrgRoutingName: IP Routing
OrgRoutingPhone: +1-206-555-0000
OrgRoutingEmail: aws-routing-poc@amazon.com
OrgRoutingRef: https://rdap.arin.net/registry/entity/IPROU3-ARIN
OrgAbuseHandle: AEA8-ARIN
OrgAbuseName: Amazon EC2 Abuse
OrgAbusePhone: +1-206-555-0000
OrgAbuseEmail: trustandsafety@support.aws.com
OrgAbuseRef: https://rdap.arin.net/registry/entity/AEA8-ARIN
OrgTechHandle: ANO24-ARIN
OrgTechName: Amazon EC2 Network Operations
OrgTechPhone: +1-206-555-0000
OrgTechEmail: amzn-noc-contact@amazon.com
OrgTechRef: https://rdap.arin.net/registry/entity/ANO24-ARIN
# end
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2025, American Registry for Internet Numbers, Ltd.
#
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 54.234.97.40
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 26145
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;54.234.97.40. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025101701 1800 900 604800 86400
;; Query time: 197 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Oct 18 09:30:17 CST 2025
;; MSG SIZE rcvd: 105
40.97.234.54.in-addr.arpa domain name pointer ec2-54-234-97-40.compute-1.amazonaws.com.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
40.97.234.54.in-addr.arpa name = ec2-54-234-97-40.compute-1.amazonaws.com.
Authoritative answers can be found from:
IP | Type | Details | Datetime |
---|---|---|---|
121.182.166.82 | attackspam | Aug 29 07:04:10 OPSO sshd\[5064\]: Invalid user kmysclub from 121.182.166.82 port 10234 Aug 29 07:04:10 OPSO sshd\[5064\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.182.166.82 Aug 29 07:04:11 OPSO sshd\[5064\]: Failed password for invalid user kmysclub from 121.182.166.82 port 10234 ssh2 Aug 29 07:09:14 OPSO sshd\[6090\]: Invalid user 123 from 121.182.166.82 port 55556 Aug 29 07:09:14 OPSO sshd\[6090\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.182.166.82 |
2019-08-29 13:13:09 |
218.92.0.194 | attack | 2019-08-29T04:56:11.483551abusebot-8.cloudsearch.cf sshd\[10585\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.194 user=root |
2019-08-29 12:57:59 |
141.98.81.37 | attackspambots | Invalid user admin from 141.98.81.37 port 40973 |
2019-08-29 13:39:35 |
71.6.146.130 | attack | 3389BruteforceStormFW21 |
2019-08-29 12:43:58 |
207.154.232.160 | attackspambots | Aug 29 08:07:27 hosting sshd[10449]: Invalid user test from 207.154.232.160 port 34118 Aug 29 08:07:27 hosting sshd[10449]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=207.154.232.160 Aug 29 08:07:27 hosting sshd[10449]: Invalid user test from 207.154.232.160 port 34118 Aug 29 08:07:29 hosting sshd[10449]: Failed password for invalid user test from 207.154.232.160 port 34118 ssh2 Aug 29 08:12:54 hosting sshd[10793]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=207.154.232.160 user=root Aug 29 08:12:57 hosting sshd[10793]: Failed password for root from 207.154.232.160 port 49416 ssh2 ... |
2019-08-29 13:25:27 |
104.214.231.44 | attack | Aug 29 07:08:41 SilenceServices sshd[27224]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.214.231.44 Aug 29 07:08:43 SilenceServices sshd[27224]: Failed password for invalid user demo from 104.214.231.44 port 35460 ssh2 Aug 29 07:13:48 SilenceServices sshd[29314]: Failed password for mail from 104.214.231.44 port 53926 ssh2 |
2019-08-29 13:23:27 |
168.227.212.66 | attackspambots | [Aegis] @ 2019-08-29 00:48:03 0100 -> Multiple attempts to send e-mail from invalid/unknown sender domain. |
2019-08-29 13:47:43 |
50.117.96.61 | attackbotsspam | Aug 29 07:21:15 lnxmysql61 sshd[31165]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=50.117.96.61 |
2019-08-29 13:44:20 |
95.33.149.15 | attackbots | Aug 29 01:49:47 XXX sshd[47521]: Invalid user uuuuu from 95.33.149.15 port 57988 |
2019-08-29 12:50:40 |
95.246.201.35 | attack | Aug 29 01:16:21 pl3server sshd[1596559]: Failed password for r.r from 95.246.201.35 port 60126 ssh2 Aug 29 01:16:23 pl3server sshd[1596559]: Failed password for r.r from 95.246.201.35 port 60126 ssh2 Aug 29 01:16:26 pl3server sshd[1596559]: Failed password for r.r from 95.246.201.35 port 60126 ssh2 ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=95.246.201.35 |
2019-08-29 13:20:50 |
96.57.82.166 | attackbotsspam | Aug 29 01:13:28 xtremcommunity sshd\[20784\]: Invalid user moylea from 96.57.82.166 port 64911 Aug 29 01:13:28 xtremcommunity sshd\[20784\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=96.57.82.166 Aug 29 01:13:30 xtremcommunity sshd\[20784\]: Failed password for invalid user moylea from 96.57.82.166 port 64911 ssh2 Aug 29 01:18:12 xtremcommunity sshd\[20913\]: Invalid user max from 96.57.82.166 port 65007 Aug 29 01:18:12 xtremcommunity sshd\[20913\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=96.57.82.166 ... |
2019-08-29 13:21:23 |
146.185.149.245 | attack | Aug 29 00:42:52 debian sshd[30444]: Unable to negotiate with 146.185.149.245 port 39754: no matching key exchange method found. Their offer: ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 [preauth] Aug 29 00:51:13 debian sshd[30796]: Unable to negotiate with 146.185.149.245 port 33360: no matching key exchange method found. Their offer: ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 [preauth] ... |
2019-08-29 13:04:35 |
113.161.238.25 | attackbots | Automatic report - Port Scan Attack |
2019-08-29 13:11:59 |
219.128.23.26 | attackbotsspam | Aug 29 03:14:47 *** sshd[31328]: reveeclipse mapping checking getaddrinfo for 26.23.128.219.broad.zs.gd.dynamic.163data.com.cn [219.128.23.26] failed - POSSIBLE BREAK-IN ATTEMPT! Aug 29 03:14:47 *** sshd[31328]: Invalid user admin from 219.128.23.26 Aug 29 03:14:47 *** sshd[31328]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=219.128.23.26 Aug 29 03:14:49 *** sshd[31328]: Failed password for invalid user admin from 219.128.23.26 port 33608 ssh2 Aug 29 03:14:51 *** sshd[31328]: Failed password for invalid user admin from 219.128.23.26 port 33608 ssh2 Aug 29 03:14:53 *** sshd[31328]: Failed password for invalid user admin from 219.128.23.26 port 33608 ssh2 Aug 29 03:14:55 *** sshd[31328]: Failed password for invalid user admin from 219.128.23.26 port 33608 ssh2 Aug 29 03:14:57 *** sshd[31328]: Failed password for invalid user admin from 219.128.23.26 port 33608 ssh2 Aug 29 03:14:59 *** sshd[31328]: Failed password for invalid us........ ------------------------------- |
2019-08-29 13:12:33 |
14.177.234.161 | attack | @LucianNitescu Personal Honeypot Network <<<>>> Donate at paypal.me/LNitescu <<<>>> 2019-08-28 21:57:12,854 INFO [amun_request_handler] PortScan Detected on Port: 445 (14.177.234.161) |
2019-08-29 13:02:05 |