Skip to security report
Analytics Dashboard
Crypto Drainer — Listed on PhishDestroy
Stored PhishDestroy threat listing. VirusTotal analysis stored; no vendor detections were recorded at check time. Exercise extreme caution — do not enter credentials or personal information.
Domain security and threat intelligence
qfsconnect.org favicon

qfsconnect.org

In short

qfsconnect.org is a crypto investment scam detected by PhishDestroy on 2026-10-25.

“Web3 Wallet Staking Platform | QFSConnect”

Review the evidence
Registrar
Hostinger
Resolved IP
85.195.85.58
Registered
Jan 28, 2026
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
Stored PhishDestroy threat listing Automated brand label: Arbitrum Scam type: Crypto Drainer
VirusTotal
0 / 92
engine detections ·
OTX
4
community references
Cloudflare Radar
clean
source verdict
Page captures
5
open gallery
Domain age
271 days
Reports sent
1
view timeline
OTX: 4 refs Oct 25, 2026 1 Report Sent
X Telegram API

Analysis

Domain summary

qfsconnect.org is a crypto investment scam detected by PhishDestroy on 2026-10-25. Risk: critical (73/100). Registrar: Hostinger. Status: Last known active. Hosting: velia.net Internetdienste GmbH. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.

Critical
VirusTotal
0 / 92
OTX
4 community refs
Page captures
5
Page captures Source results Registration record

PhishDestroy threat report

Overview

PhishDestroy’s automated assessment classified qfsconnect.org as a crypto‑wallet drainer because the page advertises a Web3 staking service and displays a “Connect Wallet” button. The intake AI noted a 90% confidence score and the domain age of 269 days as supporting signals. The site returned HTTP 200 on 2026-10-25 and the recorded title was “Web3 Wallet Staking Platform | QFSConnect”.

How the scam works

A crypto‑wallet drainer pretends to be a legitimate staking or DeFi platform and asks visitors to connect their cryptocurrency wallet. Once the user authorises the connection, the attacker can request token transfers or approve contracts that move funds out of the wallet.

Evidence

VirusTotal scanned the domain on 2026-07-31 (retrieved 2026-10-25) and reported 0 malicious and 0 suspicious detections from 92 engines. Google Safe Browsing checked on 2026-10-25 and did not flag the site. OTX listed four pulses referencing the domain as of 2026-10-25, none assigning a malicious verdict. urlscan.io captured the page on 2026-10-25; its machine‑learning engine gave a malicious score of 89 and tagged the page as malicious, while the overall verdict was non‑malicious. PhishDestroy’s internal blocklist contains qfsconnect.org, and external blocklists as well as Spamhaus DBL reported no entries on 2026-10-25.

Infrastructure

The domain was registered on 2026-01-28 through HOSTINGER operations, UAB, giving it 269 days of age at the time of capture. The recorded DNS entry listed the A record 85.195.85.58, which was associated with ASN 29066 (velia.net Internetdienste GmbH) and the GeoIP data showed Frankfurt, Germany. The site presented a TLS 1.3 certificate issued by Let’s Encrypt, valid from 2026-09-30 to 2026-12-29, and HTTP headers identified the server as LiteSpeed; open ports observed included 21, 25, 53, 80, 110, 143, 443, 587, 993, 995 and 3306.

What to do

If you visited the site and connected a wallet, immediately revoke any approvals and move assets to a new wallet; do not enter seed phrases or private keys on the site. Defenders should add qfsconnect.org to web‑traffic blocklists and monitor for outbound connections to the recorded IP, while avoiding blanket IP blocking.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportURLQuery reportStored capture screenshotCloudflare Radar screenshot (2026-10-25T03:51:37Z)URLQuery screenshotVirusTotal reportGoogle Safe Browsing statusArchived copyRevoke token approvalsReport crypto fraud (Chainabuse)Report phishing to GoogleSite owner? Request a review
Source evidenceVirusTotal 0 / 92 · OTX 4 references 9 sources

