Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 2. Exercise extreme caution — do not enter credentials or personal information.
Domain security and threat intelligence
musor.blog favicon

musor.blog

In short

musor.blog is a Cs2 impersonation page detected by PhishDestroy on 2026-10-25.

“MUSOR DROP на musor.blog — разбор кейсов CS2 и код INVFMFEP7”

Review the evidence
Registrar
Dynadot
Resolved IP
188.114.97.3
Registered
Sep 4, 2026
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed Website checks · HTTP 200
Risk signals
VirusTotal detections: 2/92 Automated brand label: Cs2 Scam type: Impersonation
VirusTotal
2 / 92
engine detections ·
OTX
4
community references
Cloudflare Radar
clean
source verdict
Page captures
4
open gallery
Domain age
51 days
Reports sent
—
No sent record
OTX: 4 refs Oct 25, 2026 CDN
X Telegram API

Analysis

Domain summary

musor.blog is a Cs2 impersonation page detected by PhishDestroy on 2026-10-25. Risk: critical (81/100). Registrar: Dynadot. Status: Last known active. Hosting: Cloudflare, Inc. VirusTotal: 2/92 engines flag it. Do not enter credentials or connect a wallet.

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

PhishDestroy threat report

Overview

PhishDestroy’s intake AI assigned a strong phishing confidence (90%) and flagged musor.blog because the site describes a CS2 “MUSOR DROP” case‑opening and upgrade gambling service, offers a promotional code and mentions Steam login and withdrawal. The domain was first seen by PhishDestroy on 2026-10-25 and returned an HTTP 200 response at that time. The assessment relies on page metadata and AI‑generated reasoning, not on observed transactions.

How the scam works

Sites that market CS2 case‑opening or upgrade services typically lure users with high‑return‑to‑player claims, require a Steam login, and ask for deposits or personal credentials to “withdraw” virtual items. Because the services are unregulated, they can harvest Steam credentials, charge fees, or disappear with any funds or items the victim provides. This pattern is treated as a fraudulent gambling or phishing scheme.

Evidence

VirusTotal recorded two malicious detections out of 92 engines on 2026-10-25, specifically from Forcepoint ThreatSeeker and SOCRadar, labeling the domain as phishing. Google Safe Browsing reported no flag on the same date. OTX listed four pulses referencing the domain. PhishDestroy’s internal blocklist marks the domain as malicious, while external blocklists (including Spamhaus) showed no entry as of 2026-10-25. URLScan’s engine flagged the site as malicious with a score of 100, though its overall verdict was non‑malicious; the scan captured the page title and metadata on 2026-10-25.

Infrastructure

The domain was registered on 2026-09-04 with Dynadot LLC, giving it a 51‑day age at first sight. The recorded DNS at the time listed Cloudflare A records 172.67.168.3 and 104.21.74.93 and AAAA records in the 2606:4700:: range. The TLS certificate, issued by Google Trust Services, is valid until 2026-12-20 and covers musor.blog and its sub‑domains. No DNSSEC signatures were present, and the domain was not listed on Spamhaus or other external blocklists.

What to do

Users should avoid entering Steam credentials or any payment information on musor.blog and, if they have already done so, change their Steam password and enable two‑factor authentication. Organizations should block musor.blog at the DNS or proxy level, monitor outbound connections to its recorded IPs, and review logs for any Steam‑related authentication attempts.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportStored capture screenshotCloudflare Radar screenshot (2026-10-25T15:25:26Z)URLScan screenshot (2026-10-25T15:05:36Z)URLScan capture reportVirusTotal reportGoogle Safe Browsing statusArchived copyReport phishing to GoogleSite owner? Request a review
Source evidenceVirusTotal 2 / 92 · OTX 4 references 8 sources

VirusTotal

2 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
53
Malicious
2
Suspicious
0
Undetected
37

Vendor labels

SOCRadar
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Registrar

