Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 21/92 engines flagged. malicious: 21. suspicious: 0. Analysis time (as stored): 2026-10-23T10:50:16Z. Retrieved (as stored): 2026-11-04T07:41:23Z. Listed by external blocklists: Phishunt, PhishFeed. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
theamazon.vercel.app favicon

theamazon.vercel.app

In short

On 2026-11-03, theamazon.vercel.app displayed a page styled like an Amazon shopping homepage. The header shows the Amazon logo, a delivery location set to Nepal, a search bar, account and cart links, and a navigation row with Today's Deals, Customer Service, Registry, Gift Cards, and Sell. A banner reads "Find gifts for dads who have it all" alongside product imagery, and a notice states "You are on amazon.com" with a link to shop on Amazon Nepal. Category tiles below include Clothes, Health & Personal Care, Furniture, and Electronics.

“Amazon-Clone”

Review the evidence
Registrar
United StatesVercel
Resolved IP
United States216.198.79.131Amazon.com, Inc. · CDN
First observed
Nov 3, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 21/92 Stored blocklist matches: 2 Google Safe Browsing: threat flag recorded
VirusTotal
21 / 92
engine detections ·
Google Safe Browsing
Flagged
Blocklist matches
2
Phishunt, PhishFeed
URLScan
Malicious
Page captures
7
open gallery
Nov 3, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded theamazon.vercel.app on 2026-11-03. Stored VirusTotal result: 21/92 engines flagged. malicious: 21. suspicious: 0. Analysis time (as stored): 2026-10-23T10:50:16Z. Retrieved (as stored): 2026-11-04T07:41:23Z. Google Safe Browsing flags it. Risk: critical (100/100). Registrar: Vercel. Status: Last known active. Hosting: Amazon.com, Inc. Listed by external blocklists: Phishunt, PhishFeed. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
21 / 92
Blocklist matches
2
Hosting
United States216.198.79.131Amazon.com, Inc. · CDN
Registrar
United StatesVercel
Page captures
7
Page captures Source results Registration record

Capture recorded with this analysis · URLScan · 2026-11-03T18:26:29Z
SHA-256: 74aa52b8e5ee78add65f6dd7f174d7e75e9604f801652c58ec47ae8196813888

PhishDestroy analysis, reviewed version

On 2026-11-03, theamazon.vercel.app displayed a page styled like an Amazon shopping homepage. The header shows the Amazon logo, a delivery location set to Nepal, a search bar, account and cart links, and a navigation row with Today's Deals, Customer Service, Registry, Gift Cards, and Sell. A banner reads "Find gifts for dads who have it all" alongside product imagery, and a notice states "You are on amazon.com" with a link to shop on Amazon Nepal. Category tiles below include Clothes, Health & Personal Care, Furniture, and Electronics.

The stored VirusTotal domain result reports 21 detections out of 92 engines. DNS8 reported "phishing"; ESET reported "phishing".

Source evidenceVirusTotal 21 / 92 · Google Safe Browsing: flagged 8 sources

VirusTotal

21 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
43
Malicious
21
Suspicious
0
Undetected
28

Vendor labels

DNS8
phishing
ESET
phishing
Ermes
phishing
VIPRE
malware
G-Data
phishing
Lionic
phishing
Sophos
phishing
Certego
phishing
CyRadar
phishing
Webroot
malicious
Emsisoft
phishing
Fortinet
phishing
Netcraft
malicious
SOCRadar
phishing
URLQuery
malicious
Kaspersky
phishing
LevelBlue
phishing
Gridinsoft
phishing
BitDefender
phishing
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Registrar

Tucows Domains Inc

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    A
    Value
    216.198.79.3
  • TTL, seconds
    300
    Type
    A
    Value
    64.29.17.3

DNS records observed

JARM fingerprint

3fd3fd00000000000043d43d00043dc3b2afa8a5ec09b510a8559aff7899fb

Certificate

Subject alternative names
  • *.vercel.app
Issuer
Google Trust Services / WR1
Serial
f7911168ffa7d0f4135e24792e7a52a8
SHA-256
8f46c4a0a289bfde4060d06986f2af761ee62d668dde972e6bef4687ee4f6093
Subject
*.vercel.app
Valid until
Valid from