URLScan

Malicious · engine verdict · score 89

Open report
URLScanOriginal source recordObserved: 21 fields

Observed: · Retrieved:

Report ID

01a17108-71b4-757f-828d-e14668992e47

Final URL

https://qfsconnect.org/

HTTP response

200

IP address

85.195.85.58

Reverse DNS (PTR)

de6000-r.iaasdns.com

Contacted domains

  • fonts.bunny.net
  • cdn.jsdelivr.net
  • bootstrap.smartsuppchat.com
  • www.smartsuppchat.com
  • cdnjs.cloudflare.com

Contacted IP addresses

  • 3.125.68.253
  • 152.233.11.105
  • 104.17.25.14
  • 151.101.129.229
  • 79.127.243.187
  • 85.195.85.58

Autonomous systems (ASN)

  • 16509
  • 60068
  • 13335
  • 54113
  • 29066

Server countries

  • DE
  • US

Document hash

40e5a520c7bedec351c47e4daff9aeaaf80865d0c472d5ba556634081d0433cd

Script hashes

  • 855ee51a38ba95465d988635e3e6d37b7e7c17bc3aaa0231126664b3eca958be

JavaScript globals

  • Shepherd
  • _smartsupp
  • smartsupp
  • axios
  • Alpine
  • SMARTSUPP_LOADED
  • $smartsupp

Cookies

  • XSRF-TOKEN
  • qfsconnect-session

TLS session and certificate

Subject alternative names
  • *.qfsconnect.org
  • qfsconnect.org
Cipher
AES_128_GCM
Issuer
YR1
Subject
qfsconnect.org
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

269

Registered domain age, days

269

Certificate age, days

24

Certificate validity, days

89

Page requests

15

Provider verdicts

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

HTTP headers

