Security engines reporting a detection: 4. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
On 2026-10-01, oelpugoqb7qzckmixbyxy5azestwojbi2p3x22r7cb74dg4hqkpa.arweave.net returned an HTTP 451 status. returned an HTTP 451 response, a recorded status from that check. The same domain appears on the MetaMask and SEAL external blocklists, and PhishDestroy holds an internal listing for it.
Recorded Evidence
VirusTotal recorded 4 detections across 91 scanners on 2026-08-23. The domain was first observed on 2026-08-17, when PageSpeed also measured a performance score of 82. An SSL scan on 2026-08-18 identified the issuer as Let's Encrypt / YE1, and the HTTP check on 2026-10-01 resolved to IP 212.102.56.179 in DE under CDN77 Frankfurt.
Interpretation
The MetaMask and SEAL listings and the PhishDestroy internal listing each describe separate monitoring records rather than a shared finding. The VirusTotal count and the HTTP 451 response come from different checks on different dates, so they should be read as distinct observations. The first-observed and PageSpeed dates fall on the same day, but that alone does not establish that the two measurements were taken together.
Recommended Actions
For oelpugoqb7qzckmixbyxy5azestwojbi2p3x22r7cb74dg4hqkpa.arweave.net, preserve the MetaMask and SEAL blocklist records and the PhishDestroy internal listing for later comparison. Retain the VirusTotal result and the recorded HTTP response as separate reference points. Compare future blocklist entries against the current ones, and re-check the HTTP response independently of the other sources.
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.
What we count
Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: Last known active.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedAug 17, 2026
Page Title
Suspected Phishing | Cloudflare
Impersonates
Cloudflare
TLS Certificate
Certificate hostname mismatch·
Issued by Let's Encrypt· stored validity ends in 45 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
212.102.56.179
Network ASN
AS60068
Organization
CDN77 Frankfurt
Observed location
Frankfurt am Main, DE
Server header
CDN77-Turbo
Nameservers 1
nitin.ns.cloudflare.com
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt
Valid from
2026-07-06 09:50:51
Valid until
2026-10-04 09:50:50
Hostname coverage
Certificate hostname mismatch
Validity
Stored certificate expired
Collection time
2026-08-18 01:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprint7efd72e7f4f5b095ed480248d139f795b4e1ed856821c2f229ead69356808f4aCertificate names · 1 SANs
arweave.net
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationUnknownHttp 2xx Unclassified40%2026-10-07 01:41:04 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-08-17 20:28:10 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.
Last analyzed First positive detection Previous stored snapshot: 5 detections
Forcepoint ThreatSeeker
Fortinet
G-Data
Phishing Database
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of oelpugoqb7qzckmixbyxy5azestwojbi2p3x22r7cb74dg4hqkpa.arweave.net· checked Aug 17, 2026
82
Needs Work
Performance
FCP
1.81s
First Contentful Paint
LCP
4.66s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.98s
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-08-22 10:00:25 UTC
Domain state transitioned from alive to dead.
VirusTotal Detections Update2026-08-18 03:03:10 UTC
VirusTotal scanner detections updated from 0 to 5. Added scanner alerts: Forcepoint ThreatSeeker, Fortinet, G-Data, LevelBlue, Phishing Database.
Threat First Observed2026-08-17 20:33:11 UTC
Domain ingestion complete. Initial state is marked as alive.
Threat Response Pipeline
Discovery
Analysis
Monitoring
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
oelpugoqb7qzckmixbyxy5azestwojbi2p3x22r7cb74dg4hqkpa.arweave.net detected and queued for full analysis
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.
3 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 →
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)
