Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 6. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
electrum-hub.org favicon

electrum-hub.org

In short

electrum-hub.org is an Electrum impersonation page detected by PhishDestroy on 2026-10-23.

“Electrum Bitcoin Wallet”

Review the evidence
Registrar
United StatesDynadot
Resolved IP
Canada138.226.253.79COLO
Registered
Oct 1, 2026
First observed
Oct 23, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 6/92 Stored blocklist matches: 2 Automated brand label: Electrum Scam type: Impersonation Young domain: 26 days old
VirusTotal
6 / 92
engine detections ·
Blocklist matches
2
MetaMask, SEAL
URLQuery
2
detections
OTX
4
community references
URLScan
Malicious
engine verdict · score 98
Page captures
10
open gallery
Domain age
26 days
Reports sent
1
view timeline
OTX: 4 refs Oct 23, 2026 1 Report Sent
X Telegram API
ABUSE NOTICE · 72H+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@dynadot.com. The latest stored availability evidence still shows the domain reachable; 4 days has elapsed since the first outgoing report.

ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.

Elapsed since first report
4 days
Reports sent
1
Latest case ID
PD-20261023-B8D409
Current status
HTTP 302 at latest stored check

Analysis

Domain summary

electrum-hub.org is an Electrum impersonation page detected by PhishDestroy on 2026-10-23. Risk: critical (100/100). Registrar: Dynadot. Status: Last known active. Hosting: COLO. PhishDestroy sent 1 abuse report. VirusTotal: 6/92 engines flag it. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
6 / 92
Blocklist matches
2
Scam type
Impersonation
Hosting
Canada138.226.253.79COLO
Registrar
United StatesDynadot
Registered
Oct 1, 2026
OTX
4 community refs
Page captures
10
Page captures Source results Registration record

PhishDestroy threat report

Overview

PhishDestroy’s automated assessment classifies electrum-hub.org as an impersonation phishing page that pretends to be the Electrum Bitcoin wallet. The recorded page title was “Electrum Bitcoin Wallet”. PhishDestroy first observed the domain on 2026-10-23 and recorded an HTTP 200 response on that date.

How the scam works

Impersonation phishing sites replicate the visual design and wording of legitimate wallet services to lure users into entering login credentials, seed phrases, or other sensitive data. Harvested information can be used to gain unauthorized access to victims’ cryptocurrency wallets.

Evidence

VirusTotal reported six detections across ninety‑two engines on 2026-10-23, with five vendors labeling the domain malicious and one as suspicious. Google Safe Browsing showed no flag on 2026-10-23, while urlscan’s engine flagged the site as malicious with a score of 98 despite an overall clean verdict on the same day. External blocklists MetaMask and SEAL listed the domain as of 2026-10-23, and OTX recorded four pulses mentioning it on that date. PhishDestroy added the domain to its internal blocklist on 2026-10-23, citing two malicious VirusTotal vendors as the intake reason.

Infrastructure

The domain was observed pointing to IP 138.226.253.79, associated with Trunk Networks LTD, and the TLS handshake used a Let’s Encrypt certificate valid through 2026-12-30. The domain was registered with Dynadot Inc on 2026-10-01, giving it an age of 21 days at the time of first observation. The web server identified itself as nginx, and DNSSEC was not enabled.

What to do

Anyone who entered credentials, seed phrases, or other wallet data on this site should assume the information is compromised, create a new secure wallet, and monitor accounts for unauthorized activity. Defenders should block the exact domain, monitor DNS queries for 138.226.253.79, and add the domain to relevant blocklists and security policies.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportURLQuery reportStored capture screenshotCloudflare Radar screenshot (2026-10-23T02:03:37Z)URLQuery screenshotURLScan screenshot (2026-10-07T16:57:52Z)URLScan capture reportURLScan screenshot (2026-10-07T23:38:48Z)URLScan capture reportURLScan screenshot (2026-10-08T03:34:22Z)URLScan capture reportURLScan screenshot (2026-10-16T07:21:58Z)URLScan capture reportURLScan screenshot (2026-10-20T07:25:35Z)URLScan capture reportURLScan screenshot (2026-10-23T02:14:50Z)URLScan capture reportVirusTotal reportGoogle Safe Browsing statusArchived copyReport phishing to GoogleSite owner? Request a review
Source evidenceVirusTotal 6 / 92 · OTX 4 references 9 sources

VirusTotal

6 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 15 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
53
Malicious
5
Suspicious
1
Undetected
33

Vendor labels

VIPRE
malware
SOCRadar
malicious
Kaspersky
phishing
Gridinsoft
suspicious
alphaMountain.ai
malicious
Forcepoint ThreatSeeker
malicious

Reputation score

0

Categories