Server
LiteSpeed
Content-type
text/html; charset=utf-8
X-powered-by
PHP/8.4.27
Original source fields · JSON
Uuid
01a17108-71b4-757f-828d-e14668992e47
Final url
https://qfsconnect.org/
Status
200
Ip
85.195.85.58
Ptr
de6000-r.iaasdns.com
Contacted domains
[
    "fonts.bunny.net",
    "cdn.jsdelivr.net",
    "bootstrap.smartsuppchat.com",
    "www.smartsuppchat.com",
    "cdnjs.cloudflare.com"
]
Contacted IP addresses
[
    "3.125.68.253",
    "152.233.11.105",
    "104.17.25.14",
    "151.101.129.229",
    "79.127.243.187",
    "85.195.85.58"
]
Asns
[
    "16509",
    "60068",
    "13335",
    "54113",
    "29066"
]
Countries
[
    "DE",
    "US"
]
Document hash
40e5a520c7bedec351c47e4daff9aeaaf80865d0c472d5ba556634081d0433cd
Script hashes
[
    "855ee51a38ba95465d988635e3e6d37b7e7c17bc3aaa0231126664b3eca958be"
]
Globals
[
    "Shepherd",
    "_smartsupp",
    "smartsupp",
    "axios",
    "Alpine",
    "SMARTSUPP_LOADED",
    "$smartsupp"
]
Cookies
[
    "XSRF-TOKEN",
    "qfsconnect-session"
]
Tls
{
    "san": [
        "*.qfsconnect.org",
        "qfsconnect.org"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YR1",
    "subject": "qfsconnect.org",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-29T03:33:46Z",
    "valid_from": "2026-09-30T03:33:47Z"
}
Domain age days
269
Apex age days
269
Tls age days
24
Tls valid days
89
Requests
15
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 89,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "LiteSpeed",
    "content-type": "text/html; charset=utf-8",
    "x-powered-by": "PHP/8.4.27"
}
Separate monitor record · 2026-10-25 04:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a17108-71b4-757f-828d-e14668992e47
score
0
malicious
false
result_at
2026-10-25T04:30:45Z
enriched_at
2026-10-26T09:21:12Z
source_timestamps
{"urlscan_result_at":"2026-10-25 05:30:45","urlscan_enriched_at":"2026-10-26 10:21:12"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

VirusTotal

0 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 10 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
56
Malicious
0
Suspicious
0
Undetected
36

Reputation score

0

Created

Updated

First seen

DNS records

  • TTL, seconds
    14400
    Type
    A
    Value
    85.195.85.58
  • TTL, seconds
    21600
    Type
    SOA
    Responsible mailbox
    biz\.urdesigner.gmail.com
    Value
    ns1.betahostit.com
  • TTL, seconds
    14400
    Type
    MX
    Value
    qfsconnect.org
    Priority
    0
  • TTL, seconds
    14400
    Type
    TXT
    Value
    v=spf1 +a +mx +ip4:85.195.85.58 include:relay.mailbaby.net ~all
  • TTL, seconds
    21600
    Type
    NS
    Value
    ns1.betahostit.com
  • TTL, seconds
    21600
    Type
    NS
    Value
    ns2.betahostit.com

DNS records observed

JARM fingerprint

29d29d00029d29d00042d43d00041d598ac0c1012db967bb1ad0ff2491b3ae

Certificate

Subject alternative names
  • *.qfsconnect.org
  • qfsconnect.org
Issuer
Let's Encrypt / YR1
Serial
54a376570910fee72dde313d85fa5393211
SHA-256
4c178dd7526c0db36fa77eee1467d8be38f820b988801e50dd16d8a0ed2a29d4
Subject
*.qfsconnect.org
Valid until
Valid from

Registry data (RDAP)

Status
  • client transfer prohibited
Registry events
Expiration
Last changed
Registration
Last RDAP database update
Registrar
HOSTINGER operations, UAB
Registrar IANA ID
1636
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 56,
    "malicious": 0,
    "suspicious": 0,
    "undetected": 36
}
Reputation
0
Created
2026-01-28T00:00:00Z
Updated
2026-01-28T00:00:00Z
First seen
2026-01-28T08:48:54Z
DNS records
[
    {
        "ttl": 14400,
        "type": "A",
        "value": "85.195.85.58"
    },
    {
        "ttl": 21600,
        "type": "SOA",
        "rname": "biz\\.urdesigner.gmail.com",
        "value": "ns1.betahostit.com"
    },
    {
        "ttl": 14400,
        "type": "MX",
        "value": "qfsconnect.org",
        "priority": 0
    },
    {
        "ttl": 14400,
        "type": "TXT",
        "value": "v=spf1 +a +mx +ip4:85.195.85.58 include:relay.mailbaby.net ~all"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns1.betahostit.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns2.betahostit.com"
    }
]
Dns at
2026-07-31T06:05:52Z
Jarm
29d29d00029d29d00042d43d00041d598ac0c1012db967bb1ad0ff2491b3ae
Certificate
{
    "san": [
        "*.qfsconnect.org",
        "qfsconnect.org"
    ],
    "issuer": "Let's Encrypt / YR1",
    "serial": "54a376570910fee72dde313d85fa5393211",
    "sha256": "4c178dd7526c0db36fa77eee1467d8be38f820b988801e50dd16d8a0ed2a29d4",
    "subject": "*.qfsconnect.org",
    "valid_to": "2026-10-29T03:43:01Z",
    "valid_from": "2026-07-31T03:43:02Z"
}
Registry data
{
    "status": [
        "client transfer prohibited"
    ],
    "events": {
        "expiration": "2027-01-28T08:23:05Z",
        "last changed": "2026-02-02T08:23:23Z",
        "registration": "2026-01-28T08:23:05Z",
        "last update of RDAP database": "2026-07-31T06:05:51Z"
    },
    "registrar": "HOSTINGER operations, UAB",
    "registrar_iana_id": "1636"
}
Separate source record · 0 malicious + 0 suspicious / 92 · 2026-07-31 05:57:03 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-07-31T05:57:03Z
fetched_at
2026-10-25T03:49:51Z
stats
{"timeout":0,"harmless":56,"malicious":0,"suspicious":0,"undetected":36}