Dynadot LLC

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3034::6815:4a5d
  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    henrik.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    TXT
    Value
    yandex-verification: 991fcc836a0ca8f9
  • TTL, seconds
    300
    Type
    A
    Value
    172.67.168.3
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3037::ac43:a803
  • TTL, seconds
    21600
    Type
    NS
    Value
    ruth.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    104.21.74.93
  • TTL, seconds
    21600
    Type
    NS
    Value
    henrik.ns.cloudflare.com

DNS records observed

JARM fingerprint

27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c

Certificate

Subject alternative names
  • musor.blog
  • musor26.musor.blog
  • *.musor26.musor.blog
Issuer
Google Trust Services / WE1
Serial
7b13729497fe7abb0eb4c7110101925f
SHA-256
53ed1da7914d6cd7802066acff982e99690111576c8a9d49d4201753448348a2
Subject
musor.blog
Valid until
Valid from

Registration record

Registrar
Dynadot LLC
Registrar IANA ID
472
Registrar URL
http://www.dynadot.com
Registered
Updated
Expires
Status
  • clientTransferProhibited
  • serverTransferProhibited
Nameservers
  • henrik.ns.cloudflare.com
  • ruth.ns.cloudflare.com
DNSSEC
unsigned

Registry data (RDAP)

Status
  • transfer prohibited
Registry events
Expiration
Last changed
Registration
Registrar expiration
Last RDAP database update
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 53,
    "malicious": 2,
    "suspicious": 0,
    "undetected": 37
}
Vendor labels
{
    "SOCRadar": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Registrar
Dynadot LLC
Created
2026-09-04T03:38:58Z
Expires
2027-09-04T03:38:58Z
Updated
2026-09-09T03:42:55Z
First seen
2026-09-04T04:48:58Z
DNS records
[
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3034::6815:4a5d"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "henrik.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "TXT",
        "value": "yandex-verification: 991fcc836a0ca8f9"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.168.3"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3037::ac43:a803"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ruth.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.74.93"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "henrik.ns.cloudflare.com"
    }
]
Dns at
2026-10-25T15:27:48Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "musor.blog",
        "musor26.musor.blog",
        "*.musor26.musor.blog"
    ],
    "issuer": "Google Trust Services / WE1",
    "serial": "7b13729497fe7abb0eb4c7110101925f",
    "sha256": "53ed1da7914d6cd7802066acff982e99690111576c8a9d49d4201753448348a2",
    "subject": "musor.blog",
    "valid_to": "2026-12-20T01:48:01Z",
    "valid_from": "2026-09-21T00:48:04Z"
}
Registration record
{
    "registrar": "Dynadot LLC",
    "registrar_iana_id": "472",
    "registrar_url": "http://www.dynadot.com",
    "created": "2026-09-04T03:38:58Z",
    "updated": "2026-09-09T03:42:55Z",
    "expires": "2027-09-04T03:38:58Z",
    "status": [
        "clientTransferProhibited",
        "serverTransferProhibited"
    ],
    "nameservers": [
        "henrik.ns.cloudflare.com",
        "ruth.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "transfer prohibited"
    ],
    "events": {
        "expiration": "2027-09-04T03:38:58Z",
        "last changed": "2026-09-04T03:42:52Z",
        "registration": "2026-09-04T03:38:58Z",
        "registrar expiration": "2027-09-04T03:38:58Z",
        "last update of RDAP database": "2026-10-23T11:11:17Z"
    }
}
Separate source record · 2 malicious + 0 suspicious / 92 · 2026-10-25 15:22:29 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-25T15:22:29Z
fetched_at
2026-10-25T16:34:25Z
stats
{"timeout":0,"harmless":53,"malicious":2,"suspicious":0,"undetected":37}

URLScan

Malicious · engine verdict · score 100

Open report
URLScanOriginal source recordObserved: 22 fields

Observed: · Retrieved:

Report ID

01a1738a-a8f0-7278-be6b-b0b33b6d6666

Final URL

https://musor.blog/

HTTP response

200

IP address

188.114.96.3