Google
technology
alphaMountain.ai
Malicious (alphaMountain.ai)
Forcepoint ThreatSeeker
newly registered websites

Registrar

Dynadot Inc

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    A
    Value
    138.226.253.79
  • TTL, seconds
    300
    Type
    NS
    Value
    ns2.dyna-ns.net
  • TTL, seconds
    300
    Type
    NS
    Value
    ns1.dyna-ns.net
  • TTL, seconds
    300
    Type
    SOA
    Responsible mailbox
    hostmaster.electrum-hub.org
    Value
    ns1.dyna-ns.net

DNS records observed

JARM fingerprint

29d29d15d29d29d00042d42d00000072e74222ce193a6f991becaa3da6c94d

Certificate

Subject alternative names
  • electrum-hub.org
  • www.electrum-hub.org
Issuer
Let's Encrypt / YR2
Serial
624380bd9b9be82bd1f37b68224fe4df7c6
SHA-256
3b24f380797114b7404f7dcc27c82ff32ce76b79cf2bc82cea512f63ceab2fed
Subject
www.electrum-hub.org
Valid until
Valid from

Registration record

Registrar
Dynadot Inc
Registrar IANA ID
472
Registrar URL
http://www.dynadot.com
Registered
Updated
Expires
Status
  • addPeriod
Nameservers
  • ns1.dyna-ns.net
  • ns2.dyna-ns.net
DNSSEC
unsigned

Registry data (RDAP)

Status
  • transfer prohibited
Registry events
Expiration
Last changed
Registration
Registrar expiration
Last RDAP database update
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 53,
    "malicious": 5,
    "suspicious": 1,
    "undetected": 33
}
Vendor labels
{
    "VIPRE": "malware",
    "SOCRadar": "malicious",
    "Kaspersky": "phishing",
    "Gridinsoft": "suspicious",
    "alphaMountain.ai": "malicious",
    "Forcepoint ThreatSeeker": "malicious"
}
Reputation
0
Categories
{
    "Google": "technology",
    "alphaMountain.ai": "Malicious (alphaMountain.ai)",
    "Forcepoint ThreatSeeker": "newly registered websites"
}
Registrar
Dynadot Inc
Created
2026-10-01T11:20:29Z
Expires
2027-10-01T11:20:29Z
Updated
2026-10-01T13:16:06Z
First seen
2026-10-01T16:03:38Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "138.226.253.79"
    },
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns2.dyna-ns.net"
    },
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns1.dyna-ns.net"
    },
    {
        "ttl": 300,
        "type": "SOA",
        "rname": "hostmaster.electrum-hub.org",
        "value": "ns1.dyna-ns.net"
    }
]
Dns at
2026-10-23T02:47:55Z
Jarm
29d29d15d29d29d00042d42d00000072e74222ce193a6f991becaa3da6c94d
Certificate
{
    "san": [
        "electrum-hub.org",
        "www.electrum-hub.org"
    ],
    "issuer": "Let's Encrypt / YR2",
    "serial": "624380bd9b9be82bd1f37b68224fe4df7c6",
    "sha256": "3b24f380797114b7404f7dcc27c82ff32ce76b79cf2bc82cea512f63ceab2fed",
    "subject": "www.electrum-hub.org",
    "valid_to": "2026-12-30T14:00:05Z",
    "valid_from": "2026-10-01T14:00:06Z"
}
Registration record
{
    "registrar": "Dynadot Inc",
    "registrar_iana_id": "472",
    "registrar_url": "http://www.dynadot.com",
    "created": "2026-10-01T11:20:29Z",
    "updated": "2026-10-01T13:16:06Z",
    "expires": "2027-10-01T11:20:29Z",
    "status": [
        "addPeriod"
    ],
    "nameservers": [
        "ns1.dyna-ns.net",
        "ns2.dyna-ns.net"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "transfer prohibited"
    ],
    "events": {
        "expiration": "2027-10-01T11:20:29Z",
        "last changed": "2026-10-17T11:32:19Z",
        "registration": "2026-10-01T11:20:29Z",
        "registrar expiration": "2027-10-01T11:20:29Z",
        "last update of RDAP database": "2026-10-22T09:00:49Z"
    }
}
Separate source record · 5 malicious + 1 suspicious / 92 · 2026-10-23 02:42:38 UTC

The summary above and this provider record were collected at different times. Both remain available; malicious and suspicious classifications are shown separately.

record_source
collected_observations.vt
analysis_at
2026-10-23T02:42:38Z
fetched_at
2026-10-23T14:02:13Z
stats
{"timeout":0,"harmless":53,"malicious":5,"suspicious":1,"undetected":33}

Cloudflare Radar

Suspicious

Open report
Cloudflare RadarOriginal source recordObserved: 12 fields

Observed: · Retrieved:

