Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 20/92 engines flagged. malicious: 16. suspicious: 4. Analysis time (as stored): 2026-10-22T06:06:25Z. Retrieved (as stored): 2026-11-02T12:14:55Z. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
radio-muza.eu favicon

radio-muza.eu

In short

PhishDestroy first recorded radio-muza.eu on 2026-11-02. Stored VirusTotal result: 20/92 engines flagged. malicious: 16. suspicious: 4. Analysis time (as stored): 2026-10-22T06:06:25Z. Retrieved (as stored): 2026-11-02T12:14:55Z.

Review the evidence
Registrar
LH.pl Sp. z o.o
Resolved IP
Germany85.215.192.249IONOS SE
First observed
Nov 2, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 20/92
VirusTotal
20 / 92
engine detections ·
URLQuery
2
detections
URLScan
Malicious
engine verdict · score 85
Page captures
2
open gallery
Reports sent
1
view timeline
Nov 2, 2026 1 Report Sent
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded radio-muza.eu on 2026-11-02. Stored VirusTotal result: 20/92 engines flagged. malicious: 16. suspicious: 4. Analysis time (as stored): 2026-10-22T06:06:25Z. Retrieved (as stored): 2026-11-02T12:14:55Z. Risk: critical (100/100). Registrar: LH.pl Sp. z o.o. Status: Last known active. Hosting: IONOS SE. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
20 / 92
Hosting
Germany85.215.192.249IONOS SE
Registrar
LH.pl Sp. z o.o
Page captures
2
Page captures Source results Registration record

Recorded source summary

PhishDestroy stores a record for radio-muza.eu. Source observations are dated separately; missing checks do not establish safety.

A reviewed analysis is not available for this text revision. Consult the dated source records below.

Source evidenceVirusTotal 20 / 92 3 sources

VirusTotal

20 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 8 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
41
Malicious
16
Suspicious
4
Undetected
31

Vendor labels

CRDF
malicious
DNS8
suspicious
ESET
suspicious
Ermes
not recommended
VIPRE
phishing
G-Data
phishing
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Webroot
malicious
Fortinet
phishing
PREBYTES
phishing
SOCRadar
phishing
Kaspersky
phishing
LevelBlue
phishing
Seclookup
malicious
Gridinsoft
suspicious
BitDefender
phishing
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

First seen

DNS records

  • TTL, seconds
    3600
    Type
    SOA
    Responsible mailbox
    root.lh.pl
    Value
    ns.lh.pl
  • TTL, seconds
    3600
    Type
    NS
    Value
    ns2.lighthosting.net
  • TTL, seconds
    3600
    Type
    NS
    Value
    ns.lh.pl
  • TTL, seconds
    3600
    Type
    TXT
    Value
    v=spf1 include:_spf.lh.pl -all
  • TTL, seconds
    3600
    Type
    A
    Value
    85.215.192.249

DNS records observed

JARM fingerprint

28d28d28d00028d00042d42d000000831b6af40378e2dd35eeac4e9311926e

Certificate

Subject alternative names
  • radio-muza.eu
  • www.radio-muza.eu