Contacted domains

  • musorprod.web.gaypictures.online
  • mc.yandex.com
  • community.akamai.steamstatic.com
  • musor.bar
  • musor.best
  • fonts.gstatic.com
  • mc.yandex.ru
  • fonts.googleapis.com
  • musor2.win

Contacted IP addresses

  • 95.129.232.111
  • 23.32.239.51
  • 142.251.127.94
  • 2a02:6b8::1:119
  • 95.129.237.63
  • 186.2.163.224
  • 2a00:1450:4001:c0f::5f
  • 188.114.96.3

Autonomous systems (ASN)

  • 57724
  • 20940
  • 15169
  • 13238
  • 59692
  • 13335

Server countries

  • RU
  • DE
  • US
  • NL

Linked domains

  • musor.click

Document hash

d401bb094378b1793982a16a21f6ba0a0eee76d07e58b9cf142791143c2d1b8c

Script hashes

  • daf818f12f80d05284a1e7ad3488249e07f0b3594f7afcaa701a9a35daa34dbd

JavaScript globals

  • ym
  • Ya
  • yaCounter112281526
  • dataLayer
  • REF
  • SKINS
  • track
  • online
  • CATALOG
  • catalog

Cookies

  • bh
  • _ym_uid
  • _ym_d
  • sync_cookie_csrf
  • _ym_isad
  • yabs-sid
  • i
  • yandexuid
  • yuidss
  • ymex
  • sync_cookie_csrf_secondary
  • sync_cookie_ok_secondary

Browser storage keys

  • _ymBRC
  • _ym_synced
  • _ym112281526_lsid
  • _ym112281526:0_reqNum
  • _ym_uid
  • _ym_retryReqs
  • _ym_jn

TLS session and certificate

Subject alternative names
  • musor.blog
  • musor26.musor.blog
  • *.musor26.musor.blog
Cipher
AES_128_GCM
Issuer
WE1
Subject
musor.blog
Protocol
QUIC
Valid until
Valid from

Domain age, days

51

Registered domain age, days

51

Certificate age, days

34

Certificate validity, days

90

Page requests

73

Provider verdicts

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

HTTP headers

Server
cloudflare
Content-type
text/html
Original source fields · JSON
Uuid
01a1738a-a8f0-7278-be6b-b0b33b6d6666
Final url
https://musor.blog/
Status
200
Ip
188.114.96.3
Contacted domains
[
    "musorprod.web.gaypictures.online",
    "mc.yandex.com",
    "community.akamai.steamstatic.com",
    "musor.bar",
    "musor.best",
    "fonts.gstatic.com",
    "mc.yandex.ru",
    "fonts.googleapis.com",
    "musor2.win"
]
Contacted IP addresses
[
    "95.129.232.111",
    "23.32.239.51",
    "142.251.127.94",
    "2a02:6b8::1:119",
    "95.129.237.63",
    "186.2.163.224",
    "2a00:1450:4001:c0f::5f",
    "188.114.96.3"
]
Asns
[
    "57724",
    "20940",
    "15169",
    "13238",
    "59692",
    "13335"
]
Countries
[
    "RU",
    "DE",
    "US",
    "NL"
]
Linked domains
[
    "musor.click"
]
Document hash
d401bb094378b1793982a16a21f6ba0a0eee76d07e58b9cf142791143c2d1b8c
Script hashes
[
    "daf818f12f80d05284a1e7ad3488249e07f0b3594f7afcaa701a9a35daa34dbd"
]
Globals
[
    "ym",
    "Ya",
    "yaCounter112281526",
    "dataLayer",
    "REF",
    "SKINS",
    "track",
    "online",
    "CATALOG",
    "catalog"
]
Cookies
[
    "bh",
    "_ym_uid",
    "_ym_d",
    "sync_cookie_csrf",
    "_ym_isad",
    "yabs-sid",
    "i",
    "yandexuid",
    "yuidss",
    "ymex",
    "sync_cookie_csrf_secondary",
    "sync_cookie_ok_secondary"
]
Storage keys
[
    "_ymBRC",
    "_ym_synced",
    "_ym112281526_lsid",
    "_ym112281526:0_reqNum",
    "_ym_uid",
    "_ym_retryReqs",
    "_ym_jn"
]
Tls
{
    "san": [
        "musor.blog",
        "musor26.musor.blog",
        "*.musor26.musor.blog"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE1",
    "subject": "musor.blog",
    "protocol": "QUIC",
    "valid_to": "2026-12-20T01:48:01Z",
    "valid_from": "2026-09-21T00:48:04Z"
}
Domain age days
51
Apex age days
51
Tls age days
34
Tls valid days
90
Requests
73
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 100,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html"
}
Separate monitor record · date not recorded

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