Registration record

Registrar
Tucows Domains Inc
Registrar IANA ID
69
Registrar URL
http://www.tucows.com
Registered
Updated
Expires
Status
  • clientTransferProhibited
  • clientUpdateProhibited
Nameservers
  • ns1.vercel-dns-3.com
  • ns2.vercel-dns-3.com
  • ns3.vercel-dns-3.com
  • ns4.vercel-dns-3.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 43,
    "malicious": 21,
    "suspicious": 0,
    "undetected": 28
}
Vendor labels
{
    "DNS8": "phishing",
    "ESET": "phishing",
    "Ermes": "phishing",
    "VIPRE": "malware",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "Certego": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Emsisoft": "phishing",
    "Fortinet": "phishing",
    "Netcraft": "malicious",
    "SOCRadar": "phishing",
    "URLQuery": "malicious",
    "Kaspersky": "phishing",
    "LevelBlue": "phishing",
    "Gridinsoft": "phishing",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Registrar
Tucows Domains Inc
Created
2020-01-28T03:03:04Z
Expires
2026-01-28T03:03:04Z
Updated
2025-01-26T03:25:55Z
First seen
2026-08-27T17:37:54Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "216.198.79.3"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "64.29.17.3"
    }
]
Dns at
2026-10-23T10:55:35Z
Jarm
3fd3fd00000000000043d43d00043dc3b2afa8a5ec09b510a8559aff7899fb
Certificate
{
    "san": [
        "*.vercel.app"
    ],
    "issuer": "Google Trust Services / WR1",
    "serial": "f7911168ffa7d0f4135e24792e7a52a8",
    "sha256": "8f46c4a0a289bfde4060d06986f2af761ee62d668dde972e6bef4687ee4f6093",
    "subject": "*.vercel.app",
    "valid_to": "2026-11-27T19:48:08Z",
    "valid_from": "2026-08-29T19:48:09Z"
}
Registration record
{
    "registrar": "Tucows Domains Inc",
    "registrar_iana_id": "69",
    "registrar_url": "http://www.tucows.com",
    "created": "2020-01-28T03:03:04Z",
    "updated": "2025-01-26T03:25:55Z",
    "expires": "2026-01-28T03:03:04Z",
    "status": [
        "clientTransferProhibited",
        "clientUpdateProhibited"
    ],
    "nameservers": [
        "ns1.vercel-dns-3.com",
        "ns2.vercel-dns-3.com",
        "ns3.vercel-dns-3.com",
        "ns4.vercel-dns-3.com"
    ],
    "dnssec": "unsigned"
}
Separate collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

source
VirusTotal
scope
unknown
result_state
observed
numerator
21
denominator
92
malicious
null
suspicious
null
vendors
["alphaMountain.ai","BitDefender","Certego","CyRadar","DNS8","Ermes","ESET","Emsisoft","Forcepoint ThreatSeeker","Fortinet","G-Data","Gridinsoft","Kaspersky","LevelBlue","Lionic","Netcraft","SOCRadar","Sophos","URLQuery","VIPRE","Webroot"]
observed_at
2026-10-23 10:50:16
checked_at
2026-11-04 08:41:25
fetched_at
2026-11-04 07:41:25
time_basis
as stored; legacy timezone not established

Google Safe Browsing

Threat flag recorded

Open report

URLScan

Malicious

SHA-256 fb5ab75ded2406d08dbefe04affade04c9a287fd92ca3bb17340bc38b9824ce8

Open report
URLScanOriginal source recordObserved: 19 fields

Observed: · Retrieved:

Report ID

01a1a2a9-7d1f-7109-b8c9-b729311e6d21

Final URL

https://theamazon.vercel.app/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://theamazon.vercel.app/
    From
    http://theamazon.vercel.app/
    Status
    307

IP address

64.29.17.195

Contacted domains

  • cdnjs.cloudflare.com

Contacted IP addresses

  • 104.17.25.14
  • 64.29.17.195

Autonomous systems (ASN)

  • 13335
  • 16509

Server countries

  • US

Document hash

2ad43f47680f7b7a2ae401001cde2a8da5c4e3d9a937b0450862765bd5e770d4

TLS session and certificate

Subject alternative names
  • *.vercel.app
