Security engines reporting a detection: 2. Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.
The domain transfer.blockdog.network was registered on February 25, 2026 through Hostinger Operations, UAB and currently resolves to the Cloudflare edge address 104.21.34.201, which is associated with AS13335 (Cloudflare, Inc.) and geolocated to the United States. The site is hosted behind Cloudflare, uses the authoritative nameservers coen.ns.cloudflare.com and holly.ns.cloudflare.com, and does not present an SSL/TLS certificate, indicating that HTTPS was not enforced at the time of observation. The page title retrieved from the site reads "Become a Part Of BlockDAG Network | Buy BDAG Coins & Miners," directly referencing the BlockDAG brand and suggesting a cryptocurrency‑related lure. Analysis of the infrastructure reveals that the operation employed the publicly known "Wallet Connect Abuse" phishing kit, a template frequently used to harvest crypto wallet credentials.
Two of ninety‑three VirusTotal scanners flagged the domain as malicious, and the domain appears on two external security blocklists. It has also been listed by PhishDestroy and ScamSniffer as a confirmed threat. The site is presently offline, but its recent creation date, Cloudflare hosting, and lack of TLS suggest a short‑lived campaign designed to evade detection while targeting BlockDAG users.
Uncertainty remains regarding the full scope of victim outreach, as no traffic logs or phishing lure samples were captured. Defenders should block the domain at network perimeter filters, monitor DNS queries for the associated IP and nameservers, and add the host to internal watchlists. Continuous re‑scanning of the domain on VirusTotal and other sandbox services is advised in case the site becomes active again, and any related credential‑theft attempts should be investigated for potential compromise of BlockDAG wallet accounts.
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.
Stored cloaking flag
Not yet scanned
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='transfer.blockdog.network', port=80): Max retries exceeded with url: / (Caused by NewConne
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Registration (base domain)blockdog.network · Created Feb 25, 2026 (228d)—Expires Feb 16, 2027
Time to First Unavailability31h
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 DetectedFeb 25, 2026
DOM Analysisanalyzed Jul 29, 2026score 61/1001 brand signal
Submitted URLhttp://transfer.blockdog.network/
Case ID
ICANN OVERSIGHTRegistration: blockdog.network
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
For the registrable domain blockdog.network 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.
Accreditation is a contract, not a safety certification.
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.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 01:10:34 UTC
RDAP registrationUnknown
Observed timelinecurrent episode first observed: 2026-09-30 16:14:55 UTCfirst terminal observation: 2026-09-30 16:14:55 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.
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.
VirusTotal Detections Update2026-02-27 02:02:47 UTC
VirusTotal scanner detections updated from 2 to 3. Added scanner alerts: Gridinsoft, SOCRadar, Seclookup.
Domain Status Transition2026-02-27 02:02:47 UTC
Domain state transitioned from alive to dead.
Threat Response Pipeline
Discovery
Analysis
Notifications
Monitoring
15 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
transfer.blockdog.network 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 latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Feb 27, 2026
Time to First Unavailability
31 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.
5 evidence signal groups linked1 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 →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · transfer.blockdog.network
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.
Registrable-domain reportParent
Separate evidence record for the registrable domain above transfer.blockdog.network.
(LT)