Issuer
Let's Encrypt / YE1
Serial
5cb9bd7de403eabcf4d941f973f33113682
SHA-256
e24a636b89ef66c53dc1c8a8fdaa1b03ca1dc865bebe18c58052d1aaf15a7a0b
Subject
radio-muza.eu
Valid until
Valid from
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 41,
    "malicious": 16,
    "suspicious": 4,
    "undetected": 31
}
Vendor labels
{
    "CRDF": "malicious",
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "Ermes": "not recommended",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "PREBYTES": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "LevelBlue": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
First seen
2026-09-05T21:51:48Z
DNS records
[
    {
        "ttl": 3600,
        "type": "SOA",
        "rname": "root.lh.pl",
        "value": "ns.lh.pl"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns2.lighthosting.net"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns.lh.pl"
    },
    {
        "ttl": 3600,
        "type": "TXT",
        "value": "v=spf1 include:_spf.lh.pl -all"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "85.215.192.249"
    }
]
Dns at
2026-10-22T06:11:57Z
Jarm
28d28d28d00028d00042d42d000000831b6af40378e2dd35eeac4e9311926e
Certificate
{
    "san": [
        "radio-muza.eu",
        "www.radio-muza.eu"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "5cb9bd7de403eabcf4d941f973f33113682",
    "sha256": "e24a636b89ef66c53dc1c8a8fdaa1b03ca1dc865bebe18c58052d1aaf15a7a0b",
    "subject": "radio-muza.eu",
    "valid_to": "2027-01-18T16:18:53Z",
    "valid_from": "2026-10-20T16:18:54Z"
}
Separate collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

source
VirusTotal
scope
unknown
result_state
null
numerator
16
denominator
null
malicious
null
suspicious
null
vendors
["alphaMountain.ai","BitDefender","CRDF","CyRadar","Forcepoint ThreatSeeker","Fortinet","G-Data","Kaspersky","LevelBlue","Lionic","PREBYTES","Seclookup","SOCRadar","Sophos","VIPRE","Webroot"]
observed_at
null
checked_at
null
fetched_at
null
time_basis
as stored; legacy timezone not established

URLScan

Malicious · engine verdict · score 85

SHA-256 7e7cf22d920332549eb30ba308e36bf1427dec0306aa62bcc7c485c57d38c79b

Open report
URLScanOriginal source recordObserved: 24 fields

Observed: · Retrieved:

Report ID

01a19c19-0250-72db-a9fd-676db89b8180

Final URL

https://radio-muza.eu/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://radio-muza.eu/
    From
    http://radio-muza.eu/
    Status
    307

IP address

85.215.192.249

Reverse DNS (PTR)

ip85.215.192.249.pbiaas.com

Contacted domains

  • fonts.gstatic.com
  • cdnjs.cloudflare.com
  • fonts.googleapis.com

Contacted IP addresses

  • 142.251.110.94
  • 104.17.25.14
  • 142.251.110.95
  • 85.215.192.249

Autonomous systems (ASN)

  • 15169
  • 13335
  • 8560

Server countries

  • US
  • DE

Linked domains

  • tvn24.pl
  • fakty.tvn24.pl
  • eurosport.tvn24.pl
  • www.facebook.com
  • x.com
  • konkret24.tvn24.pl
  • kontakt24.tvn24.pl
  • tvn.pl
  • tvnstyle.pl

Social media links

  • https://www.facebook.com/tvn24pl
  • https://x.com/intent/follow

Document hash

7e7cf22d920332549eb30ba308e36bf1427dec0306aa62bcc7c485c57d38c79b

Script hashes

  • 1ed07ebaaaf20e9a88e7769d3a5a6784b5c195373ee5f08fb7df5c8382394855

JavaScript globals

  • FontAwesomeConfig
  • ___FONT_AWESOME___
  • __vite_is_modern_browser

TLS session and certificate

Subject alternative names
  • radio-muza.eu
  • www.radio-muza.eu
Cipher
AES_256_GCM
Issuer
YE2
Subject
radio-muza.eu
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

57

Registered domain age, days

57

Certificate age, days

1

Certificate validity, days

89

Page requests

22

Provider verdicts

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

HTTP headers

Server
nginx
Content-type
text/html
Original source fields · JSON
Uuid
01a19c19-0250-72db-a9fd-676db89b8180
Final url
https://radio-muza.eu/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://radio-muza.eu/",
        "from": "http://radio-muza.eu/",
        "status": 307
    }
]
Ip
85.215.192.249
Ptr
ip85.215.192.249.pbiaas.com
Contacted domains
[
    "fonts.gstatic.com",
    "cdnjs.cloudflare.com",
    "fonts.googleapis.com"
]
Contacted IP addresses
[
    "142.251.110.94",
    "104.17.25.14",
    "142.251.110.95",
    "85.215.192.249"
]
Asns
[
    "15169",
    "13335",
    "8560"
]
Countries
[
    "US",
    "DE"
]
Linked domains
[
    "tvn24.pl",
    "fakty.tvn24.pl",
    "eurosport.tvn24.pl",
    "www.facebook.com",
    "x.com",
    "konkret24.tvn24.pl",
    "kontakt24.tvn24.pl",
    "tvn.pl",
    "tvnstyle.pl"
]
Social
[
    "https://www.facebook.com/tvn24pl",
    "https://x.com/intent/follow"
]
Document hash
7e7cf22d920332549eb30ba308e36bf1427dec0306aa62bcc7c485c57d38c79b
Script hashes
[
    "1ed07ebaaaf20e9a88e7769d3a5a6784b5c195373ee5f08fb7df5c8382394855"
]
Globals
[
    "FontAwesomeConfig",
    "___FONT_AWESOME___",
    "__vite_is_modern_browser"
]
Tls
{
    "san": [
        "radio-muza.eu",
        "www.radio-muza.eu"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "YE2",
    "subject": "radio-muza.eu",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-30T11:42:18Z",
    "valid_from": "2026-11-01T11:42:19Z"
}
Domain age days
57
Apex age days
57
Tls age days
1
Tls valid days
89
Requests
22
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 85,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx",
    "content-type": "text/html"
}

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

