Skip to security report
Analytics Dashboard
Domain security and threat intelligence
claim.rpcblockdag.network favicon

claim.rpcblockdag.network

In short

claim.rpcblockdag.network is a BlockDAG impersonation page detected by PhishDestroy on 2026-02-23. Risk: high (61/100). Status: Content unavailable. Hosting: Cloudflare, Inc. VirusTotal: 1/95 engines flag it. Do not enter credentials or connect a wallet.

“Become a Part Of BlockDAG Network | Buy BDAG Coins & Miners”

Resolved IP
104.21.60.106
Registered
Feb 15, 2026
PhishDestroy assessment High
Availability Content unavailable Content was unavailable in the latest observation Observed · HTTP probe
Risk signals
VirusTotal detections: 1/95 Stored blocklist matches: 1 Automated brand label: BlockDAG
Feb 23, 2026 CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 1. Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
1 / 95
engine detections
Google Safe Browsing
No threat flag
Page captures
2
open gallery
Domain age
249 days
Source evidenceVirusTotal 1 / 95 5 sources

VirusTotal

1 / 95 engine detections

Open report

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

Open report

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

High
VirusTotal
1 / 95
Page captures
2
Page captures Source results Registration record

PhishDestroy threat report

The domain claim.rpcblockdag.network is a cryptocurrency phishing site engaged in brand impersonation targeting BlockDAG. It presents itself as an official BlockDAG portal, inviting users to 'Become a Part Of BlockDAG Network | Buy BDAG Coins & Miners,' but is designed to deceive victims into disclosing wallet credentials or transferring funds. No drainer kit was identified, and the site is currently taken offline.

Technical indicators confirm the elevated risk. claim.rpcblockdag.network was flagged by 1 of 95 VirusTotal security vendors, including SOCRadar, and appears on 2 security blocklists: PhishDestroy and ScamSniffer. The domain was created on February 23, 2026, and resolves to the IP address 104.21.60.106, hosted on Cloudflare's network (AS13335) in the US. No SSL certificate was observed, and the registrar remains undisclosed. The Gridinsoft trust score for the domain is 0 out of 100, reinforcing its malicious classification.

Victims who interacted with claim.rpcblockdag.network should immediately revoke any token approvals granted to unknown contracts and transfer remaining funds to a new, secure wallet. Monitor transaction history for unauthorized activity and report the incident to relevant platforms, including the impersonated brand (BlockDAG), security blocklists like PhishDestroy and ScamSniffer, and local cybercrime authorities. If credentials were entered, reset passwords and enable multi-factor authentication on all associated accounts.

Questions about claim.rpcblockdag.network

Is claim.rpcblockdag.network legit?

No. PhishDestroy classifies claim.rpcblockdag.network as a BlockDAG impersonation page (risk: high, 61/100); it was first detected on 2026-02-23. VirusTotal: 1/95 engines flag it. Treat the site as unsafe.

Is claim.rpcblockdag.network safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on claim.rpcblockdag.network. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used claim.rpcblockdag.network?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesScamSniffer · PhishDestroy 2
ScamSniffer Listed View source
PhishDestroy PhishDestroy list View source

Last checked

Stored Capture · 2 captures

Primary capture 1 / 2
SourcePrimary capture
Recorded2026-02-23 00:13 UTC
StateStored capture
Position1 / 2
Open capture Wayback Download

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registration (base domain)rpcblockdag.network · Created Feb 15, 2026 (249d)
Time to First Unavailability 61 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 DetectedFeb 23, 2026
DOM Analysisanalyzed Apr 23, 2026score 61/1001 brand signal
Submitted URLhttp://claim.rpcblockdag.network/
Observed page title
Become a Part Of BlockDAG Network | Buy BDAG Coins & Miners
Automated brand references
BlockDAG

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
104.21.60.106
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

viewdns.info · 104.21.60.106rapiddns.io

Latest Classified Outcome 2026-10-21 14:53:36 UTC

Primary outcome DNS inactive reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Unknown Probe Inconclusive 20% 2026-10-21 01:07:51 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-06-17 22:08:16 UTC current episode first observed: 2026-09-30 16:14:55 UTC observed RIP window: 2026-06-17 22:08:16 UTC → 2026-09-30 16:14:55 UTC · 2,514.11h midpoint estimate ≈ 2026-08-09 07:11:35 UTC · precision very low · 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.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

1 / 95 security vendors flagged this domain
View on VT
Last analyzed
SOCRadar

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Registration & observation details8

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
2514.11
Estimate basis
Bounded by observations
Estimate precision
very_low

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

No cloaking flag in this check

unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='claim.rpcblockdag.network', port=80): Max retries exceeded with url: / (Caused by NewConne

claim.rpcblockdag.network
Saved result
Unreachable
Stored observation history14

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

Earlier observations 9
  1. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  6. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  7. Availability monitor · Recorded state

    https://radar.cloudflare.com/scan/661b3de7-1bcc-4885-90ca-3be983a031ff

  8. Availability monitor · Recorded state

    Reachable→Unavailable

  9. Availability monitor · Recorded state

    Reachable→Unavailable

Recorded activity

4 entries
  1. VirusTotal

    1/95 engine detections

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. Added to PhishDestroy

    claim.rpcblockdag.network

    View source
  4. URLScan

    Page captured

    View source

Community reports

Reported by 1 community member, first seen Feb 23, 2026

Stored reports
1
Unique reported URLs
1
Accepted1

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 1 det. ChainPatrol URLQuery Report stored SSL Labs CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback Archived
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked 0 stored notification records Content unavailable

Listed domains receive at least one abuse report; this entry has no retained notification history.

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.

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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 →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

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
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including claim.rpcblockdag.network)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Request a correction or appeal How PhishDestroy works
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/claim.rpcblockdag.network"
  title="PhishDestroy threat report for claim.rpcblockdag.network"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>