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

clients-qba.site

In short

PhishDestroy first recorded clients-qba.site on 2026-10-29. VirusTotal: 15/92 engines flag it.

“Intuit”

Review the evidence
Registrar
RussiaRegistrar of Domain Na…
Resolved IP
Russia31.31.196.17Reg.Ru-Exepto
First observed
Oct 29, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 15/92
VirusTotal
15 / 92
engine detections ·
URLScan
Malicious
engine verdict · score 98
Page captures
6
open gallery
Oct 29, 2026
X Telegram API

Questions about clients-qba.site

Is clients-qba.site legit?

PhishDestroy rates clients-qba.site as critical risk (100/100) from the recorded evidence; it was first recorded on 2026-10-29. VirusTotal: 15/92 engines flag it. Treat the site as unsafe.

Is clients-qba.site safe to connect a wallet?

This report does not record which wallet requests clients-qba.site makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.

What should I do if I used clients-qba.site?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Source evidenceVirusTotal 15 / 92 7 sources

VirusTotal

15 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 16 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
45
Malicious
14
Suspicious
1
Undetected
32

Vendor labels

CRDF
malicious
ESET
phishing
G-Data
phishing
Sophos
phishing
Fortinet
phishing
SOCRadar
suspicious
URLQuery
malicious
Kaspersky
phishing
LevelBlue
phishing
OpenPhish
phishing
Gridinsoft
phishing
MalwareURL
phishing
BitDefender
phishing
alphaMountain.ai
malicious
Forcepoint ThreatSeeker
phishing

Reputation score

0

Tags

  • dga

Categories

Sophos
phishing and fraud
alphaMountain.ai
Malicious (alphaMountain.ai)
Forcepoint ThreatSeeker
phishing and other frauds

Registrar

Registrar of Domain Names REG.RU LLC

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    3600
    Type
    NS
    Value
    ns1.hosting.reg.ru
  • TTL, seconds
    3600
    Type
    SOA
    Responsible mailbox
    support.reg.ru
    Value
    server256.hosting.reg.ru
  • TTL, seconds
    3600
    Type
    A
    Value
    31.31.196.17
  • TTL, seconds
    3600
    Type
    NS
    Value
    ns2.hosting.reg.ru
  • TTL, seconds
    3600
    Type
    TXT
    Value
    v=spf1 ip4:31.31.196.17 a mx include:_spf.hosting.reg.ru ~all
  • TTL, seconds
    3600
    Type
    AAAA
    Value
    2a00:f940:2:2:1:1:0:256

DNS records observed

JARM fingerprint

29d29d00029d29d00042d42d0000002059a3b916699461c5923779b77cf06b

Certificate

Subject alternative names
  • *.hosting.reg.ru
  • hosting.reg.ru
Issuer
GlobalSign nv-sa / GlobalSign GCC R6 AlphaSSL CA 2025
Serial
30773007dc14191d5e3e940d
SHA-256
00f0f262cc5fee43e60750021b642577660fe3261147986f15036f0439d6ade7
Subject
*.hosting.reg.ru
Valid until
Valid from

Registration record

Registrar
Registrar of Domain Names REG.RU LLC
Registrar IANA ID
1606
Registrar URL
https://reg.ru
Registered
Updated
Expires
Status
  • addPeriod
  • clientTransferProhibited
Nameservers
  • ns1.hosting.reg.ru
  • ns2.hosting.reg.ru
DNSSEC
unsigned

Registry data (RDAP)

Status
  • client transfer prohibited