OTX

4 community references

Open report

Cloudflare Radar

provider verdict: clean

Not recorded
Open report
Cloudflare RadarOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Report ID

73a91cec-2e86-46aa-9b53-77b38b5e0d7d

Final URL

https://qfsconnect.org/

HTTP response

200

Navigation history

  • URL
    https://qfsconnect.org/
    Status
    200

DOM structure hash

c85783fdf902dd0f59e8611e6acdf988de712e2b88e9b1cae653958e8eda15b8

Document hash

184f0bcb5aa2c8af9785ec05fbbe5ef9b3dd59930a2f505d119adcf8cc625780

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    qfsconnect.org
    Type
    A
    Value
    85.195.85.58

DNSSEC valid

No

IP address

85.195.85.58

Registration record

Registrar
HOSTINGER operations, UAB
Registered
Updated
Expires
Nameservers
  • ns41.dnsiaas.com
  • ns42.dnsiaas.com
Original source fields · JSON
Uuid
73a91cec-2e86-46aa-9b53-77b38b5e0d7d
Final url
https://qfsconnect.org/
Status
200
History
[
    {
        "url": "https://qfsconnect.org/",
        "status": 200
    }
]
DOM structure hash
c85783fdf902dd0f59e8611e6acdf988de712e2b88e9b1cae653958e8eda15b8
Document hash
184f0bcb5aa2c8af9785ec05fbbe5ef9b3dd59930a2f505d119adcf8cc625780
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "qfsconnect.org",
        "type": "A",
        "value": "85.195.85.58"
    }
]
Dnssec valid
false
Ip
85.195.85.58
Registration record
{
    "registrar": "HOSTINGER operations, UAB",
    "created": "2026-01-28T08:23:05Z",
    "updated": "2026-08-12T03:25:43Z",
    "expires": "2027-01-28T08:23:05Z",
    "nameservers": [
        "ns41.dnsiaas.com",
        "ns42.dnsiaas.com"
    ]
}

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

73 / 100 · heuristic score · 5 brand references · 1 classifications

Open report
Separate monitor score · 90 / 100 · 2026-10-25T03:20:44Z

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

record_source
domain_monitor.dom_analysis
heuristic_score
90
analyzed_at
2026-10-25T03:20:44Z
source_timestamp
2026-10-25 04:20:44
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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
qfsconnect.org — Crypto Drainer
ai_description
PhishDestroy flagged qfsconnect.org on 2026-10-25 as a crypto‑wallet drainer after detecting a Web3 staking page that prompts users to “Connect Wallet”.
ai_generated_at
2026-10-25T03:55:32Z
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: 23 fields

Mail configuration

MX records
  • qfsconnect.org
SPF record
v=spf1 +a +mx +ip4:85.195.85.58 include:relay.mailbaby.net ~all
DKIM
  • default
DMARC
Yes
DKIM key size, bits
2048
SPF lookups
5

CAA records

Domain
qfsconnect.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
9615

Crawler rules

User agents
  • *
Present
Yes

Page title and metadata

Page title
Web3 Wallet Staking Platform | QFSConnect
Theme color
#0f172a

Forms and mixed content

Scripts without SRI
  • https://cdn.jsdelivr.net/npm/alpinejs@3.x.x/dist/cdn.min.js
  • https://cdn.jsdelivr.net/npm/shepherd.js@10/dist/js/shepherd.min.js
Third-party scripts
2

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
4
TLS
229
Waiting
90
Connection
7
Download
18
Response time, ms
348

TLS connection

ALPN
h2
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
  • 25
  • 53
  • 80
  • 110
  • 143
  • 443
  • 587
  • 993
  • 995
  • 3306