Cipher
AES_128_GCM
Issuer
WR1
Subject
*.vercel.app
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

74

Registered domain age, days

74

Certificate age, days

3

Certificate validity, days

89

Page requests

15

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-2aab354
Score
100
Malicious
Yes
Overall verdict
Tags
  • phishing
Score
100
Brands
  • amazon
Malicious
Yes
Categories
  • phishing
URLScan verdict
Tags
  • phishing
Score
100
Brands
  • Amazon
Malicious
Yes
Categories
  • phishing

HTTP headers

Server
Vercel
Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=63072000; includeSubDomains; preload
Original source fields · JSON
Uuid
01a1a2a9-7d1f-7109-b8c9-b729311e6d21
Final url
https://theamazon.vercel.app/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://theamazon.vercel.app/",
        "from": "http://theamazon.vercel.app/",
        "status": 307
    }
]
Ip
64.29.17.195
Contacted domains
[
    "cdnjs.cloudflare.com"
]
Contacted IP addresses
[
    "104.17.25.14",
    "64.29.17.195"
]
Asns
[
    "13335",
    "16509"
]
Countries
[
    "US"
]
Document hash
2ad43f47680f7b7a2ae401001cde2a8da5c4e3d9a937b0450862765bd5e770d4
Tls
{
    "san": [
        "*.vercel.app"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WR1",
    "subject": "*.vercel.app",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-29T11:46:09Z",
    "valid_from": "2026-10-31T11:46:10Z"
}
Domain age days
74
Apex age days
74
Tls age days
3
Tls valid days
89
Requests
15
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-2aab354"
        ],
        "score": 100,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "amazon"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Amazon"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "Vercel",
    "content-type": "text/html; charset=utf-8",
    "strict-transport-security": "max-age=63072000; includeSubDomains; preload"
}
Separate monitor record · 2026-11-08 04:30 UTC

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

