Cloudflare Radar
Phishing
Open reportaws-amzon.info presents a consulting team named Aws-amzon Cloud offering migration services while inviting visitors to initiate contact. MetaMask and SEAL block it, so avoid sharing corporate emails, credentials, or project specifications through their contact channels.
Page title: “Aws-amzon — Cloud Solutions & AWS Consulting”
Listed by external blocklists: MetaMask, SEAL. Use caution — do not enter credentials or personal information.
Risk score, higher = worse · How this score works
Pick what happened and tick the steps as you go. The ticks are kept only in this browser.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@name.com. The latest stored availability evidence still shows the domain reachable; 36 hours has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
URLScan capture · 2026-11-20 20:31 UTC · SHA-256 e1cbba43…959cc2b
PhishDestroy analysis, reviewed version
The page displays a dark header reading "Aws-amzon Cloud" alongside links for Services, About, and Contact. The main headline states "We build, migrate and secure AWS infrastructure" followed by a description claiming the site represents a consulting team specializing in Amazon Web Services. A prominent orange button labeled "Get in touch" invites visitor interaction. Three service boxes detail offerings for "Cloud Migration", "DevOps & Automation", and "Security & Compliance" with blurbs about structured migration and IAM hardening. An "About us" block claims the team has delivered cloud projects across Europe and Asia. The footer lists a contact email address at info@aws-amzon.info and a copyright notice for Aws-amzon Cloud.
The domain mimics an established cloud provider using a misspelled brand variation in its address. It was registered on 20 Nov 2026 and reported the same day, exposing a clear mismatch with the textual claims of delivering international cloud projects for years. Because MetaMask and SEAL block it, security tools independently recognize the risk associated with this site. The domain was still reachable on 20 Nov 2026 at 21:32 UTC, maintaining its presence while operating under a registration through Name.com, Inc.
When visitors reach out to addresses like info@aws-amzon.info or submit project inquiries through simulated consulting forms, they risk exposing internal infrastructure details or corporate credentials to unauthorized operators. Pages of this type typically collect direct communications to launch targeted spear-phishing or business email compromise campaigns. Always verify cloud partners through official channels such as aws.amazon.com rather than trusting unverified look-alike domains.
Phishing
Open reportspam domain
Page capture
SHA-256 db25a527…d5edf0e
Separate stored monitor snapshot; does not replace the primary report record or establish current availability.
10 / 100 · heuristic score · 2 brand references · 0 classifications
Content heuristic only; not the final score
Open reportThis dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.
Narrative generation metadata
Open reportThe narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.
Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
Stored page, network and scanner observations, grouped by source and observation time.
| Mail configuration | Spf lookups: 0 |
|---|---|
| Protective DNS results | Resolvers: 12; Blocked count: 0 |
| DNS server | NS: (IP: 163.114.217.49; Host: ns4ghm.name.com), (IP: 163.114.216.17; Host: ns1fkl.name.com), (IP: 163.114.216.49; Host: ns2clp.name.com), (IP: 163.114.217.17; Host: ns3cfp.name.com); Zone: aws-amzon.info |
| Quality | Cls: 0; Seo: 91; Si s: 1.42; Fcp s: 0.76; Lcp s: 0.76; Tbt ms: 0; Performance: 100; Accessibility: 85; Best practices: 100 |
| Location | IP: 65.0.32.171; ASN: 16509; Org: Amazon.com, Inc.; City: Mumbai; Country: IN |
| DNS records | A: 65.0.32.171; NS: ns1fkl.name.com, ns4ghm.name.com, ns3cfp.name.com, ns2clp.name.com; Soa: Nsname: ns1.name.com; Hostmaster: hostmaster.nsone.net; Serial: 1795156265; Refresh: 43200; Retry: 7200; Expire: 1209600; Minttl: 3600 |
| Dnssec | Ds: ✗; Rrsig: ✗; Dnskey: ✗ |
| Get IP | IP: 65.0.32.171; Family: 4 |
| Redirects | Chain: https://aws-amzon.info |
| Tech stack | Technologies: Nginx, HSTS |
| Page links | Internal: https://aws-amzon.info/, https://aws-amzon.info/, https://aws-amzon.info/; Internal count: 3 |
The domain uses a misspelled variation of the brand name ("amzon") to resemble an authentic partner. Always use aws.amazon.com for official cloud services.
If you contacted info@aws-amzon.info through the provided email or contact form, you risk exposing your corporate email address, project requirements, or internal infrastructure details to unauthorized operators. MetaMask and SEAL block it. Do not share credentials or sensitive network data with them.
Security vendors flag the domain because MetaMask and SEAL block it. Furthermore, it was registered on 20 Nov 2026 and reported the same day.
Last checked
ns1fkl.name.comns2clp.name.comns3cfp.name.comns4ghm.name.comnsname: ns1.name.comhostmaster: hostmaster.nsone.netserial: 1795156265refresh: 43200retry: 7200expire: 1209600minttl: 3600Location describes the IP network.
3835ebec903cc20ef1721a7670ffd39682b0d978cf073cf9bcf500c4faccba3b273058916484.signin.aws.aws-amzon.info571390245812.signin.aws.aws-amzon.info618294705123.signin.aws.aws-amzon.info824106593471.signin.aws.aws-amzon.infoap-northeast-1.signin.aws.aws-amzon.infoap-south-1.signin.aws.aws-amzon.infoap-southeast-1.console.aws.aws-amzon.infoauth.aws-amzon.infoaws-amzon.infoaws.login.aws-amzon.infoSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
The site was serving its pages at the latest check.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
273058916484.signin.aws.aws-amzon.infoDomain record571390245812.signin.aws.aws-amzon.infoDomain record618294705123.signin.aws.aws-amzon.infoDomain record824106593471.signin.aws.aws-amzon.infoDomain recordap-northeast-1.signin.aws.aws-amzon.infoDomain recordap-south-1.signin.aws.aws-amzon.infoDomain recordap-southeast-1.console.aws.aws-amzon.infoDomain recordauth.aws-amzon.infoDomain recordconsole.aws.aws-amzon.infoDomain recordeu-central-1.signin.aws.aws-amzon.infoDomain recordeu-west-1.console.aws.aws-amzon.infoDomain recordeu-west-1.signin.aws.aws-amzon.infoDomain recordoidc.eu-west-1.aws-amzon.infoDomain recordsignin.aws.aws-amzon.infoDomain recordsignin.awsapps.aws-amzon.infoDomain recordus-east-1.console.aws.aws-amzon.infoDomain recordus-east-1.signin.aws.aws-amzon.infoDomain recordus-west-2.console.aws.aws-amzon.infoDomain recordus-west-2.signin.aws.aws-amzon.infoDomain recordGoogle PageSpeed Insights — mobile performance audit of aws-amzon.info ·
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://aws-amzon.info/https://aws-amzon.info/Server: nginxContent-Type: text/htmlContent-Encoding: gzipkeep-alivegziptext/htmlFri, 20 Nov 2026 20:33:12 GMTno-referrer-when-downgradenginxmax-age=31536000; includeSubDomainschunkednosniffValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Network requests: 2 SHA-256 hashes: 1 URLScan scan:
Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-20 20:32 UTC.
Open this scan on URLScan 01a1faa8-3d82-7307-bd27-de62d2f3edd7 ↗
Loads saved data; the suspicious site is not opened.
| # | Network request | HTTP method · status | Type | Uncompressed size | Response body SHA-256 |
|---|
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Serving page content
page content returned
Serving page content
page content returned
Reachable
Recorded events: 13. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Lifecycle
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.
Download all records as JSON| ID | Stored data |
|---|
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
aws-amzon.info PD-6A6369CC072DE978C002 Recipient: abuse@name.com Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.
The draft stays only with you.
First secure your money: call your bank or revoke wallet approvals. Immediate steps →
Emergency help from security researchers when a crypto wallet is being drained right now.
Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.
Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.
Forward scam emails and text messages to the National Cyber Security Centre, which takes down the malicious sites it finds.
Emailreport@phishing.gov.uk Text messages7726Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.
Forward phishing emails to the Anti-Phishing Working Group.
Emailreportphishing@apwg.orgNational Cyber Crime Reporting Portal. For financial fraud, also call the 1930 helpline straight away.
Helpline1930Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
aws-amzon.info)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.