Skip to main content
Sandfish

Amazon Web Services Sign-In

https://us-east-1.signin-aws-console.com/signin?client_…

Group60d0feb3-941c-4090-a51e-bd709bf65253submitted urlMember 1

Results

Rules engine

AI review

AI case description

Phishing

The page uses AWS branding and collects root/IAM credentials and an MFA code at signin-aws-console.com, then the session ends at an AWS contact-form confirmation page. The supplied evidence does not establish whether the sign-in domain is an authorized AWS authentication service or show credential handling beyond successful submissions.

Findings

Analyzed page

Language
Detecting...

Infrastructure

Domain registration
signin-aws-console.com0-7 days oldRegistered 2026-11-19 · Registrar Spaceship, Inc.
Hosting
Loading...

Capture activity

Cookies
8 observed
Interaction
10 actions · 5 submissions · stopped: submission limit · download stage: left submitted site
  1. 1. fillsucceededtext | username | IAM username |
  2. 2. fillsucceededpassword | password | Password |
  3. 3. submitsucceededSign in
  4. 4. submitsucceededSign in using root user email
  5. 5. fillsucceededemail | resolvingInput | Email address | [email protected]
  6. 6. submitsucceededNext
  7. 7. fillsucceededpassword | password | Password |
  8. 8. submitsucceededSign in
  9. 9. fillsucceededtext | mfaCode | MFA code | enter code
  10. 10. submitsucceededSign in
Kit source work

Loading related source work…

Discover or upload kit source

Analysis metadata

How and when the analysis ran.

Processing status
Evidence coverage
Input kind
url
Execution kind
capture
Duration
1.7m
Navigation
4 navigations
Engine version
0.4.2
Created
2026-11-20 04:03:03Z
Started
2026-11-20 04:03:05Z
Finished
2026-11-20 04:04:47Z
Archive
4.2 MB
Favicon source
html_link / favicon-v7
Analysis ID
1fd9cf38-947e...

Document-source diagnostics

These records identify rejected document reads. A current epoch does not prove that a replacement read succeeded. Later success does not erase an earlier evidence limit.

No rejected document reads were recorded.

Browser-observed navigation status

The browser status can differ from the normalized origin response, including during a proxy failure. Inspect the recorded document request for origin response evidence.

Showing 0–0 of 0

Signals by severity

Detected findings grouped by risk

Request activity

Network requests grouped by resource type

Behavior

Recorded actions grouped by type

Network contacts

Requests to the most active hosts

Request ownership

First-party and third-party requests

Response MIME types

Network responses grouped by MIME type