城市(city): Ashburn
省份(region): Virginia
国家(country): United States
运营商(isp): 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-2026, American Registry for Internet Numbers, Ltd.
#
NetRange: 54.144.0.0 - 54.221.255.255
CIDR: 54.208.0.0/13, 54.220.0.0/15, 54.216.0.0/14, 54.192.0.0/12, 54.160.0.0/11, 54.144.0.0/12
NetName: AMAZON
NetHandle: NET-54-144-0-0-1
Parent: NET54 (NET-54-0-0-0-0)
NetType: Direct Allocation
OriginAS:
Organization: Amazon Technologies Inc. (AT-88-Z)
RegDate: 2014-10-23
Updated: 2021-02-10
Ref: https://rdap.arin.net/registry/ip/54.144.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: 2026-04-17
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: 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
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
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
OrgDNSHandle: DNS1131-ARIN
OrgDNSName: DNS
OrgDNSPhone: +1-202-555-0000
OrgDNSEmail: ipmanagement+dns@amazon.com
OrgDNSRef: https://rdap.arin.net/registry/entity/DNS1131-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
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
#
# 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-2026, American Registry for Internet Numbers, Ltd.
#; <<>> DiG 9.10.3-P4-Ubuntu <<>> 54.160.132.55
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 56627
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;54.160.132.55. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026060501 1800 900 604800 86400
;; Query time: 8 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Jun 06 08:30:32 CST 2026
;; MSG SIZE rcvd: 10655.132.160.54.in-addr.arpa domain name pointer ec2-54-160-132-55.compute-1.amazonaws.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
55.132.160.54.in-addr.arpa name = ec2-54-160-132-55.compute-1.amazonaws.com.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 188.166.111.207 | attackbotsspam | CMS (WordPress or Joomla) login attempt. |
2020-03-04 23:53:20 |
| 196.203.108.54 | attackspam | 445/tcp [2020-03-04]1pkt |
2020-03-04 23:14:08 |
| 104.248.16.213 | attackspambots | CMS (WordPress or Joomla) login attempt. |
2020-03-04 23:51:31 |
| 218.93.27.230 | attackspam | Mar 4 14:36:05 serwer sshd\[27940\]: Invalid user test from 218.93.27.230 port 49031 Mar 4 14:36:05 serwer sshd\[27940\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.93.27.230 Mar 4 14:36:07 serwer sshd\[27940\]: Failed password for invalid user test from 218.93.27.230 port 49031 ssh2 ... |
2020-03-04 23:54:54 |
| 222.186.31.135 | attackbotsspam | SSH bruteforce more then 50 syn to 22 port per 10 seconds. |
2020-03-04 23:24:39 |
| 202.105.107.124 | attackspambots | suspicious action Wed, 04 Mar 2020 10:36:24 -0300 |
2020-03-04 23:31:53 |
| 111.186.57.170 | attackspam | Mar 4 15:20:05 vpn01 sshd[10017]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.186.57.170 Mar 4 15:20:07 vpn01 sshd[10017]: Failed password for invalid user pellegrini from 111.186.57.170 port 47244 ssh2 ... |
2020-03-04 23:17:35 |
| 140.255.139.154 | attack | Mar 4 13:36:17 l03 postfix/smtpd[23984]: lost connection after AUTH from unknown[140.255.139.154] Mar 4 13:36:19 l03 postfix/smtpd[23984]: lost connection after AUTH from unknown[140.255.139.154] Mar 4 13:36:22 l03 postfix/smtpd[23984]: lost connection after AUTH from unknown[140.255.139.154] Mar 4 13:36:23 l03 postfix/smtpd[23984]: lost connection after AUTH from unknown[140.255.139.154] Mar 4 13:36:24 l03 postfix/smtpd[23984]: lost connection after AUTH from unknown[140.255.139.154] ... |
2020-03-04 23:29:35 |
| 182.77.95.183 | attackbots | 1583328986 - 03/04/2020 14:36:26 Host: 182.77.95.183/182.77.95.183 Port: 445 TCP Blocked |
2020-03-04 23:26:56 |
| 178.62.95.122 | attack | Mar 4 05:18:43 eddieflores sshd\[15936\]: Invalid user odoo from 178.62.95.122 Mar 4 05:18:43 eddieflores sshd\[15936\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.62.95.122 Mar 4 05:18:45 eddieflores sshd\[15936\]: Failed password for invalid user odoo from 178.62.95.122 port 33361 ssh2 Mar 4 05:26:50 eddieflores sshd\[16554\]: Invalid user gameserver from 178.62.95.122 Mar 4 05:26:50 eddieflores sshd\[16554\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.62.95.122 |
2020-03-04 23:27:09 |
| 182.226.87.165 | attackbots | Honeypot attack, port: 5555, PTR: PTR record not found |
2020-03-04 23:38:23 |
| 185.53.88.44 | attack | 185.53.88.44 was recorded 7 times by 7 hosts attempting to connect to the following ports: 5060. Incident counter (4h, 24h, all-time): 7, 10, 89 |
2020-03-04 23:48:11 |
| 23.83.179.208 | attackspam | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found drjenniferbrandon.com after doing a quick search – you showed up near the top of the rankings, so whatever you’re doing for SEO, looks like it’s working well. So here’s my question – what happens AFTER someone lands on your site? Anything? Research tells us at least 70% of the people who find your site, after a quick once-over, they disappear… forever. That means that all the work and effort you put into getting them to show up, goes down the tubes. Why would you want all that good work – and the great site you’ve built – go to waste? Because the odds are they’ll just skip over calling or even grabbing their phone, leaving you high and dry. But here’s a thought… what if you could make it super-simple for someone to raise their hand, say, “okay, let’s talk” without requiring them to even pull their cell phone from their pocket? You can – thanks to revolutionary new software t |
2020-03-04 23:40:59 |
| 117.141.6.210 | attack | suspicious action Wed, 04 Mar 2020 10:36:41 -0300 |
2020-03-04 23:12:37 |
| 221.140.151.235 | attack | $f2bV_matches |
2020-03-04 23:45:12 |