Registry events
Expiration
Registration
Registrar expiration
Last RDAP database update
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 45,
    "malicious": 14,
    "suspicious": 1,
    "undetected": 32
}
Vendor labels
{
    "CRDF": "malicious",
    "ESET": "phishing",
    "G-Data": "phishing",
    "Sophos": "phishing",
    "Fortinet": "phishing",
    "SOCRadar": "suspicious",
    "URLQuery": "malicious",
    "Kaspersky": "phishing",
    "LevelBlue": "phishing",
    "OpenPhish": "phishing",
    "Gridinsoft": "phishing",
    "MalwareURL": "phishing",
    "BitDefender": "phishing",
    "alphaMountain.ai": "malicious",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Categories
{
    "Sophos": "phishing and fraud",
    "alphaMountain.ai": "Malicious (alphaMountain.ai)",
    "Forcepoint ThreatSeeker": "phishing and other frauds"
}
Registrar
Registrar of Domain Names REG.RU LLC
Created
2026-10-27T13:20:48Z
Expires
2027-10-27T13:20:48Z
Updated
2026-10-27T13:20:48Z
First seen
2026-10-27T13:45:38Z
DNS records
[
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns1.hosting.reg.ru"
    },
    {
        "ttl": 3600,
        "type": "SOA",
        "rname": "support.reg.ru",
        "value": "server256.hosting.reg.ru"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "31.31.196.17"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns2.hosting.reg.ru"
    },
    {
        "ttl": 3600,
        "type": "TXT",
        "value": "v=spf1 ip4:31.31.196.17 a mx include:_spf.hosting.reg.ru ~all"
    },
    {
        "ttl": 3600,
        "type": "AAAA",
        "value": "2a00:f940:2:2:1:1:0:256"
    }
]
Dns at
2026-10-28T22:18:22Z
Jarm
29d29d00029d29d00042d42d0000002059a3b916699461c5923779b77cf06b
Certificate
{
    "san": [
        "*.hosting.reg.ru",
        "hosting.reg.ru"
    ],
    "issuer": "GlobalSign nv-sa / GlobalSign GCC R6 AlphaSSL CA 2025",
    "serial": "30773007dc14191d5e3e940d",
    "sha256": "00f0f262cc5fee43e60750021b642577660fe3261147986f15036f0439d6ade7",
    "subject": "*.hosting.reg.ru",
    "valid_to": "2027-03-06T12:07:58Z",
    "valid_from": "2026-02-02T12:07:59Z"
}
Registration record
{
    "registrar": "Registrar of Domain Names REG.RU LLC",
    "registrar_iana_id": "1606",
    "registrar_url": "https://reg.ru",
    "created": "2026-10-27T13:20:48Z",
    "updated": "2026-10-27T13:20:48Z",
    "expires": "2027-10-27T13:20:48Z",
    "status": [
        "addPeriod",
        "clientTransferProhibited"
    ],
    "nameservers": [
        "ns1.hosting.reg.ru",
        "ns2.hosting.reg.ru"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "client transfer prohibited"
    ],
    "events": {
        "expiration": "2027-10-27T13:20:49Z",
        "registration": "2026-10-27T13:20:49Z",
        "registrar expiration": "2027-10-27T13:20:49Z",
        "last update of RDAP database": "2026-10-27T13:43:20Z"
    }
}
Separate source record · 14 malicious + 1 suspicious / 92 · 2026-10-28 22:17:47 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-28T22:17:47Z
fetched_at
2026-10-29T00:40:01Z
stats
{"timeout":0,"harmless":45,"malicious":14,"suspicious":1,"undetected":32}

Cloudflare Radar

Malicious

Open report
Cloudflare RadarOriginal source recordObserved: 10 fields

Observed: · Retrieved:

Report ID

5b8f085f-167b-4a1c-8b36-d1e08d01f813

Final URL

https://clients-qba.site/

Navigation history

  • URL
    https://clients-qba.site/
    Status
    0

DOM structure hash

94bfc7c24186e5b245b5675859fb84b248547086370961e5637590177432b219

Domain risk categories

  • Newly Seen Domains
  • Security Risks
  • Phishing
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    clients-qba.site
    Type
    A
    Value
    31.31.196.17
  • Name
    clients-qba.site
    Type
    AAAA
    Value
    2a00:f940:2:2:1:1:0:256

