VirusTotal
16 / 89
“K-POP STUDIO FANCY”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@dynadot.com.
The latest stored availability evidence still shows the domain reachable; 1 month 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.
16 / 89
provider verdict: malicious
ReportReport stored; detailed verdict not recorded
Report5 community references
Reportstored report
Report Analysis completed
ReportChecked; no threat flag recorded
Reportfancymusic.live returned HTTP status 200 on 2026-10-01, according to the recorded HTTP check. The domain was first observed on 2026-09-10, and its registration date is listed as 2026-08-10.
The HTTP check on 2026-10-01 recorded status 200 for fancymusic.live, while the first observation of the domain dates to 2026-09-10. VirusTotal, checked on 2026-09-18, reported 16 detections across 89 scanners. OTX, checked on 2026-09-10, showed 5 pulses, and the PhishDestroy internal listing was recorded as true. The registrar is Dynadot Inc, and the SSL issuer is Google Trust Services / WE1, scanned on 2026-09-11.
The OTX and PhishDestroy records were both captured on 2026-09-10, so they reflect the same early observation window, while the VirusTotal scan on 2026-09-18 and the HTTP check on 2026-10-01 occurred later. Because these named sources were collected on different dates, a reader can compare how the recorded signals evolved over that period rather than treating them as a single snapshot. The SSL scan on 2026-09-11 sits between the earliest observations and the later checks, adding another dated reference point.
Anyone reviewing fancymusic.live should retain the dated records from OTX, VirusTotal, and the HTTP check so that later observations can be compared against them. Subsequent checks should be logged with their own dates and source names, allowing changes in the recorded signals to be tracked over time. During any review, avoid submitting sensitive information to the domain until the recorded evidence has been fully assessed.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare
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.
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.
Edge-IP reputation is not attributed to this domain.
arnold.ns.cloudflare.comgigi.ns.cloudflare.comLocation describes the IP network.
f99d6846b982508366fb29690451cb834f0b493e7386eb20e13c6c762ebbc871Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
188.114.96.3. 11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
PD-20260910-511C40 Recipient: abuse@dynadot.com Registrar: Dynadot LLC / Dynadot Inc (United States) Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
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
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