Carbon estimate

Bytes
36963
CO₂, grams
0.0014
Cleaner than, %
43

DNS servers

Nameservers
  • Host
    ns2.betahostit.com
  • Host
    ns1.betahostit.com
DNS zone
qfsconnect.org

Location

IP address
85.195.85.58
ASN
29066
Organization
velia.net Internetdienste GmbH
City
Frankfurt am Main
Country
DE

TLS certificate

Issuer
Let's Encrypt / YR1
Subject
qfsconnect.org

DNS records

A
  • 85.195.85.58
MX
  • Mail server
    qfsconnect.org
    Priority
    0
NS
  • ns2.betahostit.com
  • ns1.betahostit.com
SOA
Primary nameserver
ns1.betahostit.com
Hostmaster
biz\.urdesigner.gmail.com
Serial
2026093001
Refresh, seconds
3600
Retry, seconds
1800
Expiry, seconds
1209600
Minimum TTL, seconds
86400
TXT
  • v=spf1 +a +mx +ip4:85.195.85.58 include:relay.mailbaby.net ~all

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
85.195.85.58
IP version
4

Redirects

Redirect chain
  • https://qfsconnect.org

Page links

Internal links
6

Registration record

Registrar
HOSTINGER operations, UAB
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • ns41.dnsiaas.com
  • ns42.dnsiaas.com

HTTP headers

Response headers
Server
LiteSpeed
Content-type
text/html; charset=utf-8
X-powered-by
PHP/8.4.27
Original source fields · JSON
Mail configuration
{
    "mx": [
        "qfsconnect.org"
    ],
    "spf": "v=spf1 +a +mx +ip4:85.195.85.58 include:relay.mailbaby.net ~all",
    "dkim": [
        "default"
    ],
    "dmarc": true,
    "dkim_bits": 2048,
    "spf_lookups": 5
}
Caa records
{
    "domain": "qfsconnect.org"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-10-25T03:11:31Z",
    "first": "2026-10-25T03:11:31Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 9615
}
Crawler rules
{
    "agents": [
        "*"
    ],
    "present": true
}
Page title and metadata
{
    "title": "Web3 Wallet Staking Platform |  QFSConnect",
    "themeColor": "#0f172a"
}
Forms and mixed content
{
    "no_sri": [
        "https://cdn.jsdelivr.net/npm/alpinejs@3.x.x/dist/cdn.min.js",
        "https://cdn.jsdelivr.net/npm/shepherd.js@10/dist/js/shepherd.min.js"
    ],
    "third_party_scripts": 2
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 4,
        "tls": 229,
        "wait": 90,
        "connect": 7,
        "download": 18
    },
    "response_ms": 348
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        21,
        25,
        53,
        80,
        110,
        143,
        443,
        587,
        993,
        995,
        3306
    ]
}
Carbon
{
    "bytes": 36963,
    "co2_grams": 0.0014,
    "cleaner_than": 43
}
Dns server
{
    "ns": [
        {
            "host": "ns2.betahostit.com"
        },
        {
            "host": "ns1.betahostit.com"
        }
    ],
    "zone": "qfsconnect.org"
}
Location
{
    "ip": "85.195.85.58",
    "asn": "29066",
    "org": "velia.net Internetdienste GmbH",
    "city": "Frankfurt am Main",
    "country": "DE"
}
Ssl
{
    "issuer": "Let's Encrypt / YR1",
    "subject": "qfsconnect.org"
}
DNS records
{
    "A": [
        "85.195.85.58"
    ],
    "MX": [
        "{\"exchange\": \"qfsconnect.org\", \"priority\": 0}"
    ],
    "NS": [
        "ns2.betahostit.com",
        "ns1.betahostit.com"
    ],
    "SOA": "{\"nsname\": \"ns1.betahostit.com\", \"hostmaster\": \"biz\\\\.urdesigner.gmail.com\", \"serial\": 2026093001, \"refresh\": 3600, \"retry\": 1800, \"expire\": 1209600, \"minttl\": 86400}",
    "TXT": [
        "v=spf1 +a +mx +ip4:85.195.85.58 include:relay.mailbaby.net ~all"
    ]
}
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": "85.195.85.58",
    "family": 4
}
Redirects
{
    "chain": [
        "https://qfsconnect.org"
    ]
}
Page links
{
    "internal_count": 6
}
Registration record
{
    "registrar": "HOSTINGER operations, UAB",
    "created": "2026-01-28T08:23:05Z",
    "updated": "2026-08-12T03:25:43Z",
    "expires": "2027-01-28T08:23:05Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "ns41.dnsiaas.com",
        "ns42.dnsiaas.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "LiteSpeed",
        "content-type": "text/html; charset=utf-8",
        "x-powered-by": "PHP/8.4.27"
    }
}

