VirusTotal
18 / 89
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
“Sign in to your account”
Assessment based on the stored source evidence below. Review sources →
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
18 / 89
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
provider verdict: malicious
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
malicious
ReportThis is the recorded automated analysis. Completion alone is not a safety verdict.
no community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
stored report
View stored capture ↗ ReportA preserved page image documents what the collector received; a capture is not a safety verdict.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
0 external matches
DetailsA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.
excel-micro.wasmer.app returned an HTTP 200 status code on 2026-10-01, a recorded response for that date. The same domain also appeared on the PhishFeed external blocklist, and a PageSpeed performance score of 100 was recorded on 2026-09-11.
On 2026-10-01, excel-micro.wasmer.app was recorded with an HTTP 200 status. PhishFeed listed the domain as an external blocklist entry. VirusTotal reported 18 detections across 89 scanners on 2026-09-20. The SSL certificate, issued by Let's Encrypt / YE1, was scanned on 2026-09-11. The domain was first observed on 2026-09-11, when PageSpeed recorded a performance score of 100.
The PhishFeed listing and the VirusTotal detection count are separate source observations that a reader can compare against later checks. The HTTP 200 response and the PageSpeed score describe different measurements taken on different dates, so they should not be combined into a single judgment. The first-observed date and the SSL scan date fall on the same calendar day, but that alone does not establish that the measurements were simultaneous.
Preserve the PhishFeed listing and the VirusTotal record for excel-micro.wasmer.app so future checks can be compared against them. Retain the HTTP response record and the PageSpeed score as separate items for later review. Compare each preserved source record against new observations of the same source rather than against one another.
19 · datasets with records / 12 · not recorded
What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.
These checks have no retained result. This does not mean they passed or that a scan is running.
0 · external source matches
Wasmer · 62.210.172.150 · DNS, TLS and retained responses
For the registrable domain wasmer.app behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
beta.ns.wasmernet.comLocation describes the IP network.
b22cbf855d708f012eaa0a3c4a93d9a90348d61bd926cf938f38954f00a626e6Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of excel-micro.wasmer.app · checked Sep 11, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Stored browser and crawler observations
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: dead_http: raw=http_410; http=410; via=https_proxy
Collection history, report status and investigation channels
62.210.172.150.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
inactive→Unknown
probe_inconclusive
Unknown→inactive
http_no_content
inactive→Unknown
probe_inconclusive
Unknown→inactive
http_no_content
inactive→Unknown
probe_inconclusive
Unknown→inactive
http_no_content
inactive→Unknown
probe_inconclusive
Unknown→inactive
http_no_content
inactive→Unknown
probe_inconclusive
Unknown→inactive
http_no_content
inactive→Unknown
probe_inconclusive
Unknown→inactive
http_no_content
Reachable→Unavailable
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
Unknown
probe_inconclusive
Unknown
14 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Shared hosting, registrar records and related domains
Original reports, independent checks and evidence links
Recovery steps, reporting contacts and complaint drafts
Listed domains receive at least one abuse report; this entry has no retained notification history.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Choose 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 ↗
excel-micro.wasmer.app)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
Stored evidence snapshot. Source timestamps appear where available.
Captured title: “Sign in to your account”. Apparent target: Excelpdfdownload.
VirusTotal detections for excel-micro.wasmer.app: 18 (2026-09-20 02:15:17 UTC).
Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.
submit an appeal or review the FAQ page.