VirusTotal
5 / 90 engine detections
PhishDestroy first recorded blockchain-explorer.network on 2026-02-13. Stored VirusTotal result: 5/90 engines flagged.
“Multi-Chain Wallet Explorer - React + Node.js”
Recorded source summary
PhishDestroy stores a record for blockchain-explorer.network. Source observations are dated separately; missing checks do not establish safety.
A reviewed analysis is not available for this text revision. Consult the dated source records below.
5 / 90 engine detections
Scan report
Open report23 community references
Open reportprovider verdict: clean
Open reportObserved: · Retrieved:
| Uuid | c41316db-cb90-47c8-bee7-364b069c9332 |
|---|---|
| Final url | https://blockchain-explorer.network/ |
| Status | 200 |
| History | [
{
"url": "https://blockchain-explorer.network/",
"status": 200
}
] |
| DOM structure hash | c0411386000d357f1ca166e5fe6e7391cee563714f881290755151f53a5ae765 |
| Document hash | 54eab78d6b422a236521403bcb82bed9a90a917506b602fdcb44ca57390c43df |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "blockchain-explorer.network",
"type": "A",
"value": "104.21.7.247"
},
{
"name": "blockchain-explorer.network",
"type": "A",
"value": "172.67.188.30"
},
{
"name": "blockchain-explorer.network",
"type": "AAAA",
"value": "2606:4700:3035::6815:7f7"
},
{
"name": "blockchain-explorer.network",
"type": "AAAA",
"value": "2606:4700:3037::ac43:bc1e"
}
] |
| Dnssec valid | false |
| Ip | 104.21.7.247 |
| Registration record | {
"registrar": "NICENIC INTERNATIONAL GROUP CO., LIMITED",
"created": "2025-10-01T13:17:45Z",
"updated": "2025-10-06T13:17:49Z",
"expires": "2026-10-01T13:17:45Z",
"nameservers": [
"adel.ns.cloudflare.com",
"quinton.ns.cloudflare.com"
]
} |
No threat flag
Open reportNo malicious flag
Open reportObserved: · Retrieved:
| Uuid | 019c56b9-fcbe-735f-88a3-ea3612912804 |
|---|---|
| Final url | https://blockchain-explorer.network/ |
| Status | 200 |
| Ip | 172.67.188.30 |
| Contacted domains | [
"fonts.gstatic.com",
"cdnjs.cloudflare.com",
"fonts.googleapis.com"
] |
| Contacted IP addresses | [
"142.251.143.99",
"104.17.24.14",
"142.250.187.202",
"172.67.188.30"
] |
| Asns | [
"15169",
"13335"
] |
| Countries | [
"US"
] |
| Document hash | d61ea4685cf653b7fd8ba60fc86f98c37cccce30880d38a749c5f7c78214b1f0 |
| Script hashes | [
"7660c2f06951943c3224e381f81c16186b834a6cbf66fe75c0f97cb6b22c3de4"
] |
| Globals | [
"crashReport"
] |
| Cookies | [
"GAESA"
] |
| Tls | {
"san": [
"blockchain-explorer.network",
"*.blockchain-explorer.network"
],
"cipher": "AES_128_GCM",
"issuer": "WE1",
"subject": "blockchain-explorer.network",
"protocol": "QUIC",
"valid_to": "2026-04-27T23:01:21Z",
"valid_from": "2026-01-27T22:03:26Z"
} |
| Domain age days | 134 |
| Apex age days | 134 |
| Tls age days | 16 |
| Tls valid days | 90 |
| Requests | 30 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-0.1.0-1-d9114fd"
],
"score": -57,
"malicious": false
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "cloudflare",
"content-type": "text/html; charset=UTF-8",
"x-powered-by": "Express",
"strict-transport-security": "max-age=63072000; includeSubDomains",
"priority": "u=0,i",
"via": "1.1 google"
} |
Separate stored monitor snapshot; does not replace the primary report record or establish current availability.
Check recorded; verdict not retained
Open reportNo report found
Open reportA missing report is not a trust verdict. Legacy zeroes remain in the stored record; the measured trust score is unavailable.
88 / 100 · heuristic score · 1 brand reference · 1 classification
Open reportThis dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.
Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
Stored page, network and scanner observations, grouped by source and observation time.
PhishDestroy rates blockchain-explorer.network as critical risk (88/100) from the recorded evidence; it was first recorded on 2026-02-13. Stored VirusTotal result: 5/90 engines flagged. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
This report does not record which wallet requests blockchain-explorer.network makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.
It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.
Checked, no match
Last checked
89cd2c3cb784e1052a7a08dcff771bde0351c72b478f08fb915209219424c0f8 · 174936 bytes 5437b8e81eab33094526a83ece08ade561c551500ec414799d3007dd0f6e0ab7 · 63139 bytes 9532ddfc368c3f06884602fbbd2f785dfce9f78b06bc8b538b47c497a3779d5d · 65395 bytes d1960131a09fc11cc31e9816edc47924c4b850734f4cee8fc20569ef84bf51b1 · 49443 bytes 57653d422c31bebfff7a5ec3512583aad6eae321925f6f0f9d294692df283a2f · 72238 bytes 2ec0a98b06b9852eb922b421995a21516f4d838948e848051e259be5ffe878e2 · 78248 bytes a6c8a879b075490c53ae5588b0beb6e54c3589f894b533f5b3d0f303616787d0 · 77774 bytes 8d25f31f964dd1d90b8238c69aabda6280d4a9c2d42e377776e159d226641bf1 · 162102 bytes For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
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.
Edge-IP reputation is not attributed to this domain.
quinton.ns.cloudflare.commail.blockchain-explorer.networkpriority 0Location describes the IP network.
c60897742f5d043ba1ca9c4472c6c286a05b72ab0905533e543e8f2d5356d25eblockchain-explorer.network*.blockchain-explorer.networkSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Google PageSpeed Insights — mobile performance audit of blockchain-explorer.network · checked Mar 2, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Network requests: 30 SHA-256 hashes: 30 URLScan scan:
Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-29 06:19 UTC.
Open this scan on URLScan 019c56b9-fcbe-735f-88a3-ea3612912804 ↗
| # | Network request | HTTP method · status | Type | Uncompressed size | Response body SHA-256 |
|---|
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
The site did not answer our scanner (host unreachable).
blockchain-explorer.network Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Reachable→Unavailable
Unavailable→Reachable
https://radar.cloudflare.com/scan/e9067e61-5a1a-4e1e-9585-d816167c691c
https://radar.cloudflare.com/scan/c41316db-cb90-47c8-bee7-364b069c9332
Reachable→Unavailable
Source: domain_monitor. This stored snapshot does not establish current availability.
Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.
Recorded events: 15. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
23 community references
View sourceblockchain-explorer.network
View sourcePage captured
View sourceWe 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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.
Download all records as JSON| ID | Stored data |
|---|
Reported by 1 community member, first seen Feb 13, 2026
Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.
IC3 does not accept attachments. Keep original evidence for investigators. IC3 guidance
Federal tips line1-800-CALL-FBICurrent service: Report Fraud. England, Wales and Northern Ireland. Scotland: 101.
Contact centre0300 123 2040Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.
Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.
Forward scam emails and text messages to the National Cyber Security Centre, which takes down the malicious sites it finds.
Emailreport@phishing.gov.uk Text messages7726Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.
Forward phishing emails to the Anti-Phishing Working Group.
Emailreportphishing@apwg.orgNational Cyber Crime Reporting Portal. For financial fraud, also call the 1930 helpline straight away.
Helpline1930Select your country to get official cybercrime contacts, or create a complaint draft →.
If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.
Scammers are criminals. Filing a report creates a legal record and helps protect others.
Template-based draft • optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
blockchain-explorer.network)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.
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.