Report ID

e7734359-fbe8-4053-9c5a-7b999ce93db2

Final URL

https://electrum-hub.org/

HTTP response

200

Navigation history

  • URL
    https://electrum-hub.org/
    Status
    200

DOM structure hash

77be6186a123b063a14d0dc41ee8ea3f1d4d528856548e49238f91aa351517f0

Document hash

0ec418c4d70e35d523db6ff534da0e0b2f5d69a290c6f42728a246a3475fb2e3

Domain risk categories

  • Newly Seen Domains
  • Security Risks
  • New Domains

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    electrum-hub.org
    Type
    A
    Value
    138.226.253.79

DNSSEC valid

No

IP address

138.226.253.79

Registration record

Registrar
Dynadot Inc
Registered
Updated
Expires
Nameservers
  • ns1.dyna-ns.net
  • ns2.dyna-ns.net
Original source fields · JSON
Uuid
e7734359-fbe8-4053-9c5a-7b999ce93db2
Final url
https://electrum-hub.org/
Status
200
History
[
    {
        "url": "https://electrum-hub.org/",
        "status": 200
    }
]
DOM structure hash
77be6186a123b063a14d0dc41ee8ea3f1d4d528856548e49238f91aa351517f0
Document hash
0ec418c4d70e35d523db6ff534da0e0b2f5d69a290c6f42728a246a3475fb2e3
Domain risks
[
    "Newly Seen Domains",
    "Security Risks",
    "New Domains"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "electrum-hub.org",
        "type": "A",
        "value": "138.226.253.79"
    }
]
Dnssec valid
false
Ip
138.226.253.79
Registration record
{
    "registrar": "Dynadot Inc",
    "created": "2026-10-01T11:20:29Z",
    "updated": "2026-10-17T11:32:19Z",
    "expires": "2027-10-01T11:20:29Z",
    "nameservers": [
        "ns1.dyna-ns.net",
        "ns2.dyna-ns.net"
    ]
}

URLScan

Malicious · engine verdict · score 98

SHA-256 9aa255fd9b5a0a07c6a1311a18294c944cb575f207423b60388d46104c5b74bc

Open report
URLScanOriginal source recordObserved: 21 fields

Observed: · Retrieved:

Report ID

01a16685-828a-7079-aec6-0cec129925ab

Final URL

https://electrum-hub.org/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://electrum-hub.org/
    From
    http://electrum-hub.org/
    Status
    307

IP address

138.226.253.79

Reverse DNS (PTR)

dedicated.sollutium.com

Contacted IP addresses

  • 138.226.253.79

Autonomous systems (ASN)

  • 43180

Server countries

  • PL

Linked domains

  • electrum.org
  • github.com
  • x.com
  • njump.me
  • electrum-method.ledger-download.workers.dev
  • docs.electrum.org
  • download.electrum.org
  • raw.githubusercontent.com
  • bitcointalk.org
  • play.google.com
  • f-droid.org
  • www.youtube.com
  • en.wikipedia.org

Social media links

  • https://github.com/spesmilo/electrum
  • https://x.com/ElectrumWallet
  • https://github.com/spesmilo/electrum/blob/master/RELEASE-NOTES
  • https://www.youtube.com/watch
  • https://github.com/spesmilo/electrum/blob/master/LICENCE
  • https://github.com/spesmilo/electrum-web

Document hash

0ec418c4d70e35d523db6ff534da0e0b2f5d69a290c6f42728a246a3475fb2e3

TLS session and certificate

Subject alternative names
  • electrum-hub.org
  • www.electrum-hub.org
Cipher
AES_256_GCM
Issuer
YR2
Subject
www.electrum-hub.org
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

21

Registered domain age, days

21

Certificate age, days

21

Certificate validity, days

89

Page requests

14

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
98
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Server
nginx
Content-type
text/html
Original source fields · JSON
Uuid
01a16685-828a-7079-aec6-0cec129925ab
Final url
https://electrum-hub.org/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://electrum-hub.org/",
        "from": "http://electrum-hub.org/",
        "status": 307
    }
]
Ip
138.226.253.79
Ptr
dedicated.sollutium.com
Contacted IP addresses
[
    "138.226.253.79"
]
Asns
[
    "43180"
]
Countries
[
    "PL"
]
Linked domains
[
    "electrum.org",
    "github.com",
    "x.com",
    "njump.me",
    "electrum-method.ledger-download.workers.dev",
    "docs.electrum.org",
    "download.electrum.org",
    "raw.githubusercontent.com",
    "bitcointalk.org",
    "play.google.com",
    "f-droid.org",
    "www.youtube.com",
    "en.wikipedia.org"
]
Social
[
    "https://github.com/spesmilo/electrum",
    "https://x.com/ElectrumWallet",
    "https://github.com/spesmilo/electrum/blob/master/RELEASE-NOTES",
    "https://www.youtube.com/watch",
    "https://github.com/spesmilo/electrum/blob/master/LICENCE",
    "https://github.com/spesmilo/electrum-web"
]
Document hash
0ec418c4d70e35d523db6ff534da0e0b2f5d69a290c6f42728a246a3475fb2e3
Tls
{
    "san": [
        "electrum-hub.org",
        "www.electrum-hub.org"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "YR2",
    "subject": "www.electrum-hub.org",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-30T14:00:05Z",
    "valid_from": "2026-10-01T14:00:06Z"
}
Domain age days
21
Apex age days
21
Tls age days
21
Tls valid days
89
Requests
14
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 98,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx",
    "content-type": "text/html"
}
Separate monitor record · date not recorded

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

