VirusTotal
5 / 92 engine detections
Open reportdasco.kz is a Facebook impersonation page detected by PhishDestroy on 2026-10-10. Risk: critical (88/100). Status: Last known active. Hosting: Hoster-ALM LLP "Kompaniya Hoster.KZ", KZ. PhishDestroy sent 1 abuse report. VirusTotal: 5/92 engines flag it. Do not enter credentials or connect a wallet.
“Dasco Group”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@hoster.kz.
The latest stored availability evidence still shows the domain reachable; 11 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
5 / 92 engine detections
Open report2 det.
Open report37 community references
Open reportprovider verdict: clean
Open reportNo threat flag
Open reportNo malicious flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
dasco.kz is an impersonation phishing page that presents itself under the title "Dasco Group", borrowing that company's identity to win the trust of its customers, partners and anyone searching for it. PhishDestroy first flagged the domain on 2026-10-10. When last checked on 2026-10-19, the site was still online and its content was being served behind a protection layer, so the threat remains active.
Brand-impersonation sites copy the name and look of a real business so that visitors believe they are on the genuine company's portal. Here the "Dasco Group" title does that job. A visitor arriving from a search result, an email or a message is then asked to log in, submit personal or business details, or make a payment. Anything entered goes straight to the operators, who can reuse stolen credentials, run follow-up fraud in the company's name, or keep payments that never reach the real business.
Five of 92 engines on VirusTotal flag the domain as of 2026-10-16: alphaMountain.ai, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar and URLQuery. That is a modest count, but these vendors work independently of each other and of PhishDestroy, which lists the domain on its own blocklist. The domain also appears in 37 AlienVault OTX pulses, which shows that other researchers are tracking it as a threat indicator.
The site resolves to 93.115.14.8 on the network of Hoster-ALM LLP "Kompaniya Hoster.KZ" in Kazakhstan. Local hosting fits a .kz domain and helps it pass as a domestic company site. It uses a free Let's Encrypt certificate, so the padlock in the browser only means the connection is encrypted. It does not prove the site belongs to Dasco Group.
If you entered a username and password on this page, change that password at once on the real service and on any other account where you reused it, and turn on two-factor authentication. If you sent a payment or card details, contact your bank to dispute the charge and block the card. Verify any invoice or request that came through this site using contact details you already trust. Report the incident to the genuine Dasco Group so it can warn its clients. Defenders should block dasco.kz at DNS, proxy and email gateways, search logs for past visits or form submissions, and treat any credentials tied to those sessions as compromised.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a127d1-136b-7420-92fc-2e8612db2a57 |
|---|---|
| Final url | https://dasco.kz/ |
| Status | 200 |
| Redirected | https-only |
| Redirects | [
{
"to": "https://dasco.kz/",
"from": "http://dasco.kz/",
"status": 307
}
] |
| Ip | 93.115.14.8 |
| Ptr | acloud-2.hoster.kz |
| Contacted domains | [
"fonts.gstatic.com",
"fonts.googleapis.com"
] |
| Contacted IP addresses | [
"142.251.14.94",
"142.250.154.95",
"2a00:1450:4001:c0f::5f",
"93.115.14.8"
] |
| Asns | [
"15169",
"202958"
] |
| Countries | [
"US",
"DE",
"KZ"
] |
| Linked domains | [
"survey.dasco.kz",
"www.youtube.com",
"www.instagram.com",
"kz.linkedin.com",
"t.me",
"www.tiktok.com",
"www.facebook.com"
] |
| Social | [
"https://www.youtube.com/@DASCO_GROUP",
"https://www.instagram.com/dasco.kz",
"https://t.me/dascolight",
"https://www.tiktok.com/@dasco.group",
"https://www.facebook.com/dascoconsulting"
] |
| Document hash | 6eb3c705a6edbb96cc455b1e59bed5d8180a7888b1aaf308ff036d5e3d3c2310 |
| Script hashes | [
"d949f1c3687aedadcedac85261865f29b17cd273997e7f6b2bfc53b2f9d4c4dd",
"35f4f974f4b2bcd44da73963347f8952e341f83909e4498227d4e26b98f66f0d",
"086c56ce48d2e3c5884a54e3c1aa8c65d2c595f0cd634716eda2b91066600bda",
"99aaf7045a5c801db73f65f4108f8ef0893178c0fb726b70d986641845588ec1",
"fc774906082b59dedcfc55b8ef127783b6d056578ff4586a8ebbdb81bbe286f1",
"5083905862c2b7aa8a84c4f2313d359d2288fb25fbe1ff577fa7325eff2ed2d9",
"1110d342a7031617a862f62bca8765ab7d2251db6b9e8541e7aa599d6c93cf69",
"84e6a0541e61f345695c6b5722dad0f4ddfd06ba097699b50ba1bcfe7b2608ce",
"6cb66f61897e852725119ad7b3cfcb032166b540a739658d6233efb76791b7a5",
"82212924a854ca5275b5102be80b5d30417c81a33f8ca2ce034fab05a4fd6009"
] |
| Globals | [
"React",
"ReactDOM",
"ReactJSXRuntime",
"wp",
"Mousetrap",
"moment",
"__wpStyleRuntime",
"jQuery",
"_tpt",
"SR7",
"$us",
"frontend_global_data",
"pow",
"_document",
"_navigator",
"_window",
"$ush",
"EvEmitter",
"imagesLoaded",
"USAnimate",
"usGmapLoaded",
"USHeader",
"pum_vars",
"pum_sub_vars",
"pum_popups",
"PUM",
"PUM_Accessibility",
"PUM_Analytics",
"pm_cookie",
"pm_cookie_json",
"pm_remove_cookie",
"pum_debug_mode",
"ajaxurl",
"pum",
"FormSerializer",
"MagicGrid",
"_smart_filter_object",
"Popper",
"bootstrap",
"Swiper"
] |
| Cookies | [
"pll_language"
] |
| Storage keys | [
"__wpDataTestLocalStorage",
"wpEmojiSettingsSupports"
] |
| Tls | {
"san": [
"*.dasco.kz",
"dasco.kz"
],
"cipher": "AES_256_GCM",
"issuer": "YR1",
"subject": "dasco.kz",
"protocol": "TLS 1.3",
"valid_to": "2026-12-15T16:59:54Z",
"valid_from": "2026-09-16T16:59:55Z"
} |
| Domain age days | 2907 |
| Apex age days | 2907 |
| Tls age days | 24 |
| Tls valid days | 89 |
| Requests | 135 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": -26,
"malicious": false
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "nginx",
"content-type": "text/html; charset=UTF-8",
"x-powered-by": "PleskLin"
} |
Observed: · Retrieved:
| Uuid | 8478ff63-71d9-45e0-ac4e-48ff895e2679 |
|---|---|
| Final url | https://dasco.kz/ |
| Status | 200 |
| History | [
{
"url": "https://dasco.kz/",
"status": 200
}
] |
| DOM structure hash | eba596a3bb34188f974bd9bbf3b32f4683e619adfa486efc1d6a0bd93e48d92b |
| Document hash | 9502f87f6e1a49701f8189a1270a3039a9cb4ba063e7a46bfced849e284f997e |
| Domain risks | [
"Business",
"Business & Economy"
] |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "dasco.kz",
"type": "A",
"value": "93.115.14.8"
}
] |
| Dnssec valid | false |
| Ip | 93.115.14.8 |
| Registration record | {
"created": "2018-03-16T11:11:05Z",
"updated": "2018-10-22T18:16:02Z",
"nameservers": [
"ns1.hoster.kz",
"ns2.hoster.kz",
"ns3.hoster.kz"
]
} |
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 55,
"malicious": 3,
"suspicious": 2,
"undetected": 32
} |
|---|---|
| Vendor labels | {
"SOCRadar": "phishing",
"URLQuery": "suspicious",
"Gridinsoft": "malicious",
"alphaMountain.ai": "malicious",
"Forcepoint ThreatSeeker": "suspicious"
} |
| Reputation | 0 |
| Categories | {
"BitDefender": "porn",
"alphaMountain.ai": "Business/Economy, Malicious (alphaMountain.ai)",
"Forcepoint ThreatSeeker": "compromised websites"
} |
| Popularity | {
"Alexa": 467663,
"Statvoo": 172758
} |
| First seen | 2023-10-03T09:50:26Z |
| DNS records | [
{
"ttl": 3600,
"type": "NS",
"value": "ns1.hoster.kz"
},
{
"ttl": 3600,
"type": "TXT",
"value": "google-site-verification=WM2_dnkJ51hmuDni-GokuZP4VBfhHBjhUw39NNbJmUM"
},
{
"ttl": 3600,
"type": "MX",
"value": "alt1.aspmx.l.google.com",
"priority": 10
},
{
"ttl": 3600,
"type": "MX",
"value": "alt4.aspmx.l.google.com",
"priority": 15
},
{
"ttl": 3600,
"type": "MX",
"value": "alt2.aspmx.l.google.com",
"priority": 10
},
{
"ttl": 3600,
"type": "NS",
"value": "ns3.hoster.kz"
},
{
"ttl": 3600,
"type": "A",
"value": "93.115.14.8"
},
{
"ttl": 3600,
"type": "TXT",
"value": "v=spf1 include:_spf.google.com ~all."
},
{
"ttl": 3600,
"type": "MX",
"value": "alt3.aspmx.l.google.com",
"priority": 15
},
{
"ttl": 3600,
"type": "NS",
"value": "ns2.hoster.kz"
},
{
"ttl": 3600,
"type": "TXT",
"value": "MS=ms62890202"
},
{
"ttl": 3600,
"type": "MX",
"value": "aspmx.l.google.com",
"priority": 5
},
{
"ttl": 3600,
"type": "TXT",
"value": "update_dns_zone"
},
{
"ttl": 3600,
"type": "TXT",
"value": "MS=FCB4B10B1570A011F50B206B47E942C7506A4B1C"
},
{
"ttl": 3600,
"type": "SOA",
"rname": "support.hoster.kz",
"value": "ns3.hoster.kz"
}
] |
| Dns at | 2026-10-20T02:00:37Z |
| Jarm | 29d29d00029d29d00042d42d0000002059a3b916699461c5923779b77cf06b |
| Certificate | {
"san": [
"*.dasco.kz",
"dasco.kz"
],
"issuer": "Let's Encrypt / YR1",
"serial": "5582eebeb48cb65d69ed8506e7be511d8d9",
"sha256": "6b9b543faa4ad65da34e29c1b41b52e76346f0928c196d7b4ccc918b0c53d78e",
"subject": "dasco.kz",
"valid_to": "2026-12-15T16:59:54Z",
"valid_from": "2026-09-16T16:59:55Z"
} |
| Registration record | {
"status": [
"clientDeleteProhibited"
],
"nameservers": [
"ns1.hoster.kz",
"ns2.hoster.kz",
"ns3.hoster.kz"
]
} |
No. PhishDestroy classifies dasco.kz as a Facebook impersonation page (risk: critical, 88/100); it was first detected on 2026-10-10. VirusTotal: 5/92 engines flag it. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on dasco.kz. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
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.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/dascolightStored page referenceIoC extraction recorded 2026-10-11 04:01:16 UTC
ns1.hoster.kzns2.hoster.kzns3.hoster.kzaspmx.l.google.compriority 5alt2.aspmx.l.google.compriority 10alt1.aspmx.l.google.compriority 10alt4.aspmx.l.google.compriority 15alt3.aspmx.l.google.compriority 15Location describes the IP network.
6b9b543faa4ad65da34e29c1b41b52e76346f0928c196d7b4ccc918b0c53d78e*.dasco.kzdasco.kzSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
new.dasco.kzDomain recordsupport.dasco.kzDomain recordsurvey.dasco.kzDomain recordwww.dasco.kzDomain recordwww.new.dasco.kzDomain recordwww.survey.dasco.kzDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of dasco.kz · checked Oct 12, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→live_content
content_served
protected→live_content
content_served
Unknown→protected
http_access_restricted · access_restriction
Unknown→protected
http_access_restricted · access_restriction
Unknown→protected
http_access_restricted · access_restriction
protected→live_content
content_served
Unknown→protected
http_access_restricted · access_restriction
live_content→protected
http_access_restricted · access_restriction
Unknown→live_content
content_served
Unknown→protected
http_access_restricted · access_restriction
live_content→protected
http_access_restricted · access_restriction
Unknown→live_content
content_served
protected→live_content
content_served
Unknown→protected
http_access_restricted · access_restriction
protected→live_content
content_served
Unknown→protected
http_access_restricted · access_restriction
Unknown→live_content
content_served
Unknown→live_content
content_served
Reachable
No threat flag
View source5/92 engine detections
View source37 community references
View sourcePD-20261010-3C6DA7
dasco.kz
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
dasco.kz
PD-20261010-3C6DA7 Recipient: abuse@hoster.kz If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
dasco.kz)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
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.