PhishPin / Brands Live Phishing Data / Tech, email & cloud / Amazon Web Services
Amazon Web Services phishing: how to spot fake sites, domains & scams
PhishPin's phishing-feed index currently lists 5 hostnames that reference Amazon Web Services, across 8 reported URLs from 1 of 6 threat feeds we track. Amazon Web Services ranks #536 of 2108 brands we track by reported hosts. No newly registered domain in the last 15 days matched the name.
Tech, email & cloud · rank #536 of 2108 by reported hosts
Key findings for Amazon Web Services
- Impersonation pressure is Low (14/100): Amazon Web Services has more reported hosts than 74% of the 2108 brands we track.
- That is 0.1× the average for tech, email & cloud (43 hosts per brand).
- 4 hosts (80%) hide the Amazon Web Services name in a subdomain of an unrelated site, the trick that makes a link look official at a glance.
- The most common ending is .com (1 hosts, 20%).
- 80% of hosts pair the brand with a bait word. The most common is “signin” (4 hosts).
How attackers fake Amazon Web Services
These breakdowns cover all 5 matching hostnames, not only the rows listed below.
Top endings (TLDs)
Bait words next to the brand
Hostname tricks
Hosts reported in phishing feeds
The most widely reported hostnames that reference Amazon Web Services, ranked by how many feeds list them and then by reported URLs. Search, filter and export all 5 rows.
| # | Hostname (defanged) | Pattern | Feeds | URLs |
|---|---|---|---|---|
| 1 | e-aws-console[.]com | name in domain | 1 feed | 2 |
| 2 | signin-aws-amazon[.]com-signin-redirect-1384119c[.]ijsblokjesvlaanderen[.]be | subdomain tricksignin | 1 feed | 2 |
| 3 | signin-aws-amazon[.]com-signin-redirect-d073e551[.]thermodoos[.]nl | subdomain tricksignin | 1 feed | 2 |
| 4 | signin-aws-amazon[.]pages[.]dev | subdomain tricksignin | 1 feed | 1 |
| 5 | www[.]signinawsconsole[.]duckdns[.]org | subdomain tricksignin | 1 feed | 1 |
Is your brand in these feeds?
Free check: email-spoofing gaps, registered lookalikes and feed listings for your own domain. About a minute, public DNS only.
New lookalike domains registered recently
How Amazon Web Services phishing works
Phishing against Amazon Web Services follows patterns common to tech, email & cloud. Typical lures:
- A "password expires today" or "mailbox full" email with a link to a fake sign-in page.
- A shared-document or e-signature request from a compromised contact that leads to a credential-harvesting page.
- A security alert about a login from an unfamiliar country that asks you to "secure your account".
- A billing or renewal notice with a phone number to call for a refund.
Red flags
- The sign-in page is on a domain you do not recognise, even if the logo and layout look perfect.
- A document or voicemail arrives from a colleague you were not expecting to hear from.
- The message pushes you to sign in immediately instead of going to the service yourself.
Real Amazon Web Services domains
If the address in your browser is not one of these (or a subdomain of them), it is not Amazon Web Services. The list is not exhaustive.
aws.amazon.comamazonaws.comIf you already clicked or entered details
Change the password from a clean device, sign out all sessions, review mailbox rules and connected apps for anything you did not create, and turn on multi-factor authentication. Tell your IT team, because stolen mailbox logins are often used to attack colleagues next.
Protecting a brand like Amazon Web Services from lookalike domains
If you run security, brand or fraud for a company that is copied this way, this is the order that works in practice:
- Enforce DMARC. Move your policy to quarantine, then reject, so attackers cannot send mail that passes as your domain.
- Watch new registrations. Lookalikes appear daily; the earlier you see one, the sooner you can act, ideally before the first email goes out.
- Register the obvious typos and keyword variants you can afford to hold, and check which lookalikes are already registered by someone else.
- Report fast. A live fake needs a request to the registrar and host, plus a report to browser safe-browsing lists and the public feeds shown above.
- Tell your customers where you will and will not ask for logins, codes or payments.
Protect your brand from lookalike domains
Amazon Web Services is one of 2108 brands in this index, but attackers copy any company whose customers log in or pay. PhishPin checks your domain for registered lookalikes, email-spoofing gaps and listings in these same phishing feeds, then helps you get the fakes taken down.
Audits use public data only – we never touch your servers. Results within 24 hours.
Questions about Amazon Web Services phishing
How can I tell if a message from Amazon Web Services is phishing?
Check the sender and link domain first. The sign-in page is on a domain you do not recognise, even if the logo and layout look perfect. A document or voicemail arrives from a colleague you were not expecting to hear from. The message pushes you to sign in immediately instead of going to the service yourself. When in doubt, do not use the link: type aws.amazon.com into your browser or open the official app.
How many Amazon Web Services phishing sites has PhishPin found?
As of 7 Nov 2026, 5 hostnames referencing Amazon Web Services appear in the phishing feeds PhishPin indexes (8 reported URLs). These are reported hostnames, not a count of sites that are online today; many are removed quickly and some matches are coincidental.
What do fake Amazon Web Services domains look like?
In our data, the most common ending for reported hosts is .com. The brand is most often combined with the word "signin". 4 hosts put the brand name in a subdomain of an unrelated site. Always read the part of the address just before the first single slash: that is the real site. Real Amazon Web Services addresses end in aws.amazon.com.
What should I do if I entered my details on a fake Amazon Web Services page?
Change the password from a clean device, sign out all sessions, review mailbox rules and connected apps for anything you did not create, and turn on multi-factor authentication. Tell your IT team, because stolen mailbox logins are often used to attack colleagues next.
How do I report a fake Amazon Web Services website or message?
Forward phishing emails to reportphishing@apwg.org, report scams at reportfraud.ftc.gov, and report the page to Google Safe Browsing. Also tell Amazon Web Services through the contact options on its official website (aws.amazon.com).
Is it safe to visit the domains listed on this page?
No. They are shown defanged, with dots in brackets, so they cannot be clicked by accident. Do not type them into a browser. Listings are warnings from automated matching, and some are harmless coincidences. Treat everything listed as potentially phishing, infected or malware, and have a certified security expert review any list before you block, import or act on it. PhishPin is not responsible for loss or damage from using this data.
How does PhishPin find lookalike domains of Amazon Web Services?
We read the daily list of newly registered domains (1,050,000 domains over the last 15 days) and flag those that contain the brand name, differ by one character or swap look-alike characters. A match is a warning sign, not proof of abuse.
How can a company protect its own brand from lookalike domains like these?
Publish an enforced DMARC policy so nobody can send mail as your domain, monitor newly registered domains that resemble your name, register the obvious typo domains, and file takedown requests with the registrar, host and browser safe-browsing lists when a fake goes live. PhishPin's free brand audit checks the first three for your domain.
Other tech, email & cloud being impersonated
All tech, email & cloud brands ranked