Mail configuration

SPF record
v=spf1 include:_spf.lh.pl -all
SPF lookups
1

CAA records

Domain
radio-muza.eu

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

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

Page title and metadata

Page title
TVN24
Indexing directives
noindex,nofollow
Open Graph image
https://zapodaj.net/images/97090fe94b2f0.png
Open Graph title
Tragiczna śmierć młodego rapera! [WIDEO]
Open Graph description
Przechodnie nagrali całe zajście.

Trackers

Requests
19
Observed services
  • Name
    Cloudflare
    Company
    Cloudflare
    Country
    US
    Category
    Hosting
    Requests
    2
  • Name
    Google Fonts
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    Google Static
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    2

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
26
TLS
19
Waiting
457
Connection
15
Download
0
Response time, ms
517

TLS connection

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

Ports

Open ports
  • 22
  • 80
  • 443

Carbon estimate

Bytes
2799
CO₂, grams
0.0001
Cleaner than, %
95

DNS servers

Nameservers
  • IP address
    3.67.205.197
    Host
    ns.lh.pl
  • IP address
    52.57.104.17
    Host
    ns2.lighthosting.net
DNS zone
radio-muza.eu

Location

IP address
85.215.192.249
ASN
8560
Organization
IONOS SE
City
Berlin
Country
DE

TLS certificate

Issuer
Let's Encrypt / YE2
Subject
radio-muza.eu

DNS records

A
  • 85.215.192.249
NS
  • ns2.lighthosting.net
  • ns.lh.pl
SOA
Primary nameserver
ns.lh.pl
Hostmaster
root.lh.pl
Serial
2008052701
Refresh, seconds
1200
Retry, seconds
600
Expiry, seconds
604800
Minimum TTL, seconds
86400
TXT
  • v=spf1 include:_spf.lh.pl -all

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

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

IP lookup

IP address
85.215.192.249
IP version
4

Redirects

Redirect chain
  • https://radio-muza.eu

Registration record

Registrar
LH.pl Sp. z o.o.
Nameservers
  • ns2.lighthosting.net
  • ns.lh.pl

HTTP headers