Questions about qfsconnect.org

Is qfsconnect.org legit?

No. PhishDestroy classifies qfsconnect.org as a crypto investment scam (risk: critical, 73/100); it was first detected on 2026-10-25. Treat the site as unsafe.

Is qfsconnect.org safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on qfsconnect.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 qfsconnect.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 matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 5 captures

Primary capture 1 / 5
SourcePrimary capture
Recorded
StateStored capture
HTTP statusNot recorded for this capture
Final URLNot recorded for this capture
Position1 / 5
Open capture Wayback Download
All capture links and hashes (5)

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation abuse score 0/100 1 report PhishingEmail Spam checked Oct 25, 2026
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Hostinger LT(LT)
Abuse contactabuse@velia.net, abuse@hostinger.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for qfsconnect.org →
Hosting abuse contact abuse@velia.net velia.net Internetdienste GmbH · AS29066
RegistrationCreated Jan 28, 2026 (271d) — Expires Jan 28, 2027
HTTP Status302 Found (Temporary)
Technical detailsProvenance & timestamps
First DetectedOct 25, 2026
DOM Analysisanalyzed Oct 25, 2026score 73/1005 brand signals
Submitted URLhttps://qfsconnect.org/
Favicon Hash
Case ID
Observed page title
Web3 Wallet Staking Platform | QFSConnect
Automated brand references
Arbitrum Coinbase Discord MetaMask Polygon
TLS Certificate
Issued by YR1 · stored validity ends in 63 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
85.195.85.58
Network ASN
AS29066
Organization
RackNerd, LLC
Observed location
Frankfurt am Main, DE
Server header
LiteSpeed

Nameservers 4

  • ns1.betahostit.com
  • ns2.betahostit.com
  • ns41.dnsiaas.com
  • ns42.dnsiaas.com

Mail routing 1 MX record

  • qfsconnect.orgpriority 0

Location describes the IP network.

TLS certificate

Issuer
YR1
Valid from
2026-09-30 03:33:47
Valid until
2026-12-29 03:33:46
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint4c178dd7526c0db36fa77eee1467d8be38f820b988801e50dd16d8a0ed2a29d4
Certificate names · 2 SANs
  • *.qfsconnect.org
  • qfsconnect.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 · 85.195.85.58rapiddns.io

Latest Classified Outcome 2026-10-25 23:23:11 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: Unknown Content: Unknown DNS: Stale Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-25 23:23:11 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-25 03:09:57 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.qfsconnect.orgDomain record

The original observation time is not recorded for these hostnames.

Technologies · 6 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of qfsconnect.org · checked Oct 25, 2026

