VirusTotal
4 / 91
ReportInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“Save, Grow, Spend. Do more with your crypto | ether.fi”
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.
4 / 91
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
malicious
ReportThis is the recorded automated analysis. Completion alone is not a safety verdict.
3 external matches
DetailsA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
no community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
provider verdict: clean
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
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.
Stored narrative · generated . Provider checks below retain their own observation dates.
On 2026-10-01, oepyikr62somsy5uhrhbmfgfgpdmyyvvirudgvqwpymmaurgmsza.arweave.net returned an HTTP 451 status, recorded during an HTTP check. The same hostname appears on the PhishDestroy internal listing, and three external blocklists named MetaMask, ScamSniffer and SEAL also list it.
The first observation of this domain was logged on 2026-08-15, the same date as its PageSpeed check, which produced a performance score of 27. A certificate scan on 2026-08-16 recorded Let's Encrypt / YE1 as the issuer. VirusTotal, checked on 2026-09-29, reported 4 detections across 91 scanners. The external blocklist count of 3 was recorded on 2026-10-01, alongside the HTTP check. The IP address 37.19.194.80 is associated with DE and the organization Cdn77 FRA.
The MetaMask, ScamSniffer and SEAL listings and the PhishDestroy internal listing reflect observations made on different dates, so their counts and statuses describe separate snapshots rather than one synchronized measurement. Because the VirusTotal check on 2026-09-29 and the HTTP check on 2026-10-01 fall on different days, a reader can compare them only as dated records, not as a single current state. The PageSpeed score of 27 from 2026-08-15 and the SSL scan of 2026-08-16 likewise predate the later checks, so the sequence of dates matters when weighing these sources together.
Anyone reviewing oepyikr62somsy5uhrhbmfgfgpdmyyvvirudgvqwpymmaurgmsza.arweave.net should retain dated copies of each blocklist entry, the HTTP response and the VirusTotal result so later observations can be compared against them. Subsequent checks should be recorded with their own dates and source names, allowing changes in the external blocklist count or HTTP status to be tracked over time. During any review, avoid submitting passwords, payment details or other sensitive information to the domain, since the recorded HTTP 451 response and blocklist listings do not establish what the site currently serves.
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.
aurora.ns.cloudflare.comnitin.ns.cloudflare.comLocation describes the IP network.
7efd72e7f4f5b095ed480248d139f795b4e1ed856821c2f229ead69356808f4aarweave.netSaved 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 oepyikr62somsy5uhrhbmfgfgpdmyyvvirudgvqwpymmaurgmsza.arweave.net · checked Aug 15, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
CDN77-TurboScanner note: dead_http: raw=http_451; http=451; via=https_direct; server=CDN77-Turbo
37.19.194.80.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→blocked
http_451_blocked · http_451_unavailable
blocked→Unknown
probe_inconclusive
Unknown→blocked
http_451_blocked · http_451_unavailable
blocked→Unknown
probe_inconclusive
Unknown→blocked
http_451_blocked · http_451_unavailable
blocked→Unknown
probe_inconclusive
Unknown→blocked
http_451_blocked · http_451_unavailable
blocked→Unknown
probe_inconclusive
Reachable→Unavailable
live_content→blocked
http_451_blocked · http_451_unavailable
Unknown→live_content
content_served
Unavailable→Reachable
blocked→Unknown
probe_inconclusive
Unknown→blocked
http_451_blocked · http_451_unavailable
blocked→Unknown
probe_inconclusive
Unknown→blocked
http_451_blocked · http_451_unavailable
Unknown
probe_inconclusive
Reachable→Unavailable
Unavailable→Reachable
Reachable→Unavailable
Reachable
17 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.
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
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