Response headers
Server
nginx
Content-type
text/html
Original source fields · JSON
Mail configuration
{
    "spf": "v=spf1 include:_spf.lh.pl -all",
    "spf_lookups": 1
}
Caa records
{
    "domain": "radio-muza.eu"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-11-02T11:53:53Z",
    "first": "2026-11-02T11:53:53Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 1974
}
Page title and metadata
{
    "title": "TVN24",
    "robots": "noindex,nofollow",
    "ogImage": "https://zapodaj.net/images/97090fe94b2f0.png",
    "ogTitle": "Tragiczna śmierć młodego rapera! [WIDEO]",
    "ogDescription": "Przechodnie nagrali całe zajście."
}
Trackers
{
    "requests": 19,
    "trackers": [
        {
            "name": "Cloudflare",
            "company": "Cloudflare",
            "country": "US",
            "category": "Hosting",
            "requests": 2
        },
        {
            "name": "Google Fonts",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        },
        {
            "name": "Google Static",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 2
        }
    ]
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 26,
        "tls": 19,
        "wait": 457,
        "connect": 15,
        "download": 0
    },
    "response_ms": 517
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        22,
        80,
        443
    ]
}
Carbon
{
    "bytes": 2799,
    "co2_grams": 0.0001,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "ip": "3.67.205.197",
            "host": "ns.lh.pl"
        },
        {
            "ip": "52.57.104.17",
            "host": "ns2.lighthosting.net"
        }
    ],
    "zone": "radio-muza.eu"
}
Location
{
    "ip": "85.215.192.249",
    "asn": "8560",
    "org": "IONOS SE",
    "city": "Berlin",
    "country": "DE"
}
Ssl
{
    "issuer": "Let's Encrypt / YE2",
    "subject": "radio-muza.eu"
}
DNS records
{
    "A": [
        "85.215.192.249"
    ],
    "NS": [
        "ns2.lighthosting.net",
        "ns.lh.pl"
    ],
    "SOA": "{\"nsname\": \"ns.lh.pl\", \"hostmaster\": \"root.lh.pl\", \"serial\": 2008052701, \"refresh\": 1200, \"retry\": 600, \"expire\": 604800, \"minttl\": 86400}",
    "TXT": [
        "v=spf1 include:_spf.lh.pl -all"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "85.215.192.249",
    "family": 4
}
Redirects
{
    "chain": [
        "https://radio-muza.eu"
    ]
}
Registration record
{
    "registrar": "LH.pl Sp. z o.o.",
    "nameservers": [
        "ns2.lighthosting.net",
        "ns.lh.pl"
    ]
}
HTTP headers
{
    "headers": {
        "server": "nginx",
        "content-type": "text/html"
    }
}

Questions about radio-muza.eu

Is radio-muza.eu legit?

PhishDestroy rates radio-muza.eu as critical risk (100/100) from the recorded evidence; it was first recorded on 2026-11-02. Stored VirusTotal result: 20/92 engines flagged. malicious: 16. suspicious: 4. Analysis time (as stored): 2026-10-22T06:06:25Z. Retrieved (as stored): 2026-11-02T12:14:55Z. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is radio-muza.eu safe to connect a wallet?

This report does not record which wallet requests radio-muza.eu 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 radio-muza.eu?

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

Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 2 captures

URLScan · 2026-11-02 1 / 2
SourceURLScan · 2026-11-02
Recorded
StateStored capture
HTTP status200
Final URLhttps://radio-muza.eu/
Position1 / 2
Open capture Source Report Wayback Download
All capture links and hashes (2)
  • URLScan · 2026-11-02 · 2026-11-02 11:50 UTC · Source report
    SHA-256: 9f486023baa919dc63e285a14dad577719490ae599c8701ca1378b440dbe04cb · 33814 bytes
  • URLQuery · Capture time unavailable · Source report
    SHA-256: df7170b294a410e734095549999315104fe8c5c20474a2ff4f37cd31134a0b0b · 53476 bytes

Domain details

Domain
IP Reputation Germany85.215.192.249 abuse score 0/100 0 reports checked Nov 2, 2026
Registrar LH.pl Sp. z o.o
Abuse contactabuse@ionos.com, abuse@strato.de
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for radio-muza.eu →
Hosting abuse contact abuse@ionos.com IONOS SE · AS8560
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedNov 2, 2026
Submitted URLhttp://radio-muza.eu/
Case ID
TLS Certificate
Issued by YE2 · stored validity ends in 88 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Germany85.215.192.249
Network ASN
AS8560
Organization
IONOS SE
Observed location
GermanyBerlin, DE
Server header
nginx

Nameservers 7

  • ns.lh.pl
  • visit
  • www.eurid.eu
  • for
  • more
  • info
  • ns2.lighthosting.net

SOA

  • nsname: ns.lh.pl
  • hostmaster: root.lh.pl
  • serial: 2008052701
  • refresh: 1200
  • retry: 600
  • expire: 604800
  • minttl: 86400

Location describes the IP network.

TLS certificate

Issuer
YE2
Valid from
2026-11-01 11:42:19
Valid until
2027-01-30 11:42:18
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprinte24a636b89ef66c53dc1c8a8fdaa1b03ca1dc865bebe18c58052d1aaf15a7a0b
Certificate names · 2 SANs
  • radio-muza.eu
  • www.radio-muza.eu

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

viewdns.info · 85.215.192.249rapiddns.io
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

20 / 92 security vendors flagged this domain
View on VT
Last analyzed
CRDF
DNS8
ESET
Ermes
VIPRE
G-Data
Lionic
Sophos
CyRadar
Webroot
Fortinet
PREBYTES
SOCRadar
Kaspersky
LevelBlue
Seclookup
Gridinsoft
BitDefender
alphaMountain.ai
Forcepoint ThreatSeeker

Archived Evidence

Wayback Machine Snapshot
View Archive
Stored Capture Evidence 1 snapshot

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

Archived HTTP response HTTP 200
Requested URL: http://radio-muza.eu/
Final URL: https://radio-muza.eu/
TVN24
Response
HTTP 200
HTML body
2.7 KB
Compressed
1.3 KB
Links
0 internal · 0 external
Detected technologies
nginx
Selected response headers
Server: nginx
Content-Type: text/html
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Open Graph title: Tragiczna śmierć młodego rapera! [WIDEO]
Open Graph description: Przechodnie nagrali całe zajście.
Saved response-header values · 10
Accept-Ranges
bytes
Connection
keep-alive
Content-Encoding
gzip
Content-Length
1302
Content-Type
text/html
Date
Mon, 02 Nov 2026 11:53:30 GMT
Etag
"aef-65ac4285a1598-gzip"
Last-Modified
Sat, 05 Sep 2026 22:46:37 GMT
Server
nginx
Vary
Accept-Encoding

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.

Captured network requests

Network requests: 22 SHA-256 hashes: 22 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-11-02 11:53 UTC.

Open this scan on URLScan 01a19c19-0250-72db-a9fd-676db89b8180 ↗

Stored observation history1

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

  1. Domain monitor · First collection record

    Reachable

Separate monitor HTTP observation

Source: domain_monitor. This stored snapshot does not establish current availability.

Observed · UTC
Recorded HTTP status
200
Probe value as recorded
200
Original source timestamp
2026-11-02 12:28:09
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
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    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-02 12:52:48.000000
    Evidence SHA-256
    8a9c5838a8ce09de727d1267233ce7ade4ee698ea9ffe20a629190a498570457
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-02 12:52:48
    Evidence reason
  2. 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-11-02 12:52:48.000000
    Evidence SHA-256
    8a9c5838a8ce09de727d1267233ce7ade4ee698ea9ffe20a629190a498570457
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-02 12:52:48
    Evidence reason

Threat Response Pipeline

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

Recorded events: 8. 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
    radio-muza.eu detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Web Archive · VirusTotal · Forensic Evidence Collected Recorded: 5 of 5
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 85
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 20/92
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, URLQuery, stored screenshot
Notification RecordsSent Report Recorded Recorded: 1 of 1
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: LH.pl Sp. z o.o.. Abuse contacts: 1.
    • abuse@ionos.com
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

5 entries
  1. Abuse report sent

    PD-EDD2173BAE5B13C3669D · Receipt 84280

    abuse@ionos.com
  2. Wayback Machine

    Page archived

    View source
  3. Added to PhishDestroy

    radio-muza.eu

    View source
  4. URLScan

    Page captured

    View source
  5. VirusTotal

    20/92 engine detections

    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
All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

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

radio-muza.eu

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 20 det. ChainPatrol URLQuery 2 det. SSL Labs Stored certificate dates valid WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-EDD2173BAE5B13C3669D Recipient: abuse@ionos.com
Page title stored with report: TVN24
PDF notice generated
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

5 evidence signal groups linked 1 stored notification records Last known active
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.

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 radio-muza.eu)
  • 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/radio-muza.eu"
  title="PhishDestroy threat report for radio-muza.eu"
  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>