88
Needs Work
Performance
FCP
2.43 s
First Contentful Paint
LCP
2.73 s
Largest Contentful Paint
CLS
0.137
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
2.64 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: https://qfsconnect.org/
Web3 Wallet Staking Platform | QFSConnect
Response
HTTP 200
HTML body
36.1 KB
Compressed
6.7 KB
Links
18 internal · 1 external
Selected response headers
X-Powered-By: PHP/8.4.27
Content-Type: text/html; charset=utf-8
Cache-Control: no-cache, private
Content-Encoding: gzip
Server: LiteSpeed
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 11
alt-svc
h3=":443"; ma=2592000, h3-29=":443"; ma=2592000
Cache-Control
no-cache, private
Connection
Keep-Alive
Content-Encoding
gzip
Content-Length
8151
Content-Type
text/html; charset=utf-8
Date
Sun, 25 Oct 2026 03:10:15 GMT
Keep-Alive
timeout=5, max=100
Server
LiteSpeed
Vary
Accept-Encoding
X-Powered-By
PHP/8.4.27

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

Archived
Registration & observation details1

Availability observations

Last reachable observation

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.

Page titles differ

redirect: raw=redirect_302; http=302; via=https_proxy; location=https://qfsconnect.org/cgi-sys/suspendedpage.cgi; server=LiteSpeed

Browser
Web3 Wallet Staking Platform | QFSConnect
Crawler
302 Found
qfsconnect.org
Stored observation history3

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

    live_content→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Domain monitor · First collection record

    Reachable

All retained availability observations6

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
    stale
    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-26 00:23:11.000000
    Evidence SHA-256
    9d3f9f0a653195887e50b1893bf6337321970f8d194d2645d65acf5c0bc35642
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-26 00:23:11
    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-26 00:23:11.000000
    Evidence SHA-256
    9d3f9f0a653195887e50b1893bf6337321970f8d194d2645d65acf5c0bc35642
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-26 00:23:11
    Evidence reason
    redirect
  3. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    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:20:48.000000
    Evidence SHA-256
    4fcdf4a9ae98a79fac194832a9eeee1d7174740f0e04bc0ef1e9f4a10f457734
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 12:20:48
    Evidence reason
    alive_content
  4. 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:20:48.000000
    Evidence SHA-256
    4fcdf4a9ae98a79fac194832a9eeee1d7174740f0e04bc0ef1e9f4a10f457734
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 12:20:48
    Evidence reason
    alive_content
  5. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    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-25 04:09:57.000000
    Evidence SHA-256
    f5e0edb7c4b1b368390c28e869de67642947ea08a033ef9a06d9aec7e442f2af
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 04:09:57
    Evidence reason
  6. 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-25 04:09:57.000000
    Evidence SHA-256
    f5e0edb7c4b1b368390c28e869de67642947ea08a033ef9a06d9aec7e442f2af
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 04:09:57
    Evidence reason

Recorded activity

6 entries
  1. AlienVault OTX

    4 community references

    View source
  2. VirusTotal

    0/92 engine detections

    View source
  3. Abuse report sent

    PD-20261025-3FFEA6

    abuse@velia.net
  4. Wayback Machine

    Page archived

    View source
  5. Added to PhishDestroy

    qfsconnect.org

    View source
  6. URLScan

    Page captured

    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

Lookalike domains

28 stored lookalike domains

a.rbitrum.io subdomain abitrum.io omission abritrum.io transposition arbbitrum.io repetition arbiitrum.io repetition arbirtum.io transposition arbirum.io omission arbit.rum.io subdomain arbitr.um.io subdomain arbitram.io vowel-swap arbitrium.io insertion arbitrm.io omission
Show all (16)
arbitrmu.io transposition arbitru.io omission arbitruum.io repetition arbittrum.io insertion arbitum.io omission arbiturm.io transposition arbtirum.io transposition arbtrum.io omission aribtrum.io transposition aritrum.io omission rabitrum.io transposition rbitrum.io omission arbitrrum.io insertion arbitrumm.io addition arbitrun.io homoglyph xn--rbitrum-r3a.io homoglyph

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal ChainPatrol URLQuery Report stored 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-20261025-3FFEA6 Recipient: abuse@velia.net
Page title stored with report: Web3 Wallet Staking Platform | QFSConnect
PDF notice generated
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?

5 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
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 →.

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