record_source
domain_monitor.urlscan
uuid
01a1738a-a8f0-7278-be6b-b0b33b6d6666
score
null
malicious
null
result_at
null
enriched_at
null
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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

c3b0eebd-df75-4a78-a44a-a0763d2bd9cc

Final URL

https://musor.blog/

HTTP response

200

Navigation history

  • URL
    https://musor.blog/
    Status
    200

DOM structure hash

0e1a14ad173216847ffd35809c71c10514fcd6220ce6a0f579bdf45fa66b02e9

Document hash

3e614dbe7ff9fa2d46340f756b30f9107a1ab7f08260c296b689e1efe24c4747

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    musor.blog
    Type
    A
    Value
    172.67.168.3
  • Name
    musor.blog
    Type
    A
    Value
    104.21.74.93
  • Name
    musor.blog
    Type
    AAAA
    Value
    2606:4700:3037::ac43:a803
  • Name
    musor.blog
    Type
    AAAA
    Value
    2606:4700:3034::6815:4a5d

DNSSEC valid

No

IP address

172.67.168.3

Registration record

Registrar
Dynadot LLC
Registered
Updated
Expires
Nameservers
  • henrik.ns.cloudflare.com
  • ruth.ns.cloudflare.com
Original source fields · JSON
Uuid
c3b0eebd-df75-4a78-a44a-a0763d2bd9cc
Final url
https://musor.blog/
Status
200
History
[
    {
        "url": "https://musor.blog/",
        "status": 200
    }
]
DOM structure hash
0e1a14ad173216847ffd35809c71c10514fcd6220ce6a0f579bdf45fa66b02e9
Document hash
3e614dbe7ff9fa2d46340f756b30f9107a1ab7f08260c296b689e1efe24c4747
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "musor.blog",
        "type": "A",
        "value": "172.67.168.3"
    },
    {
        "name": "musor.blog",
        "type": "A",
        "value": "104.21.74.93"
    },
    {
        "name": "musor.blog",
        "type": "AAAA",
        "value": "2606:4700:3037::ac43:a803"
    },
    {
        "name": "musor.blog",
        "type": "AAAA",
        "value": "2606:4700:3034::6815:4a5d"
    }
]
Dnssec valid
false
Ip
172.67.168.3
Registration record
{
    "registrar": "Dynadot LLC",
    "created": "2026-09-04T03:38:58Z",
    "updated": "2026-09-09T03:42:55Z",
    "expires": "2027-09-04T03:38:58Z",
    "nameservers": [
        "henrik.ns.cloudflare.com",
        "ruth.ns.cloudflare.com"
    ]
}

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

81 / 100 · heuristic score · 2 brand references · 1 classifications

Open report
Separate monitor score · 10 / 100 · 2026-10-25T15:20:12Z

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
10
analyzed_at
2026-10-25T15:20:12Z
source_timestamp
2026-10-25 16:20:12
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
musor.blog — Counter‑Strike 2 case gambling site
ai_description
PhishDestroy flagged musor.blog on 2026-10-25 as a malicious site promoting a Counter‑Strike 2 case‑opening gambling service.
ai_generated_at
2026-10-25T16:36:25Z
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: 28 fields