record_source
domain_monitor.urlscan
uuid
01a15833-6f2c-73da-83ab-0013cfbc4bd2
score
null
malicious
null
result_at
null
enriched_at
2026-10-23T08:15:15Z
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":"2026-10-23 10:15:15"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

4 community references

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

100 / 100 · heuristic score · 1 brand reference · 1 classification

Open report

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

ai_title
electrum-hub.org — Electrum Impersonation Phishing
ai_description
PhishDestroy flags electrum-hub.org as an impersonation phishing site that mimics the Electrum Bitcoin wallet, based on observed page content.
ai_generated_at
2026-10-23T14:05:53Z
ai_generated_by
threat-v3-groq
interpretation
Narrative generation metadata, separate from provider observation dates.

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

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 25 fields

Mail configuration

SPF lookups
0

CAA records

Domain
electrum-hub.org

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
1
Average page size, bytes
3935

Page title and metadata

Page title
Electrum Bitcoin Wallet
Description
Electrum Bitcoin Wallet — educational reconstruction of the public download panel.

Trackers

Requests
13

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
1487
TLS
159
Waiting
300
Connection
149
Download
0
Response time, ms
2095

TLS connection

ALPN
http/1.1
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 21
  • 22
  • 25
  • 53

Carbon estimate

Bytes
17422
CO₂, grams
0.0006
Cleaner than, %
60

DNS servers

Nameservers
  • IP address
    162.159.27.158
    Host
    ns1.dyna-ns.net
  • IP address
    162.159.25.5
    Host
    ns2.dyna-ns.net
DNS zone
electrum-hub.org

Location

IP address
138.226.253.79
ASN
43180
Organization
COLO
City
Vancouver
Country
CA

TLS certificate

Issuer
Let's Encrypt / YR2
Subject
www.electrum-hub.org

DNS records

A
  • 138.226.253.79
NS
  • ns2.dyna-ns.net
  • ns1.dyna-ns.net
SOA
Primary nameserver
ns1.dyna-ns.net
Hostmaster
hostmaster.electrum-hub.org
Serial
2026100106
Refresh, seconds
16384
Retry, seconds
2048
Expiry, seconds
1209600
Minimum TTL, seconds
300

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
138.226.253.79
IP version
4

Redirects

Redirect chain
  • https://electrum-hub.org

Subdomains

Count
1
Subdomains
  • www.electrum-hub.org

Technology stack

Technologies
  • Nginx

Page links

External link addresses
  • https://raw.githubusercontent.com/spesmilo/electrum/master/pubkeys/ThomasV.asc
  • https://electrum.org/
  • https://github.com/spesmilo/electrum
  • https://x.com/ElectrumWallet
  • https://njump.me/nprofile1qqspqflat0pmtegvnqqdfz7g4nau9yxcnwzhcl8p24e22uzgcnq9trsprpmhxue69uhhyetvv9ujuumwdae8gtnnda3kjctvqy88wue69uhkztnwdaejumr0dsqs7amnwvaz7tmp9ehx7uewd3hkcqgdwaehxw309ahx7uewd3hkcq
  • https://electrum-method.ledger-download.workers.dev/
  • https://electrum-method.ledger-download.workers.dev/
  • https://electrum-method.ledger-download.workers.dev/
  • https://electrum-method.ledger-download.workers.dev/
  • https://docs.electrum.org/en/latest/gpg-check.html
  • https://github.com/spesmilo/electrum/blob/master/RELEASE-NOTES
  • https://download.electrum.org/
  • https://raw.githubusercontent.com/spesmilo/electrum/master/pubkeys/sombernight_releasekey.asc
  • https://raw.githubusercontent.com/spesmilo/electrum/master/pubkeys/Emzy.asc
  • https://raw.githubusercontent.com/spesmilo/electrum/master/pubkeys/felixb_f321x.asc
  • https://raw.githubusercontent.com/spesmilo/electrum/master/pubkeys/svanstaa.asc
  • https://download.electrum.org/4.8.2/Electrum-4.8.2.tar.gz
  • https://download.electrum.org/4.8.2/Electrum-4.8.2.tar.gz.asc
  • https://download.electrum.org/4.8.2/electrum-4.8.2-x86_64.AppImage
  • https://download.electrum.org/4.8.2/electrum-4.8.2-x86_64.AppImage.asc
  • https://download.electrum.org/4.8.2/electrum-4.8.2.exe
  • https://download.electrum.org/4.8.2/electrum-4.8.2.exe.asc
  • https://download.electrum.org/4.8.2/electrum-4.8.2-setup.exe
  • https://download.electrum.org/4.8.2/electrum-4.8.2-setup.exe.asc
  • https://download.electrum.org/4.8.2/electrum-4.8.2-portable.exe