DNSSEC valid

No

Verdict

Tags
  • phishing
Malicious
Yes
Categories
  • phishing

Registration record

Registrar
Registrar of Domain Names REG.RU LLC
Registered
Updated
Expires
Nameservers
  • ns1.hosting.reg.ru
  • ns2.hosting.reg.ru
Original source fields · JSON
Uuid
5b8f085f-167b-4a1c-8b36-d1e08d01f813
Final url
https://clients-qba.site/
History
[
    {
        "url": "https://clients-qba.site/",
        "status": 0
    }
]
DOM structure hash
94bfc7c24186e5b245b5675859fb84b248547086370961e5637590177432b219
Domain risks
[
    "Newly Seen Domains",
    "Security Risks",
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "clients-qba.site",
        "type": "A",
        "value": "31.31.196.17"
    },
    {
        "name": "clients-qba.site",
        "type": "AAAA",
        "value": "2a00:f940:2:2:1:1:0:256"
    }
]
Dnssec valid
false
Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Registration record
{
    "registrar": "Registrar of Domain Names REG.RU LLC",
    "created": "2026-10-27T13:20:48Z",
    "updated": "2026-10-27T13:20:48Z",
    "expires": "2027-10-27T13:20:48Z",
    "nameservers": [
        "ns1.hosting.reg.ru",
        "ns2.hosting.reg.ru"
    ]
}

URLScan

Malicious · engine verdict · score 98

SHA-256 5f8cb7453e7eb3fd20ef20249911824a8b0c553237c39d2c285e20bf3c170f07

Open report
URLScanOriginal source recordObserved: 20 fields

Observed: · Retrieved:

Report ID

01a18360-84b0-770f-ba6e-0a2bcbd063dc

Final URL

https://clients-qba.site/

HTTP response

200

IP address

2a00:f940:2:2:1:1:0:141

Contacted domains

  • domengrain.cfd

Contacted IP addresses

  • 13.143.133.139
  • 2a00:f940:2:2:1:1:0:141

Autonomous systems (ASN)

  • 201988
  • 197695

Server countries

  • DE
  • RU

Document hash

a7df83afd09767a22259c56bc046732e7d058355be81e55c4938366e41c2b280

JavaScript globals

  • Pt
  • Dn
  • kn
  • Gt
  • Yt
  • Fr
  • ga
  • Re
  • q
  • O
  • E
  • D
  • Tr
  • lt
  • Mt
  • xe
  • X
  • xr
  • je
  • In
  • Ze
  • ce
  • et
  • Je
  • Ft
  • tt
  • Nn
  • Ue
  • ae
  • Cr
  • Ur
  • Ce
  • zt
  • On
  • Rt
  • W
  • Br
  • B
  • Pn
  • Mn

Cookies

  • mlid

Browser storage keys

  • fs-cid
  • fs_token

TLS session and certificate

Subject alternative names
  • *.clients-qba.site
  • clients-qba.site
Cipher
AES_256_GCM
Issuer
YR1
Subject
clients-qba.site
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

0

Registered domain age, days

0

Certificate age, days

1

Certificate validity, days

89

Page requests