Mail configuration

SPF lookups
0

CAA records

Domain
musor.blog

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
6613

Crawler rules

User agents
  • *
  • Yandex
Present
Yes
Sitemap URLs
  • https://musor.blog/sitemap.xml

Sitemap

Present
Yes
URL count
16

Page title and metadata

Open Graph URL
https://musor.blog/
Page title
MUSOR DROP на musor.blog — разбор кейсов CS2 и код INVFMFEP7
Open Graph type
website
Open Graph title
MUSOR DROP на musor.blog — разбор кейсов и код INVFMFEP7
Theme color
#100F12
Description
Гид musor.blog: лента дропов, кейсы CS2, апгрейд, контракт и куда вставлять INVFMFEP7. RTP 98%. 18+.
Canonical URL
https://musor.blog/
Open Graph description
Как устроены кейсы, усиление и контракт. Код INVFMFEP7 — после Steam, не в ленте.

Trackers

Requests
81
Observed services
  • Name
    Yandex
    Company
    Yandex
    Country
    RU
    Category
    Advertising
    Requests
    2
  • Name
    Google Fonts
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    Google Static
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    4
  • Name
    Yandex Metrika
    Company
    Yandex
    Country
    RU
    Category
    Site Analytics
    Requests
    2

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
2
TLS
24
Waiting
74
Connection
12
Download
1
Response time, ms
113

TLS connection

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

Ports

Open ports
  • 80
  • 443
  • 8080

Carbon estimate

Bytes
15543
CO₂, grams
0.0006
Cleaner than, %
62

DNS servers

Nameservers
  • IP address
    108.162.192.143
    Host
    ruth.ns.cloudflare.com
  • IP address
    172.64.35.105
    Host
    henrik.ns.cloudflare.com
DNS zone
musor.blog

Cookies

Cookies
  • Name
    bh
    Secure
    Yes
    SameSite
    None
  • Name
    _ym_uid
    Secure
    Yes
    SameSite
    None
  • Name
    _ym_d
    Secure
    Yes
    SameSite
    None
  • Name
    sync_cookie_csrf
    Secure
    Yes
    SameSite
    None
  • Name
    _ym_isad
    Secure
    Yes
    SameSite
    None
  • Name
    sync_cookie_csrf
    Secure
    Yes
    SameSite
    None
  • Name
    _yasc
    Secure
    Yes
    SameSite
    None
  • Name
    yabs-sid
    Secure
    Yes
    Session cookie
    Yes
    SameSite
    None
  • Name
    i
    Secure
    Yes
    HTTP-only
    Yes
    SameSite
    None
  • Name
    yandexuid
    Secure
    Yes
    SameSite
    None
  • Name
    yuidss
    Secure
    Yes
    SameSite
    None
  • Name
    ymex
    Secure
    Yes
    SameSite
    None
  • Name
    receive-cookie-deprecation
    Secure
    Yes
    HTTP-only
    Yes
    SameSite
    None
  • Name
    bh
    Secure
    Yes
    SameSite
    None

Location

IP address
2a06:98c1:3121::3
ASN
13335
Organization
CloudFLARENET-EU
City
London
Country
GB

TLS certificate

Issuer
Google Trust Services / WE1
Subject
musor.blog

DNS records

A
  • 188.114.96.3
  • 188.114.97.3
NS
  • henrik.ns.cloudflare.com
  • ruth.ns.cloudflare.com
SOA
Primary nameserver
henrik.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2415441006
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800
TXT
  • yandex-verification: 991fcc836a0ca8f9
AAAA
  • 2a06:98c1:3121::3
  • 2a06:98c1:3120::3

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

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
2a06:98c1:3120::3
IP version
6

Redirects

Redirect chain
  • https://musor.blog

Subdomains