External links
43

Registration record

Registrar
Dynadot Inc
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • ns1.dyna-ns.net
  • ns2.dyna-ns.net

HTTP headers

Response headers
Server
nginx
Content-type
text/html
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "electrum-hub.org"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-10-02T03:45:10Z",
    "first": "2026-10-02T03:45:10Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 3935
}
Page title and metadata
{
    "title": "Electrum Bitcoin Wallet",
    "description": "Electrum Bitcoin Wallet — educational reconstruction of the public download panel."
}
Trackers
{
    "requests": 13
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 1487,
        "tls": 159,
        "wait": 300,
        "connect": 149,
        "download": 0
    },
    "response_ms": 2095
}
TLS connection
{
    "alpn": "http/1.1",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        21,
        22,
        25,
        53
    ]
}
Carbon
{
    "bytes": 17422,
    "co2_grams": 0.0006,
    "cleaner_than": 60
}
Dns server
{
    "ns": [
        {
            "ip": "162.159.27.158",
            "host": "ns1.dyna-ns.net"
        },
        {
            "ip": "162.159.25.5",
            "host": "ns2.dyna-ns.net"
        }
    ],
    "zone": "electrum-hub.org"
}
Location
{
    "ip": "138.226.253.79",
    "asn": "43180",
    "org": "COLO",
    "city": "Vancouver",
    "country": "CA"
}
Ssl
{
    "issuer": "Let's Encrypt / YR2",
    "subject": "www.electrum-hub.org"
}
DNS records
{
    "A": [
        "138.226.253.79"
    ],
    "NS": [
        "ns2.dyna-ns.net",
        "ns1.dyna-ns.net"
    ],
    "SOA": "{\"nsname\": \"ns1.dyna-ns.net\", \"hostmaster\": \"hostmaster.electrum-hub.org\", \"serial\": 2026100106, \"refresh\": 16384, \"retry\": 2048, \"expire\": 1209600, \"minttl\": 300}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "138.226.253.79",
    "family": 4
}
Redirects
{
    "chain": [
        "https://electrum-hub.org"
    ]
}
Subdomains
{
    "count": 1,
    "subdomains": [
        "www.electrum-hub.org"
    ]
}
Tech stack
{
    "technologies": [
        "Nginx"
    ]
}
Page links
{
    "external": [
        "https://raw.githubusercontent.com/spesmilo/electrum/master/pubkeys/ThomasV.asc",
        "https://electrum.org/",
        "https://github.com/spesmilo/electrum",
        "https://x.com/ElectrumWallet",
        "https://njump.me/nprofile1qqspqflat0pmtegvnqqdfz7g4nau9yxcnwzhcl8p24e22uzgcnq9trsprpmhxue69uhhyetvv9ujuumwdae8gtnnda3kjctvqy88wue69uhkztnwdaejumr0dsqs7amnwvaz7tmp9ehx7uewd3hkcqgdwaehxw309ahx7uewd3hkcq",
        "https://electrum-method.ledger-download.workers.dev/",
        "https://electrum-method.ledger-download.workers.dev/",
        "https://electrum-method.ledger-download.workers.dev/",
        "https://electrum-method.ledger-download.workers.dev/",
        "https://docs.electrum.org/en/latest/gpg-check.html",
        "https://github.com/spesmilo/electrum/blob/master/RELEASE-NOTES",
        "https://download.electrum.org/",
        "https://raw.githubusercontent.com/spesmilo/electrum/master/pubkeys/sombernight_releasekey.asc",
        "https://raw.githubusercontent.com/spesmilo/electrum/master/pubkeys/Emzy.asc",
        "https://raw.githubusercontent.com/spesmilo/electrum/master/pubkeys/felixb_f321x.asc",
        "https://raw.githubusercontent.com/spesmilo/electrum/master/pubkeys/svanstaa.asc",
        "https://download.electrum.org/4.8.2/Electrum-4.8.2.tar.gz",
        "https://download.electrum.org/4.8.2/Electrum-4.8.2.tar.gz.asc",
        "https://download.electrum.org/4.8.2/electrum-4.8.2-x86_64.AppImage",
        "https://download.electrum.org/4.8.2/electrum-4.8.2-x86_64.AppImage.asc",
        "https://download.electrum.org/4.8.2/electrum-4.8.2.exe",
        "https://download.electrum.org/4.8.2/electrum-4.8.2.exe.asc",
        "https://download.electrum.org/4.8.2/electrum-4.8.2-setup.exe",
        "https://download.electrum.org/4.8.2/electrum-4.8.2-setup.exe.asc",
        "https://download.electrum.org/4.8.2/electrum-4.8.2-portable.exe"
    ],
    "external_count": 43
}
Registration record
{
    "registrar": "Dynadot Inc",
    "created": "2026-10-01T11:20:29Z",
    "updated": "2026-10-17T11:32:19Z",
    "expires": "2027-10-01T11:20:29Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "ns1.dyna-ns.net",
        "ns2.dyna-ns.net"
    ]
}
HTTP headers
{
    "headers": {
        "server": "nginx",
        "content-type": "text/html"
    }
}