3

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; charset=utf-8
Strict-transport-security
max-age=31536000;
Original source fields · JSON
Uuid
01a18360-84b0-770f-ba6e-0a2bcbd063dc
Final url
https://clients-qba.site/
Status
200
Ip
2a00:f940:2:2:1:1:0:141
Contacted domains
[
    "domengrain.cfd"
]
Contacted IP addresses
[
    "13.143.133.139",
    "2a00:f940:2:2:1:1:0:141"
]
Asns
[
    "201988",
    "197695"
]
Countries
[
    "DE",
    "RU"
]
Document hash
a7df83afd09767a22259c56bc046732e7d058355be81e55c4938366e41c2b280
Globals
[
    "Pt",
    "Dn",
    "kn",
    "Gt",
    "Yt",
    "Fr",
    "ga",
    "Re",
    "q",
    "O",
    "E",
    "D",
    "Tr",
    "lt",
    "Mt",
    "xe",
    "X",
    "xr",
    "je",
    "In",
    "Ze",
    "ce",
    "et",
    "Je",
    "Ft",
    "tt",
    "Nn",
    "Ue",
    "ae",
    "Cr",
    "Ur",
    "Ce",
    "zt",
    "On",
    "Rt",
    "W",
    "Br",
    "B",
    "Pn",
    "Mn"
]
Cookies
[
    "mlid"
]
Storage keys
[
    "fs-cid",
    "fs_token"
]
Tls
{
    "san": [
        "*.clients-qba.site",
        "clients-qba.site"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "YR1",
    "subject": "clients-qba.site",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-25T12:34:56Z",
    "valid_from": "2026-10-27T12:34:57Z"
}
Domain age days
0
Apex age days
0
Tls age days
1
Tls valid days
89
Requests
3
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; charset=utf-8",
    "strict-transport-security": "max-age=31536000;"
}
Separate monitor record · 2026-10-29 04:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a18360-84b0-770f-ba6e-0a2bcbd063dc
score
0
malicious
false
result_at
2026-10-29T04:30:27Z
enriched_at
2026-10-29T09:14:31Z
source_timestamps
{"urlscan_result_at":"2026-10-29 05:30:27","urlscan_enriched_at":"2026-10-29 10:14:31"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

15 / 100 · heuristic score · 0 brand references · 0 classifications

Open report
Separate monitor score · 15 / 100 · 2026-10-29T00:58:15Z

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
15
analyzed_at
2026-10-29T00:58:15Z
source_timestamp
2026-10-29 01:58:15
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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: 13 fields

Mail configuration

SPF record
v=spf1 ip4:31.31.196.17 a mx include:_spf.hosting.reg.ru ~all
SPF lookups
3

CAA records

Domain
clients-qba.site

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Trackers

Requests
5

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
No
Forward secrecy
Yes

Ports

Open ports
  • 21
  • 22
  • 25
  • 53
  • 80
  • 110
  • 143
  • 443
  • 587
  • 993
  • 995

DNS servers

Nameservers
  • IP address
    37.140.192.93
    Host
    ns1.hosting.reg.ru
  • IP address
    31.31.198.161
    Host
    ns2.hosting.reg.ru
DNS zone
clients-qba.site

Location

IP address
2a00:f940:2:2:1:1:0:256
ASN
197695
Organization
Reg.Ru-Exepto
City
Moscow
Country
RU

TLS certificate

Issuer
GlobalSign nv-sa / GlobalSign GCC R6 AlphaSSL CA 2025
Subject
*.hosting.reg.ru

DNS records

A
  • 31.31.196.17
NS
  • ns2.hosting.reg.ru
  • ns1.hosting.reg.ru
SOA
Primary nameserver
server256.hosting.reg.ru
Hostmaster
support.reg.ru
Serial
2026102802
Refresh, seconds
10800
Retry, seconds
3600
Expiry, seconds
604800
Minimum TTL, seconds
86400
TXT
  • v=spf1 ip4:31.31.196.17 a mx include:_spf.hosting.reg.ru ~all
AAAA
  • 2a00:f940:2:2:1:1:0:256

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

IP lookup

IP address
2a00:f940:2:2:1:1:0:256
IP version
6

Registration record

Registrar
Registrar of Domain Names REG.RU LLC
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
  • addPeriod https://icann.org/epp
Nameservers
  • ns1.hosting.reg.ru
  • ns2.hosting.reg.ru
Original source fields · JSON
Mail configuration
{
    "spf": "v=spf1 ip4:31.31.196.17 a mx include:_spf.hosting.reg.ru ~all",
    "spf_lookups": 3
}
Caa records
{
    "domain": "clients-qba.site"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Trackers
{
    "requests": 5
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": false,
    "forward_secrecy": true
}
Ports
{
    "open": [
        21,
        22,
        25,
        53,
        80,
        110,
        143,
        443,
        587,
        993,
        995
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "37.140.192.93",
            "host": "ns1.hosting.reg.ru"
        },
        {
            "ip": "31.31.198.161",
            "host": "ns2.hosting.reg.ru"
        }
    ],
    "zone": "clients-qba.site"
}
Location
{
    "ip": "2a00:f940:2:2:1:1:0:256",
    "asn": "197695",
    "org": "Reg.Ru-Exepto",
    "city": "Moscow",
    "country": "RU"
}
Ssl
{
    "issuer": "GlobalSign nv-sa / GlobalSign GCC R6 AlphaSSL CA 2025",
    "subject": "*.hosting.reg.ru"
}
DNS records
{
    "A": [
        "31.31.196.17"
    ],
    "NS": [
        "ns2.hosting.reg.ru",
        "ns1.hosting.reg.ru"
    ],
    "SOA": "{\"nsname\": \"server256.hosting.reg.ru\", \"hostmaster\": \"support.reg.ru\", \"serial\": 2026102802, \"refresh\": 10800, \"retry\": 3600, \"expire\": 604800, \"minttl\": 86400}",
    "TXT": [
        "v=spf1 ip4:31.31.196.17 a mx include:_spf.hosting.reg.ru ~all"
    ],
    "AAAA": [
        "2a00:f940:2:2:1:1:0:256"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Get ip
{
    "ip": "2a00:f940:2:2:1:1:0:256",
    "family": 6
}
Registration record
{
    "registrar": "Registrar of Domain Names REG.RU LLC",
    "created": "2026-10-27T13:20:48Z",
    "updated": "2026-10-27T13:20:48Z",
    "expires": "2027-10-27T13:20:48Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp",
        "addPeriod https://icann.org/epp"
    ],
    "nameservers": [
        "ns1.hosting.reg.ru",
        "ns2.hosting.reg.ru"
    ]
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing Security Risks Security threats Phishing
View full Cloudflare Radar report
Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 6 captures

URLScan · 2026-10-28 1 / 6
SourceURLScan · 2026-10-28
Recorded
StateStored capture
HTTP status200
Final URLhttps://clients-qba.site/
Position1 / 6
Open capture Source Report Wayback Download
All capture links and hashes (6)
Observed page title
Intuit
TLS Certificate
Issued by GlobalSign nv-sa / GlobalSign GCC R6 AlphaSSL CA 2025 · stored validity ends in 124 days
clients-qba.site: caution — 15/92 VirusTotal engines. PhishDestroy risk score 95/100 (critical).
Social preview card clients-qba.site: caution — 15/92 VirusTotal engines. PhishDestroy risk score 95/100 (critical). v 628545502020

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 98 report ↗
IP Reputation Russia31.31.196.17 abuse score 0/100 0 reports checked Oct 29, 2026 last reported
Registrar Registrar of Domain Na… RU(RU)
Abuse contact["abuse@reg.ru"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for clients-qba.site →
Hosting abuse contact abuse@reg.ru Reg.Ru-Exepto · AS197695
RegistrationExpires Oct 27, 2027
WHOIS statusclientTransferProhibitedaddPeriod
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 29, 2026
DOM Analysisanalyzed Oct 29, 2026score 15/100
Submitted URLhttp://clients-qba.site/
Favicon Hash
ICANN OVERSIGHT

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.

Accreditation is a contract, not a safety seal. Verify ICANN fees Read RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Russia31.31.196.17
Network ASN
AS197695
AS name
AS-REGRU "Domain names registrar REG.RU", Ltd, RU
Organization
Reg.Ru-Exepto
Observed location
RussiaMoscow, RU
Server header
nginx

Nameservers 2

  • ns1.hosting.reg.ru
  • ns2.hosting.reg.ru

SOA

  • nsname: server256.hosting.reg.ru
  • hostmaster: support.reg.ru
  • serial: 2026102802
  • refresh: 10800
  • retry: 3600
  • expire: 604800
  • minttl: 86400

Registrar abuse contact VirusTotal WHOIS

Location describes the IP network.

TLS certificate

Issuer
GlobalSign nv-sa / GlobalSign GCC R6 AlphaSSL CA 2025
Valid from
2026-02-02 12:07:59
Valid until
2027-03-06 12:07:58
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint00f0f262cc5fee43e60750021b642577660fe3261147986f15036f0439d6ade7
Certificate names · 2 SANs
  • *.hosting.reg.ru
  • hosting.reg.ru

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

viewdns.info · 31.31.196.17rapiddns.io

Latest Classified Outcome 2026-11-01 11:12:22 UTC

The site was serving its pages at the latest check.

Technical details
Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-11-01 11:12:22 UTC
RDAP registration
Observed timeline last reachable: 2026-11-01 11:12:22 UTC last content: 2026-11-01 11:12:22 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.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

15 / 92 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
BitDefender
CRDF
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
LevelBlue
MalwareURL
OpenPhish
SOCRadar
Sophos
URLQuery
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.

Captured network requests

Network requests: 3 SHA-256 hashes: 3 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-29 01:52 UTC.

Open this scan on URLScan 01a18360-84b0-770f-ba6e-0a2bcbd063dc ↗

Check for cloaking

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

Page titles differ

Our scanner could not complete this check.

Browser
Intuit
Crawler
Домен не привязан к хостингу
clients-qba.site
Stored observation history5

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

    content_served

  2. Availability monitor · Recorded state

    live_content

    content_served

  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

All retained availability observations23

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_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-11-01 12:12:22.000000
    Evidence SHA-256
    44a171d37a2af8c6421df249fed8547b613d351ae5589e51411ac30f959508e3
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 12:12:22
    Evidence reason
    alive_content
  2. 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-11-01 12:12:22.000000
    Evidence SHA-256
    44a171d37a2af8c6421df249fed8547b613d351ae5589e51411ac30f959508e3
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 12:12:22
    Evidence reason
    alive_content
  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-11-01 11:20:10.198716
    Evidence SHA-256
    b2987bb7a7acc32f1f9011b7a56a5a9a8539c203c0dded9abde43c0e22a9adeb
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 11:20:10.198716
    Evidence reason
  4. 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-11-01 03:55:45.000000
    Evidence SHA-256
    66b8c077b3128e0450fcf0d70f3997d7530104949458be03df081c8711c5bbbc
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 03:55:45
    Evidence reason
    alive_content
  5. 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-11-01 03:55:45.000000
    Evidence SHA-256
    66b8c077b3128e0450fcf0d70f3997d7530104949458be03df081c8711c5bbbc
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 03:55:45
    Evidence reason
    alive_content
  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-11-01 00:10:26.000000
    Evidence SHA-256
    19dfc2a5f686db99382238eb5fa27bd6e551055bc0494c9667dc5b82db089f08
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 00:10:26
    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-11-01 00:10:26.000000
    Evidence SHA-256
    19dfc2a5f686db99382238eb5fa27bd6e551055bc0494c9667dc5b82db089f08
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 00:10:26
    Evidence reason
    alive_content
  8. 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-31 12:10:54.000000
    Evidence SHA-256
    8a307c9e74884635c7b87549de10fddb2f49cdc98b4e73dfcdf9c905ca3106ff
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:10:54
    Evidence reason
    alive_content
  9. 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-31 12:10:54.000000
    Evidence SHA-256
    8a307c9e74884635c7b87549de10fddb2f49cdc98b4e73dfcdf9c905ca3106ff
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:10:54
    Evidence reason
    alive_content
  10. 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-31 11:20:09.112163
    Evidence SHA-256
    b5c6551e799cfe4d3cb298004536f14652a7bd27158039d9a8bde93b0611124a
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 11:20:09.112163
    Evidence reason
  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-31 03:31:52.000000
    Evidence SHA-256
    f44999abae272b3978912c92570638453eb5a5ac0f2a6488198f0a8c2adc1deb
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:31:52
    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-31 03:31:52.000000
    Evidence SHA-256
    f44999abae272b3978912c92570638453eb5a5ac0f2a6488198f0a8c2adc1deb
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:31:52
    Evidence reason
    alive_content
  13. current_http_probeunknown
    Observation source
    current_http_probe
    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-30 12:07:54.000000
    Evidence SHA-256
    db9b948492728e0236f4d3d8a2c1d387c1283ed2b8b3ff5ef4aed872f14b495f
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 12:07:54
    Evidence reason
    timeout
  14. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    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-30 12:07:54.000000
    Evidence SHA-256
    db9b948492728e0236f4d3d8a2c1d387c1283ed2b8b3ff5ef4aed872f14b495f
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 12:07:54
    Evidence reason
    timeout
  15. 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-30 05:03:05.462458
    Evidence SHA-256
    bbc8a7612fad967fe6394ef6e3533c42adb354b0403e4f596ca1b553348f1852
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 05:03:05.462458
    Evidence reason
  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-30 00:07:33.000000
    Evidence SHA-256
    bf381a00d62f82a841c7406b73e86219ef8b7a78323d18a5020987ac350992c9
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:07:33
    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-30 00:07:33.000000
    Evidence SHA-256
    bf381a00d62f82a841c7406b73e86219ef8b7a78323d18a5020987ac350992c9
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:07:33
    Evidence reason
    alive_content
  18. 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-29 12:07:38.000000
    Evidence SHA-256
    5d9ccd0d32511c6af0aab20798e88efb60251476e9a4d6f8ced0f6fcf5013d7d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:07:38
    Evidence reason
    alive_content
  19. 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-29 12:07:38.000000
    Evidence SHA-256
    5d9ccd0d32511c6af0aab20798e88efb60251476e9a4d6f8ced0f6fcf5013d7d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:07:38
    Evidence reason
    alive_content
  20. 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-29 05:03:05.313035
    Evidence SHA-256
    e8d7330e223cce20a4540e7f3ccd4cc0f3b8c1f41fa08898b82c337408eae933
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-29 05:03:05.313035
    Evidence reason
  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-29 03:00:31.000000
    Evidence SHA-256
    3aa5bfc6d7a19c7d69da9162b0be7e56f739cd7ddcb3c3dbd4b1bac47115abe1
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 03:00:31
    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-29 03:00:31.000000
    Evidence SHA-256
    3aa5bfc6d7a19c7d69da9162b0be7e56f739cd7ddcb3c3dbd4b1bac47115abe1
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 03:00:31
    Evidence reason
    alive_content
  23. 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-29 01:44:17.800741
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

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

Recorded events: 9. 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
    clients-qba.site detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Cloudflare Radar: Malicious · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 7 of 7
  • 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.
  • VirusTotal
    Detections recorded on VirusTotal: 15/92
  • Cloudflare Radar: Malicious
    Cloudflare Radar classified this domain as phishing, Security Risks, Security threats
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
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

3 entries
  1. Added to PhishDestroy

    clients-qba.site

    View source
  2. VirusTotal

    15/92 engine detections

    View source
  3. URLScan

    Malicious · engine verdict · score 98

    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

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 15 det. ChainPatrol URLQuery SSL Labs Certificate hostname mismatch CF Radar Malicious WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
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?

3 evidence signal groups linked 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.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

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

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.

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

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.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website

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 clients-qba.site)
  • 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.

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/clients-qba.site"
  title="PhishDestroy threat report for clients-qba.site"
  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>