Count
23
Subdomains
  • apgreid.musor.blog
  • bonusy.musor.blog
  • chestnost.musor.blog
  • faq.musor.blog
  • gid.musor.blog
  • keisy-cs2.musor.blog
  • kontrakty.musor.blog
  • musor14.musor.blog
  • musor19.musor.blog
  • musor26.musor.blog
  • musor32.musor.blog
  • musor39.musor.blog
  • musor4.musor.blog
  • musor6.musor.blog
  • musor9.musor.blog
  • mystery-box.musor.blog
  • novosti.musor.blog
  • nozhi-cs2.musor.blog
  • obzor.musor.blog
  • promocod.musor.blog
  • shansy.musor.blog
  • vhod-steam.musor.blog
  • vyvod-skina.musor.blog

Page links

External link addresses
  • https://musor.click/HBlQV3uh
External links
1
Internal links
4

Registration record

Registrar
Dynadot LLC
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
  • serverTransferProhibited https://icann.org/epp
Nameservers
  • henrik.ns.cloudflare.com
  • ruth.ns.cloudflare.com

HTTP headers

Response headers
Server
cloudflare
Content-type
text/html
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "musor.blog"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-10-25T14:52:15Z",
    "first": "2026-10-25T14:52:15Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 6613
}
Crawler rules
{
    "agents": [
        "*",
        "Yandex"
    ],
    "present": true,
    "sitemaps": [
        "https://musor.blog/sitemap.xml"
    ]
}
Sitemap
{
    "present": true,
    "url_count": 16
}
Page title and metadata
{
    "ogUrl": "https://musor.blog/",
    "title": "MUSOR DROP на musor.blog — разбор кейсов CS2 и код INVFMFEP7",
    "ogType": "website",
    "ogTitle": "MUSOR DROP на musor.blog — разбор кейсов и код INVFMFEP7",
    "themeColor": "#100F12",
    "description": "Гид musor.blog: лента дропов, кейсы CS2, апгрейд, контракт и куда вставлять INVFMFEP7. RTP 98%. 18+.",
    "canonicalUrl": "https://musor.blog/",
    "ogDescription": "Как устроены кейсы, усиление и контракт. Код INVFMFEP7 — после Steam, не в ленте."
}
Trackers
{
    "requests": 81,
    "trackers": [
        {
            "name": "Yandex",
            "company": "Yandex",
            "country": "RU",
            "category": "Advertising",
            "requests": 2
        },
        {
            "name": "Google Fonts",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        },
        {
            "name": "Google Static",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 4
        },
        {
            "name": "Yandex Metrika",
            "company": "Yandex",
            "country": "RU",
            "category": "Site Analytics",
            "requests": 2
        }
    ]
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 2,
        "tls": 24,
        "wait": 74,
        "connect": 12,
        "download": 1
    },
    "response_ms": 113
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1",
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        8080
    ]
}
Carbon
{
    "bytes": 15543,
    "co2_grams": 0.0006,
    "cleaner_than": 62
}
Dns server
{
    "ns": [
        {
            "ip": "108.162.192.143",
            "host": "ruth.ns.cloudflare.com"
        },
        {
            "ip": "172.64.35.105",
            "host": "henrik.ns.cloudflare.com"
        }
    ],
    "zone": "musor.blog"
}
Cookies
{
    "cookies": [
        {
            "name": "bh",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_ym_uid",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_ym_d",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "sync_cookie_csrf",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_ym_isad",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "sync_cookie_csrf",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_yasc",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "yabs-sid",
            "secure": true,
            "session": true,
            "same_site": "None"
        },
        {
            "name": "i",
            "secure": true,
            "http_only": true,
            "same_site": "None"
        },
        {
            "name": "yandexuid",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "yuidss",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "ymex",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "receive-cookie-deprecation",
            "secure": true,
            "http_only": true,
            "same_site": "None"
        },
        {
            "name": "bh",
            "secure": true,
            "same_site": "None"
        }
    ]
}
Location
{
    "ip": "2a06:98c1:3121::3",
    "asn": "13335",
    "org": "CloudFLARENET-EU",
    "city": "London",
    "country": "GB"
}
Ssl
{
    "issuer": "Google Trust Services / WE1",
    "subject": "musor.blog"
}
DNS records
{
    "A": [
        "188.114.96.3",
        "188.114.97.3"
    ],
    "NS": [
        "henrik.ns.cloudflare.com",
        "ruth.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"henrik.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2415441006, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}",
    "TXT": [
        "yandex-verification: 991fcc836a0ca8f9"
    ],
    "AAAA": [
        "2a06:98c1:3121::3",
        "2a06:98c1:3120::3"
    ]
}
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
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "2a06:98c1:3120::3",
    "family": 6
}
Redirects
{
    "chain": [
        "https://musor.blog"
    ]
}
Subdomains
{
    "count": 23,
    "subdomains": [
        "apgreid.musor.blog",
        "bonusy.musor.blog",
        "chestnost.musor.blog",
        "faq.musor.blog",
        "gid.musor.blog",
        "keisy-cs2.musor.blog",
        "kontrakty.musor.blog",
        "musor14.musor.blog",
        "musor19.musor.blog",
        "musor26.musor.blog",
        "musor32.musor.blog",
        "musor39.musor.blog",
        "musor4.musor.blog",
        "musor6.musor.blog",
        "musor9.musor.blog",
        "mystery-box.musor.blog",
        "novosti.musor.blog",
        "nozhi-cs2.musor.blog",
        "obzor.musor.blog",
        "promocod.musor.blog",
        "shansy.musor.blog",
        "vhod-steam.musor.blog",
        "vyvod-skina.musor.blog"
    ]
}
Page links
{
    "external": [
        "https://musor.click/HBlQV3uh"
    ],
    "external_count": 1,
    "internal_count": 4
}
Registration record
{
    "registrar": "Dynadot LLC",
    "created": "2026-09-04T03:38:58Z",
    "updated": "2026-09-09T03:42:55Z",
    "expires": "2027-09-04T03:38:58Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp",
        "serverTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "henrik.ns.cloudflare.com",
        "ruth.ns.cloudflare.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html"
    }
}