Questions about electrum-hub.org

Is electrum-hub.org legit?

No. PhishDestroy classifies electrum-hub.org as an Electrum impersonation page (risk: critical, 100/100); it was first detected on 2026-10-23. VirusTotal: 6/92 engines flag it. Treat the site as unsafe.

Is electrum-hub.org safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on electrum-hub.org. 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 electrum-hub.org?

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 matchesMetaMask · PhishDestroy · SEAL · no match in the other 9 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Checked, no match

Last checked

Stored Capture · 10 captures

Primary capture 1 / 10
SourcePrimary capture
Recorded
StateStored capture
Position1 / 10
Open capture Wayback Download
All capture links and hashes (10)
electrum-hub.org: Electrum impersonation — Blocked by MetaMask, flagged by SEAL, 6/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical).
Social preview card electrum-hub.org: Electrum impersonation — Blocked by MetaMask, flagged by SEAL, 6/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical). v 18bb8aaae7bf

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 98 report ↗
IP Reputation Canada138.226.253.79 abuse score 0/100 0 reports checked Oct 23, 2026
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Dynadot US(US)
Abuse contactabuse@dynadot.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for electrum-hub.org →
RegistrationCreated Oct 1, 2026 (26d · Very New!) — Expires Oct 1, 2027
WHOIS statusclientTransferProhibited
HTTP Status302 Found (Temporary)
Technical detailsProvenance & timestamps
First DetectedOct 23, 2026
DOM Analysisanalyzed Oct 23, 2026score 100/1001 brand signal
Submitted URLhttp://electrum-hub.org/
Favicon Hash
Case ID
Observed page title
Electrum Bitcoin Wallet
Automated brand references
Google
TLS Certificate
Issued by Let's Encrypt / YR2 · stored validity ends in 63 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Canada138.226.253.79
Network ASN
AS43180
AS name
TRUNKNETWORKS-AS Trunk Networks LTD, SC
Organization
COLO
Observed location
CanadaVancouver, CA
Server header
nginx

Nameservers 2

  • ns1.dyna-ns.net
  • ns2.dyna-ns.net

SOA

  • nsname: ns1.dyna-ns.net
  • hostmaster: hostmaster.electrum-hub.org
  • serial: 2026100106
  • refresh: 16384
  • retry: 2048
  • expire: 1209600
  • minttl: 300

Registrar abuse contact VirusTotal WHOIS

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR2
Valid from
2026-10-01 14:00:06
Valid until
2026-12-30 14:00:05
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint3b24f380797114b7404f7dcc27c82ff32ce76b79cf2bc82cea512f63ceab2fed
Certificate names · 2 SANs
  • electrum-hub.org
  • www.electrum-hub.org

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 138.226.253.79rapiddns.io

Latest Classified Outcome 2026-10-27 11:45:07 UTC

The site was redirecting visitors elsewhere at the latest check.

Technical details
Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-27 11:45:07 UTC
RDAP registration
Observed timeline last reachable: 2026-10-25 23:38:17 UTC last content: 2026-10-25 23:38:17 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.
Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.electrum-hub.orgDomain record
Technologies · 1 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

6 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 6 detections
alphaMountain.ai
Forcepoint ThreatSeeker
Gridinsoft
Kaspersky
SOCRadar
VIPRE

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of electrum-hub.org · checked Oct 23, 2026