record_source
domain_monitor.urlscan
uuid
01a1a2a9-7d1f-7109-b8c9-b729311e6d21
score
100
malicious
true
result_at
2026-11-08T04:30:58Z
enriched_at
2026-11-04T09:10:56Z
source_timestamps
{"urlscan_result_at":"2026-11-08 05:30:58","urlscan_enriched_at":"2026-11-04 10:10:56"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

10 / 100 · heuristic score · 1 brand reference · 0 classifications

Open report
Separate monitor score · 10 / 100 · 2026-11-04T07:20:14Z

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

record_source
domain_monitor.dom_analysis
heuristic_score
10
analyzed_at
2026-11-04T07:20:14Z
source_timestamp
2026-11-04 08:20:14
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

ai_title
theamazon.vercel.app: Recorded Amazon-Style Shopping Homepage
ai_description
PhishDestroy records the page at theamazon.vercel.app showing an Amazon-branded shopping homepage with category tiles, a search bar, and a gift banner.
ai_summary
On 2026-11-03, theamazon.vercel.app displayed a page styled like an Amazon shopping homepage. The header shows the Amazon logo, a delivery location set to Nepal, a search bar, account and cart links, and a navigation row with Today's Deals, Customer Service, Registry, Gift Cards, and Sell. A banner reads "Find gifts for dads who have it all" alongside product imagery, and a notice states "You are on amazon.com" with a link to shop on Amazon Nepal. Category tiles below include Clothes, Health & Personal Care, Furniture, and Electronics. The stored VirusTotal domain result reports 21 detections out of 92 engines. DNS8 reported "phishing"; ESET reported "phishing".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-04 09:13:30
revision
282f624906e6951821b6cc5f086b617914ea724831fdfd228d5733e8e631ab15
mode
reviewed
interpretation
Selected public package; text generation time is separate from source observation dates.

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 22 fields

Mail configuration

SPF lookups
0

CAA records

Count
2
Domain
vercel.app
Allowed issuers
  • letsencrypt.org
  • pki.goog

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
1
Average page size, bytes
2501

Page title and metadata

Page title
Amazon-Clone

Trackers

Requests
13
Observed services
  • Name
    Cloudflare
    Company
    Cloudflare
    Country
    US
    Category
    Hosting
    Requests
    1

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
46
TLS
13
Waiting
27
Connection
12
Download
0
Response time, ms
98

TLS connection

ALPN
h2
Cipher
TLS_AES_128_GCM_SHA256
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443

Carbon estimate

Bytes
6409
CO₂, grams
0.0002
Cleaner than, %
81

DNS servers

Nameservers
  • IP address
    205.251.197.116
    Host
    ns3.vercel-dns-3.com
  • IP address
    205.251.199.60
    Host
    ns4.vercel-dns-3.com
  • IP address
    205.251.193.92
    Host
    ns1.vercel-dns-3.com
  • IP address
    205.251.194.149
    Host
    ns2.vercel-dns-3.com
DNS zone
vercel.app

Location

IP address
64.29.17.3
ASN
16509
Organization
Amazon.com, Inc.
City
Walnut
Country
US

TLS certificate

Issuer
Google Trust Services / WR1
Subject
*.vercel.app

DNS records

A
  • 64.29.17.3
  • 216.198.79.3

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header value
max-age=63072000; includeSubDomains; preload
Observation
Site is compatible with the HSTS preload list!
Preload compatible
Yes

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
max-age=63072000; includeSubDomains; preload
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
216.198.79.3
IP version
4

Redirects

Redirect chain
  • https://theamazon.vercel.app

Technology stack

Technologies
  • Vercel
  • Cloudflare
  • Font Awesome
  • cdnjs
  • HSTS

HTTP headers

Response headers
Server
Vercel
Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=63072000; includeSubDomains; preload
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "count": 2,
    "domain": "vercel.app",
    "issuers": [
        "letsencrypt.org",
        "pki.goog"
    ]
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-14T16:17:40Z",
    "first": "2026-10-14T16:17:40Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 2501
}
Page title and metadata
{
    "title": "Amazon-Clone"
}
Trackers
{
    "requests": 13,
    "trackers": [
        {
            "name": "Cloudflare",
            "company": "Cloudflare",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        }
    ]
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 46,
        "tls": 13,
        "wait": 27,
        "connect": 12,
        "download": 0
    },
    "response_ms": 98
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_128_GCM_SHA256",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 6409,
    "co2_grams": 0.0002,
    "cleaner_than": 81
}
Dns server
{
    "ns": [
        {
            "ip": "205.251.197.116",
            "host": "ns3.vercel-dns-3.com"
        },
        {
            "ip": "205.251.199.60",
            "host": "ns4.vercel-dns-3.com"
        },
        {
            "ip": "205.251.193.92",
            "host": "ns1.vercel-dns-3.com"
        },
        {
            "ip": "205.251.194.149",
            "host": "ns2.vercel-dns-3.com"
        }
    ],
    "zone": "vercel.app"
}
Location
{
    "ip": "64.29.17.3",
    "asn": "16509",
    "org": "Amazon.com, Inc.",
    "city": "Walnut",
    "country": "US"
}
Ssl
{
    "issuer": "Google Trust Services / WR1",
    "subject": "*.vercel.app"
}
DNS records
{
    "A": [
        "64.29.17.3",
        "216.198.79.3"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=63072000; includeSubDomains; preload",
    "message": "Site is compatible with the HSTS preload list!",
    "compatible": true
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": "max-age=63072000; includeSubDomains; preload",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "216.198.79.3",
    "family": 4
}
Redirects
{
    "chain": [
        "https://theamazon.vercel.app"
    ]
}
Tech stack
{
    "technologies": [
        "Vercel",
        "Cloudflare",
        "Font Awesome",
        "cdnjs",
        "HSTS"
    ]
}
HTTP headers
{
    "headers": {
        "server": "Vercel",
        "content-type": "text/html; charset=utf-8",
        "strict-transport-security": "max-age=63072000; includeSubDomains; preload"
    }
}

Questions about theamazon.vercel.app

Is theamazon.vercel.app legit?

PhishDestroy rates theamazon.vercel.app as critical risk (100/100) from the recorded evidence; it was first recorded on 2026-11-03. Stored VirusTotal result: 21/92 engines flagged. malicious: 21. suspicious: 0. Analysis time (as stored): 2026-10-23T10:50:16Z. Retrieved (as stored): 2026-11-04T07:41:23Z. Google Safe Browsing flags it. Listed by external blocklists: Phishunt, PhishFeed. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is theamazon.vercel.app safe to connect a wallet?

This report does not record which wallet requests theamazon.vercel.app makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.

What should I do if I used theamazon.vercel.app?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy · Phishunt · PhishFeed · no match in the other 9 3
PhishDestroy PhishDestroy list View source
Phishunt Listed View source
PhishFeed Listed View source

Checked, no match

Last checked

Stored Capture · 7 captures

URLScan · 2026-11-03 1 / 7 Used in the analysis Source file SHA-256: 74aa52b8e5ee78add65f6dd7f174d7e75e9604f801652c58ec47ae8196813888 SHA-256 of the prepared copy given to the model: 415b6093d15b0e1d4e9542c94cd5d37b4645496a68317c03b2b8f416254d8abe
SourceURLScan · 2026-11-03
Recorded
StateStored capture
HTTP status200
Final URLhttps://theamazon.vercel.app/
Position1 / 7
Open capture Source Report Wayback Download
All capture links and hashes (7)

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Amazon report ↗
Google Safe Browsing Flagged Social engineering checked Nov 7, 2026
IP Context United States216.198.79.131 Vercel shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider Vercel US(US)
Abuse contactabuse@vercel.com
Hosting abuse contact abuse@vercel.com Amazon.com, Inc. · AS16509
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedNov 3, 2026
DOM Analysisanalyzed Nov 4, 2026score 10/1001 brand signal
Submitted URLhttp://theamazon.vercel.app/
Observed page title
Amazon-Clone
Automated brand references
Amazon
TLS Certificate
Issued by WR1 · stored validity ends in 82 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United States216.198.79.131
Network ASN
AS16509
AS name
AMAZON-02 - Amazon.com, Inc., US
Organization
Amazon.com, Inc.
Observed location
United StatesWalnut, US
Server header
Vercel

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

Issuer
WR1
Valid from
2026-10-31 11:46:10
Valid until
2027-01-29 11:46:09
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint8f46c4a0a289bfde4060d06986f2af761ee62d668dde972e6bef4687ee4f6093
Certificate names · 1 SAN
  • *.vercel.app

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 216.198.79.131rapiddns.io

Latest Classified Outcome 2026-11-07 23:12:15 UTC

The site was serving its pages at the latest check.

Technical details
Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Stale Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-11-07 23:12:15 UTC
RDAP registration
Observed timeline last reachable: 2026-11-07 11:10:50 UTC last content: 2026-11-07 11:10:50 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

21 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 21 detections
DNS8
ESET
Ermes
VIPRE
G-Data
Lionic
Sophos
Certego
CyRadar
Webroot
Emsisoft
Fortinet
Netcraft
SOCRadar
URLQuery
Kaspersky
LevelBlue
Gridinsoft
BitDefender
alphaMountain.ai
Forcepoint ThreatSeeker
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Captured network requests

Network requests: 15 SHA-256 hashes: 15 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-03 18:28 UTC.

Open this scan on URLScan 01a1a2a9-7d1f-7109-b8c9-b729311e6d21 ↗

Stored observation history4

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    live_content

    content_served

  2. Availability monitor · Recorded state

    protected

    http_access_restricted · access_restriction

  3. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

  4. Domain monitor · First collection record

    Reachable

All retained availability observations13

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-08 00:12:15.000000
    Evidence SHA-256
    c4dfb29041ec1d1b5f134bea3f39196822f9fed3730b34181fff4784b9fb0c03
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-08 00:12:15
    Evidence reason
    alive_content
  2. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-07 12:10:50.000000
    Evidence SHA-256
    51e8dddd7693f36b154abb6926db33ede8c999eaa51b3666e1294c50826698c1
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 12:10:50
    Evidence reason
    alive_content
  3. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-07 12:10:50.000000
    Evidence SHA-256
    51e8dddd7693f36b154abb6926db33ede8c999eaa51b3666e1294c50826698c1
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 12:10:50
    Evidence reason
    alive_content
  4. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-07 03:50:08.000000
    Evidence SHA-256
    075273c86c7e9824a9dbed1b5a82e7b8be38ee69849ec69d9c277a9a105f137f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 03:50:08
    Evidence reason
    alive_content
  5. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-07 03:50:08.000000
    Evidence SHA-256
    075273c86c7e9824a9dbed1b5a82e7b8be38ee69849ec69d9c277a9a105f137f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 03:50:08
    Evidence reason
    alive_content
  6. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-07 00:01:32.000000
    Evidence SHA-256
    0251c258d752b01a2c7b809da3b806f2133abcdfadf5e34bb417602529478393
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 00:01:32
    Evidence reason
    alive_content
  7. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-07 00:01:32.000000
    Evidence SHA-256
    0251c258d752b01a2c7b809da3b806f2133abcdfadf5e34bb417602529478393
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 00:01:32
    Evidence reason
    alive_content
  8. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-05 01:01:31.000000
    Evidence SHA-256
    4139e9e3aa25ccb7d7a5de9a76b881196cd8f42416dc485b157ac73101f101bd
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-05 01:01:31
    Evidence reason
    alive_content
  9. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-05 01:01:31.000000
    Evidence SHA-256
    d4680ecc04c72047fa086f5c985fb5181baaa4f0e30fe96208d3be90ff721459
    Evidence timestamp as recorded
    2026-11-05 01:01:31
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  10. current_http_probeprotected
    Observation source
    current_http_probe
    Cause
    http_access_restricted
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    403
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Mechanism
    access_restriction
    Monitor confidence
    50
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-04 13:03:07.000000
    Evidence SHA-256
    a002e416345b7508bbab9421bb0df71501d5510dc445ea5c12407759cef0c649
    HTTP probe value as recorded
    403
    Evidence timestamp as recorded
    2026-11-04 13:03:07
    Evidence reason
    alive_content
  11. http_observationprotected
    Observation source
    http_observation
    Cause
    http_access_restricted
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    403
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Mechanism
    access_restriction
    Monitor confidence
    50
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-04 13:03:07.000000
    Evidence SHA-256
    a002e416345b7508bbab9421bb0df71501d5510dc445ea5c12407759cef0c649
    HTTP probe value as recorded
    403
    Evidence timestamp as recorded
    2026-11-04 13:03:07
    Evidence reason
    alive_content
  12. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-03 19:26:48.000000
    Evidence SHA-256
    5052a743836b4bdfc3fe58fbe26715eb0a5ac6234c73a9c6bc3ed5133c6feb16
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-03 19:26:48
    Evidence reason
  13. http_observationunknown
    Observation source
    http_observation
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-03 19:26:48.000000
    Evidence SHA-256
    5052a743836b4bdfc3fe58fbe26715eb0a5ac6234c73a9c6bc3ed5133c6feb16
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-03 19:26:48
    Evidence reason

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · in progress

Recorded events: 11. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested Recorded: 1 of 1
  • Threat Ingested
    theamazon.vercel.app detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Google Safe Browsing · Blocklist Detection · Automated brand label: Amazon · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 9 of 9
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan classified the page as malicious · Score: 100
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • VirusTotal
    Detections recorded on VirusTotal: 21/92
  • Google Safe Browsing
    Listed as unsafe by Google Safe Browsing (Google Transparency Report)
  • Blocklist Detection
    Found in blocklists: Phishunt, PhishFeed
  • Automated brand label: Amazon
    Collector label, not confirmed by a page check.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

4 entries
  1. Google Safe Browsing

    Threat flag recorded

    View source
  2. Added to PhishDestroy

    theamazon.vercel.app

    View source
  3. URLScan

    Page captured

    View source
  4. VirusTotal

    21/92 engine detections

    View source
How we investigate & report

Public scans, evidence and abuse channels

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.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation
All stored records by source

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

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

theamazon.vercel.app

Evidence & External Reports

Security Analysis
URLScan Malicious VirusTotal 21 det. ChainPatrol URLQuery Google SB Flagged SSL Labs Stored certificate dates valid CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked Last known active
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.

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.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
More official reporting routes
FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

Template-based draft • optional AI wording assistance requires separate consent

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including theamazon.vercel.app)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?
  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?
  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?
  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
About this reportSources, observation dates and corrections

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.

Request a correction or appeal How PhishDestroy works
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/theamazon.vercel.app"
  title="PhishDestroy threat report for theamazon.vercel.app"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>