Questions about musor.blog

Is musor.blog legit?

No. PhishDestroy classifies musor.blog as a Cs2 impersonation page (risk: critical, 81/100); it was first detected on 2026-10-25. VirusTotal: 2/92 engines flag it. Treat the site as unsafe.

Is musor.blog safe to connect a wallet?

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

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 · 4 captures

Primary capture 1 / 4
SourcePrimary capture
Recorded
StateStored capture
HTTP statusNot recorded for this capture
Final URLNot recorded for this capture
Position1 / 4
Open capture Wayback Download
All capture links and hashes (4)
Observed page title
MUSOR DROP на musor.blog — разбор кейсов CS2 и код INVFMFEP7
Automated brand references
Cs2 Steam
TLS Certificate
Issued by WE1 · stored validity ends in 55 days

Domain details

Domain
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Dynadot US(US)
Abuse contact["info@dynadot.com", "06e9e0e26edd1e63s@"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for musor.blog →
RegistrationCreated Sep 4, 2026 (51d · New) — Expires Sep 4, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 25, 2026
DOM Analysisanalyzed Oct 25, 2026score 81/1002 brand signals
Submitted URLhttps://musor.blog/
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

Shared CDN edge
Resolved IP
188.114.97.3
Network ASN
AS13335
Organization
CloudFlare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • henrik.ns.cloudflare.com
  • ruth.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
WE1
Valid from
2026-09-21 00:48:04
Valid until
2026-12-20 01:48:01
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint53ed1da7914d6cd7802066acff982e99690111576c8a9d49d4201753448348a2
Certificate names · 3 SANs
  • musor.blog
  • musor26.musor.blog
  • *.musor26.musor.blog

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

viewdns.info · 188.114.97.3rapiddns.io
Recorded subdomains23

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

  • apgreid.musor.blogDomain record
  • bonusy.musor.blogDomain record
  • chestnost.musor.blogDomain record
  • faq.musor.blogDomain record
  • gid.musor.blogDomain record
  • keisy-cs2.musor.blogDomain record
  • kontrakty.musor.blogDomain record
  • musor14.musor.blogDomain record
  • musor19.musor.blogDomain record
  • musor26.musor.blogDomain record
  • musor32.musor.blogDomain record
  • musor39.musor.blogDomain record
  • musor4.musor.blogDomain record
  • musor6.musor.blogDomain record
  • musor9.musor.blogDomain record
  • mystery-box.musor.blogDomain record
  • novosti.musor.blogDomain record
  • nozhi-cs2.musor.blogDomain record
  • obzor.musor.blogDomain record
  • promocod.musor.blogDomain record
  • shansy.musor.blogDomain record
  • vhod-steam.musor.blogDomain record
  • vyvod-skina.musor.blogDomain record

The original observation time is not recorded for these hostnames.

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

VirusTotal Analysis

2 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 0 detections
Forcepoint ThreatSeeker
SOCRadar

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of musor.blog · checked Oct 25, 2026

68
Needs Work
Performance
FCP
2.86 s
First Contentful Paint
LCP
40.92 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
9 ms
Total Blocking Time
SI
4.47 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://musor.blog/
MUSOR DROP на musor.blog — разбор кейсов CS2 и код INVFMFEP7
Гид musor.blog: лента дропов, кейсы CS2, апгрейд, контракт и куда вставлять INVFMFEP7. RTP 98%. 18+.
Response
HTTP 200
HTML body
15.2 KB
Compressed
5.2 KB
Links
5 internal · 9 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html
CF-Cache-Status: HIT
Cache-Control: public, max-age=0, must-revalidate
Content-Encoding: gzip
Server: cloudflare
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Favicon fingerprint: d2a41aabb6b6a127aa8d0c5836d0666c9b4049e0a3546773ef544200b388e7a1
Open Graph title: MUSOR DROP на musor.blog — разбор кейсов и код INVFMFEP7
Open Graph description: Как устроены кейсы, усиление и контракт. Код INVFMFEP7 — после Steam, не в ленте.
Saved response-header values · 12
alt-svc
h3=":443"; ma=86400
Cache-Control
public, max-age=0, must-revalidate
CF-Cache-Status
HIT
CF-RAY
a5020b8e9f11e7bd-FRA
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html
Date
Sun, 25 Oct 2026 14:52:27 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=Tg3t1ZGdjiFjj4LbVUP691q%2B68zvi%2BxfODIPYI6qECPaZyu4q43EDZNc04riYhv20zJtvunamExudLrSF1HBZfNQ%2BXX2rk4qTF3cN1UgxvX22TJyjGDqKR4By7ss"}]}
Server
cloudflare
Transfer-Encoding
chunked

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.

Stored observation history2

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. VirusTotal · Detection count

    0→2

    Engines added
    Forcepoint ThreatSeeker · SOCRadar
    Engines removed
    None recorded
    Recorded vendor total
    2
  2. Domain monitor · First collection record

    Reachable

All retained availability observations2

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_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 15:51:53.000000
    Evidence SHA-256
    86a2cfb76450725d490be7d395c2982f221bba721e22a5eead7e095ef6789dce
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 15:51:53
    Evidence reason
  2. 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 15:51:53.000000
    Evidence SHA-256
    86a2cfb76450725d490be7d395c2982f221bba721e22a5eead7e095ef6789dce
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 15:51:53
    Evidence reason

Recorded activity

5 entries
  1. AlienVault OTX

    4 community references

    View source
  2. VirusTotal

    2/92 engine detections

    View source
  3. Wayback Machine

    Page archived

    View source
  4. Added to PhishDestroy

    musor.blog

    View source
  5. 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

Check for cloaking

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

musor.blog

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 2 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Open report OTX 4 refs 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?

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

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 musor.blog)
  • 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/musor.blog"
  title="PhishDestroy threat report for musor.blog"
  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>