99
Good
Performance
FCP
1.05 s
First Contentful Paint
LCP
1.58 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
2.97 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://electrum-hub.org/
Electrum Bitcoin Wallet
Electrum Bitcoin Wallet — educational reconstruction of the public download panel.
Response
HTTP 200
HTML body
17.0 KB
Compressed
3.3 KB
Links
0 internal · 44 external
Detected technologies
nginx
Selected response headers
Server: nginx
Content-Type: text/html
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 7
Accept-Ranges
bytes
Connection
keep-alive
Content-Length
17422
Content-Type
text/html
Date
Fri, 23 Oct 2026 01:49:45 GMT
Last-Modified
Thu, 01 Oct 2026 12:25:34 GMT
Server
nginx

Values retained by the collector; long values may be shortened during collection.

Archived
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

Stored observation history8

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

    redirected

    http_redirect

  2. Availability monitor · Recorded state

    live_content→redirected

    http_redirect

  3. Availability monitor · Recorded state

    live_content

    content_served

  4. Availability monitor · Recorded state

    live_content

    content_served

  5. Availability monitor · Recorded state

    live_content

    content_served

Earlier observations 3
  1. VirusTotal · Detection count

    4→6

    Engines added
    Gridinsoft · Kaspersky · VIPRE
    Engines removed
    CRDF
    Recorded vendor total
    6
  2. Availability monitor · Recorded state

    live_content

    content_served

  3. VirusTotal · Detection count

    3→4

    Engines added
    CRDF
    Engines removed
    None recorded
    Recorded vendor total
    4
All retained availability observations26

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.

  1. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:45:07.000000
    Evidence SHA-256
    968c0cdbccc7aa73bc6d25b97243dea295b492e0eaeb8235421efd7ec6d9bd48
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-27 12:45:07
    Evidence reason
    redirect
  2. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:45:07.000000
    Evidence SHA-256
    968c0cdbccc7aa73bc6d25b97243dea295b492e0eaeb8235421efd7ec6d9bd48
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-27 12:45:07
    Evidence reason
    redirect
  3. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 09:55:08.586816
    Evidence SHA-256
    fa8e9b8de0fa2ff3f2c60817f493162c8480eb1a7ff0a28e0a7abc823995c62f
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-27 09:55:08.586816
    Evidence reason
  4. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 04:37:56.000000
    Evidence SHA-256
    54aa377baa1a277a864bfd973f1e57462216e13156dfa28af384617d8c6bd436
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-27 04:37:56
    Evidence reason
    redirect
  5. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    302
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 04:37:56.000000
    Evidence SHA-256
    54aa377baa1a277a864bfd973f1e57462216e13156dfa28af384617d8c6bd436
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-27 04:37:56
    Evidence reason
    redirect
  6. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 12:37:39.000000
    Evidence SHA-256
    d5fca449f2928b143f9332bcaa3e0c7152b02ee2693b1876192b98028a68b3d7
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 12:37:39
    Evidence reason
    alive_content
  7. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 12:37:39.000000
    Evidence SHA-256
    d5fca449f2928b143f9332bcaa3e0c7152b02ee2693b1876192b98028a68b3d7
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 12:37:39
    Evidence reason
    alive_content
  8. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 09:55:08.299319
    Evidence SHA-256
    37b5c19af06da555fb6055130c267aaeda09ed615e57f17df294ffe2591f7ef9
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-26 09:55:08.299319
    Evidence reason
  9. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 00:38:17.000000
    Evidence SHA-256
    5cafc9501a7fa40a8e34d34190f3b06f5241d9110a485dc0191390ea7cd67fbb
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 00:38:17
    Evidence reason
    alive_content
  10. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 00:38:17.000000
    Evidence SHA-256
    5cafc9501a7fa40a8e34d34190f3b06f5241d9110a485dc0191390ea7cd67fbb
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 00:38:17
    Evidence reason
    alive_content
  11. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 12:35:40.000000
    Evidence SHA-256
    78fe2f2a096699c5568a96efce442a5daf08c3fc6ff36283eb80edd29e8aa4d5
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 12:35:40
    Evidence reason
    alive_content
  12. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 12:35:40.000000
    Evidence SHA-256
    78fe2f2a096699c5568a96efce442a5daf08c3fc6ff36283eb80edd29e8aa4d5
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 12:35:40
    Evidence reason
    alive_content
  13. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 09:55:07.418941
    Evidence SHA-256
    f29421045a2f0d44850c6f52d6d8bbdf0829af36630a6ed5c83feca2dfe013b6
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 09:55:07.418941
    Evidence reason
  14. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 04:27:25.000000
    Evidence SHA-256
    9433e67cbf6997a18305c41acfd098e83a405376bb0bc0e72c08daea1132f035
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 04:27:25
    Evidence reason
    alive_content
  15. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 04:27:25.000000
    Evidence SHA-256
    9433e67cbf6997a18305c41acfd098e83a405376bb0bc0e72c08daea1132f035
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 04:27:25
    Evidence reason
    alive_content
  16. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 12:32:13.000000
    Evidence SHA-256
    c840e98233063fe8fd02cd7a3d158e0f0b285014b3d864d80eee002e136721ce
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 12:32:13
    Evidence reason
    alive_content
  17. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 12:32:13.000000
    Evidence SHA-256
    c840e98233063fe8fd02cd7a3d158e0f0b285014b3d864d80eee002e136721ce
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 12:32:13
    Evidence reason
    alive_content
  18. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 10:55:03.666169
    Evidence SHA-256
    3db3280361d0b0da230e0746730e29bf48f3dcd3dc85a990b2931515e779b43a
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-24 10:55:03.666169
    Evidence reason
  19. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 00:34:53.000000
    Evidence SHA-256
    59b68ba94760a0c34a41c5c10a0762daedb4212dde36878f8116e65965acc3b3
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 00:34:53
    Evidence reason
    alive_content
  20. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 00:34:53.000000
    Evidence SHA-256
    59b68ba94760a0c34a41c5c10a0762daedb4212dde36878f8116e65965acc3b3
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 00:34:53
    Evidence reason
    alive_content
  21. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 12:35:51.000000
    Evidence SHA-256
    2120f39523933e9fd09540c826b547649d8418a3a08da6e4c0e5997d474f9d42
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-23 12:35:51
    Evidence reason
    alive_content
  22. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 12:35:51.000000
    Evidence SHA-256
    2120f39523933e9fd09540c826b547649d8418a3a08da6e4c0e5997d474f9d42
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-23 12:35:51
    Evidence reason
    alive_content
  23. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 10:55:00.743425
    Evidence SHA-256
    13567a4852d2464d4e779931d6b58e9a7e4c364f8037d80b364e44546cdc66cf
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-23 10:55:00.743425
    Evidence reason
  24. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 04:11:16.000000
    Evidence SHA-256
    788924c2a7271d146b9411dd7e9f93ee713a8e284555cfc2357eece1240af89f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-23 04:11:16
    Evidence reason
  25. http_observationunknown
    Observation source
    http_observation
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 04:11:16.000000
    Evidence SHA-256
    788924c2a7271d146b9411dd7e9f93ee713a8e284555cfc2357eece1240af89f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-23 04:11:16
    Evidence reason
  26. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 04:02:12.986330
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Notifications · recorded
  4. Monitoring · in progress

