Security engines reporting a detection: 2. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
The domain fxrmay-a73jotc0.vercel.app returned an HTTP 404 status during a check on 2026-10-01, indicating that no content was found at the requested URL at that time. A separate performance evaluation on 2026-09-03 recorded a PageSpeed score of 100, reflecting optimal technical performance for the domain.
Recorded Evidence
On 2026-10-01, fxrmay-a73jotc0.vercel.app was listed on two external blocklists: MetaMask and SEAL. VirusTotal reported 3 detections out of 90 scanners during its check on 2026-09-04. The domain was first observed on 2026-08-26, and a PageSpeed check was completed on 2026-09-03.
Interpretation
Each source provides a distinct record about fxrmay-a73jotc0.vercel.app, with blocklist entries and VirusTotal detections reflecting separate evaluations. The HTTP 404 status only describes the response recorded on 2026-10-01 and does not indicate the domain's content or availability at other times. The chronology of checks shows multiple perspectives but does not establish any trend or change between observations.
Recommended Actions
For fxrmay-a73jotc0.vercel.app, retain the MetaMask and SEAL blocklist listings and the VirusTotal detection results for ongoing monitoring. Compare future HTTP responses to the recorded 404 status for this domain. Keep the PageSpeed performance score for reference, and ensure all source records are preserved for separate review.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-13 10:06:08 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-13 10:06:08 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.
Technologies · 2 identified
V
Vercel
PaaS
Vercel is a cloud platform for static frontends and serverless functions.
Last analyzed First positive detection Previous stored snapshot: 3 detections
alphaMountain.ai
Forcepoint ThreatSeeker
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of fxrmay-a73jotc0.vercel.app· checked Sep 3, 2026
100
Good
Performance
FCP
0.79s
First Contentful Paint
LCP
0.79s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.79s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Domain Status Transition2026-10-09 01:22:58 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-09-03 01:00:25 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-02 23:13:12 UTC
Domain ingestion complete. Initial state is marked as alive.
Threat Response Pipeline
Discovery
Analysis
Monitoring
9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
fxrmay-a73jotc0.vercel.app detected and queued for full analysis
Aug 26, 2026
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
The domain remains reachable or access-restricted; future checks may update this observation.
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+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
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.
1 evidence signal groups linked0 reports recordedLast known active
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
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 →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · fxrmay-a73jotc0.vercel.app
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches4
Same favicon hash or the same page title as this host.
(US)
