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, the domain 7dkqmrkjviutkrjqcc3bg2var2oezcofojuvkocr7qww6howrpja.arweave.net returned an HTTP status code of 451. returned HTTP status 451 on 2026-10-01, according to the recorded HTTP check. The same record set shows a PhishDestroy internal listing for the full domain 7dkqmrkjviutkrjqcc3bg2var2oezcofojuvkocr7qww6howrpja.arweave.net, and that listing is the only internal flag in this evidence.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 451 for the domain. VirusTotal, checked on 2026-08-30, reported 4 detections across 91 scanners. The external blocklists MetaMask and SEAL both listed the domain, and the blocklist check date was 2026-10-02. The domain was first observed on 2026-08-16, the same date as the PageSpeed check, which recorded a performance score of 100. The SSL scan on 2026-08-16 named Let's Encrypt / YE1 as the certificate issuer. The IP address 212.102.56.179 is recorded in Germany under CDN77 Frankfurt.
Interpretation
The named sources describe different things: a recorded HTTP response, scanner detections, external blocklist entries, an internal listing, and a performance score. Because the HTTP check, VirusTotal check, and blocklist check carry different dates, they are separate observations rather than a single measurement. The first-observed and SSL scan dates coincide, but that shared calendar date does not establish simultaneous measurement. The recorded HTTP code describes only that response, not all content on the domain.
Recommended Actions
For the full domain 7dkqmrkjviutkrjqcc3bg2var2oezcofojuvkocr7qww6howrpja.arweave.net, preserve the HTTP check record and the VirusTotal record for later comparison. Preserve the MetaMask and SEAL blocklist entries as separate source records, and compare them against the PhishDestroy internal listing. Review the PageSpeed record alongside the HTTP check to distinguish performance data from response data. Re-check the domain against each named source and compare any new observations with the preserved records.
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 16, 2026
Favicon Hash
Page Title
Suspected Phishing | Cloudflare
Impersonates
Cloudflare
TLS Certificate
Certificate hostname mismatch·
Issued by Let's Encrypt· stored validity ends in 46 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-16 19:02:03 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:01 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-08-16 14:28:15 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: 4 detections
Chong Lua Dao
Forcepoint ThreatSeeker
Fortinet
Phishing Database
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of 7dkqmrkjviutkrjqcc3bg2var2oezcofojuvkocr7qww6howrpja.arweave.net· checked Aug 16, 2026
100
Good
Performance
FCP
0.76s
First Contentful Paint
LCP
1.67s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.29s
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-09-08 10:00:23 UTC
Domain state transitioned from alive to dead.
VirusTotal Detections Update2026-08-16 22:48:19 UTC
VirusTotal scanner detections updated from 3 to 5. Added scanner alerts: Chong Lua Dao, Fortinet.
Threat First Observed2026-08-16 14:33:11 UTC
Domain ingestion complete. Initial state is marked as alive.
Threat Response Pipeline
Discovery
Analysis
Monitoring
13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
7dkqmrkjviutkrjqcc3bg2var2oezcofojuvkocr7qww6howrpja.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 matches8
Same favicon hash or the same page title as this host.
(US)