Recorded events: 15. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested Recorded: 1 of 1
  • Threat Ingested
    electrum-hub.org detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · Blocklist Detection · OTX Community References · Brand Impersonation · Forensic Evidence Collected · Technical Analysis Recorded · VirusTotal detections +2 · VirusTotal detections +1 Recorded: 12 of 12
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 98
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 6/92
  • Blocklist Detection
    Found in blocklists: MetaMask, SEAL
  • OTX Community References
    Community publication references on AlienVault OTX: 4. References are not vendor verdicts and are excluded from the evidence score.
  • Brand Impersonation
    Automated brand label: Electrum
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, URLQuery, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
  • VirusTotal detections +2
    New detections: +2 (4 → 6): Gridinsoft, Kaspersky, VIPRE
  • VirusTotal detections +1
    New detections: +1 (3 → 4): CRDF
Notification RecordsSent Report Recorded Recorded: 1 of 1
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: Dynadot Inc. Abuse contacts: 1.
    • abuse@dynadot.com
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

6 entries
  1. AlienVault OTX

    4 community references

    View source
  2. VirusTotal

    6/92 engine detections

    View source
  3. Abuse report sent

    PD-20261023-B8D409 · Receipt 81626

    abuse@dynadot.com
  4. URLScan

    Page captured

    View source
  5. Added to PhishDestroy

    electrum-hub.org

    View source
  6. Wayback Machine

    Page archived

    View source
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
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Check for cloaking

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

electrum-hub.org

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 6 det. ChainPatrol URLQuery 2 det. SSL Labs Stored certificate dates valid CF Radar Open report OTX 4 refs WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261023-B8D409 Recipient: abuse@dynadot.com
Page title stored with report: Electrum Bitcoin Wallet
PDF notice generated Notice text archived (291 characters)
Abuse notice text as sent to the provider 
Registrar: Dynadot LLC / Dynadot Inc (United States)
Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains
Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
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
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?

6 evidence signal groups linked 1 stored notification records Last known active
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
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

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
More official reporting routes
FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

Report to Your Local Authorities

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

Even if funds were frozen, they cannot be recovered without an official police report or court order. Submitting a complaint is the only path to potential recovery.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

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 electrum-hub.org)
  • 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

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 →
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/electrum-hub.org"
  title="PhishDestroy threat report for electrum-hub.org"
  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>