Security engines reporting a detection: 7. Public blocklists reporting a match: 3. Exercise extreme caution — do not enter credentials or personal information.
On 2026-10-01, jjfeb5j6tzvrfujq4sanjlwaynbz5sd47xunwexh4eankvpgod7q.arweave.net returned HTTP status 451. returned HTTP status 451, per the recorded HTTP check. The same record shows the domain was first observed on 2026-09-17, giving a dated starting point for the available observations.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 451. A VirusTotal scan on 2026-09-29 reported 7 detections across 91 scanners. External blocklists MetaMask, ScamSniffer, and SEAL were recorded on 2026-10-02, and the domain appears in the PhishDestroy internal listing. An SSL scan on 2026-09-21 recorded the issuer as Let's Encrypt / YE2. The IP address 37.19.194.80 is listed with Cdn77 FRA in DE.
Interpretation
The HTTP 451 response and the SSL scan are separate dated records, so they describe different points in time. The blocklist entries and the VirusTotal detection count come from distinct sources and should be read as separate observations. The first observation on 2026-09-17 predates the other records, but the available data does not show what occurred between those dates.
Recommended Actions
For jjfeb5j6tzvrfujq4sanjlwaynbz5sd47xunwexh4eankvpgod7q.arweave.net, preserve the HTTP check record, the VirusTotal result, and the external blocklist entries as separate source documents. Compare the HTTP status record with the blocklist records to see whether they describe the same access conditions. Review the VirusTotal detection count alongside the named blocklists without merging them into a single score. Retain the first-observed and SSL scan records for chronological reference.
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.
Registration (base domain)arweave.net · Created Jan 25, 2018
HTTP Status451 Unavailable For Legal Reasons
Time to First Unavailability5 days
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
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.
Technical detailsProvenance & timestamps
First DetectedSep 17, 2026
Favicon Hash
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
37.19.194.80
Network ASN
AS60068
Organization
Cdn77 FRA
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 / YE2
Valid from
2026-09-04 11:42:14
Valid until
2026-12-03 11:42:13
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-21 13:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprint032027be4817019c7469b1a5c6bfa8d8d579e5088b17473756bba17294bd1cf8Certificate 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.
Observed timelinelast reachable: 2026-10-07 10:18:27 UTClast content: 2026-10-07 10:18:27 UTCcurrent episode first observed: 2026-10-07 22:10:00 UTCobserved RIP window: 2026-10-07 10:18:27 UTC → 2026-10-07 22:10:00 UTC · 11.86hmidpoint estimate ≈ 2026-10-07 16:14:13 UTC · precision medium · basis bounded
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
BitDefender
ESET
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
Kaspersky
VIPRE
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-07 22:10:00 UTC
Domain state transitioned from alive to dead.
Domain Status Transition2026-10-07 02:11:36 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-09-29 22:05:34 UTC
Domain state transitioned from alive to dead.
Domain Status Transition2026-09-29 01:29:36 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-09-21 22:00:22 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-21 10:13:10 UTC
Domain ingestion complete. Initial state is marked as alive.
Threat Response Pipeline
Discovery
Analysis
Monitoring
14 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
jjfeb5j6tzvrfujq4sanjlwaynbz5sd47xunwexh4eankvpgod7q.arweave.net detected and queued for full analysis
Sep 17, 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 latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Oct 8, 2026
Time to First Unavailability
114 hours elapsed from detection to the first unavailable 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 recordedContent unavailable
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)
