Skip to security report
Domain security report
musordrop2.com favicon

musordrop2.com

“Security Check”

Threat verdict
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Availability Last known active Latest stored reachability observation Observed · HTTP probe
VirusTotal detections: 16/89 Spamhaus DBL: DBL_PHISH Stored blocklist matches: 2 Automated brand label: Steam
OTX: 7 refs Sep 9, 2026 Steam CDN
API
Registrar
Fewmoretaps OU d/b/a T…
Resolved IP
45.74.7.27
Registered
Sep 3, 2026
3 sources
In this reportGet help
This domain has been flagged as malicious
Security engines reporting a detection: 16. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.

Additional indicators at a glance

Spamhaus DBL
DBL_PHISH
VirusTotal
VirusTotal
16 det.
OTX references
URLScan
URLScan
ScamAdviser
Scamadviser
80/100Likely Safe
TLS Certificate
Within stored validity dates
Let's Encrypt / YR2 · Hostname coverage not recorded
Age
1 mo New
Observed status
Last known active 200
PhishDestroy
DestroyList
Listed

Source evidence

9 · sources

These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.

VirusTotal

16 / 89

Report
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

URLScan verdict

malicious

Report
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

Public blocklists

2 external matches

Details
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Spamhaus DBL

DBL_PHISH

Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

OTX

7 community references

Report
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

CF Radar

provider verdict: clean

Observation time not recorded
Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

URLScan capture

stored report

View stored capture ↗
Report
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

Scamadviser

80/100

Observation time not recorded
Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Google Safe Browsing

Checked; no threat flag recorded

Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Network Security Intelligence Registrar context
Registrar context Trustname
Stored registration data identifies Trustname / Fewmoretaps OÜ (IANA 4318) as the registrar. PhishDestroy maintains a separate registrar investigation; that material is contextual and is not an independent detection for this domain.
Trustname Investigation

Evidence Summary

Critical
VirusTotal
16/89
OTX
7 community refs
URLScan
Stored capture

AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.

Assessment

Stored evidence for musordrop2.com: VirusTotal recorded 2 detections among 89 scanners on 2026-09-09. That ratio reproduces the stored check in its original units and is not converted into another measure. MetaMask and SEAL appear as named external blocklist observations for musordrop2.com. Each item in this report remains at the scope supplied by its dated source record.

Detection Evidence

VirusTotal records 2 detections among 89 scanners in the stored snapshot dated 2026-09-09. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-09-09 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.

Source Context

MetaMask and SEAL are recorded as named external blocklist observations for musordrop2.com in the snapshot dated 2026-09-09. The stored MetaMask and SEAL blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains musordrop2.com as a publisher record. That PhishDestroy record is counted separately from the MetaMask and SEAL external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.

Reachability and Timeline

The record first observed musordrop2.com on 2026-09-09. The MetaMask and SEAL blocklist snapshot is dated 2026-09-09 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-09-03. A URLScan reference was stored on 2026-09-09 as a dated artifact for review. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.

Registration and Infrastructure

The source stores 45.74.7.27 as the observed address in this record. The registration date for musordrop2.com is recorded as 2026-09-03. The stored ASN observation records AS13335 and CLOUDFLARENET - Cloudflare, Inc., US in this record. The observed server header is recorded as Microsoft-IIS/10.0 in this record. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.

Conclusion

The musordrop2.com record states that VirusTotal recorded 2 detections among 89 scanners on 2026-09-09. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-09-09. PhishDestroy remains a separate publisher catalogue entry in the stored record. The observed address field in this record contains 45.74.7.27. The supported conclusion is bounded to the exact stored observations for musordrop2.com. Any statement beyond those source values would require additional dated material.

Recommended Actions

Avoid submitting sensitive information to musordrop2.com during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain musordrop2.com as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and MetaMask and SEAL blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to musordrop2.com. The stored record does not justify extending that rule to 45.74.7.27 or to other infrastructure records.

Data coverage & collection

20 · datasets with records / 11 · not recorded

What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.

Recorded dataPartial recordUTC
VirusTotal
16 / 89 · engine detections
URLScan analysis
Automated verdict retained
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
7 · community references
External blocklists
2 · external matches
Cloudflare Radar
cleanCollection time not recorded
Scamadviser
80/100 · provider trust scoreCollection time not recorded
Spamhaus DBL
DBL_PHISH
Domain registration
Fewmoretaps OU d/b/a Trustname.comCollection time not recorded
Network & DNS
45.74.7.27 · 2 · nameserversCollection time not recorded
TLS certificate
Let's Encrypt / YR2
Page captures
3 · retained captures
Page analysis
1 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
PageSpeed performance
27/100 · mobile performance
Availability history
33 · stored state changes
Source observation history
5 · stored source events
IP reputation
Network-level observations
Wayback archive
Archive link retained
Not recorded in this report 11

These checks have no retained result. This does not mean they passed or that a scan is running.

  • URLQuery
  • PhishStats
  • DNS security filters
  • Gridinsoft
  • HTML archives
  • Site configuration files
  • Response records
  • Recorded subdomains
  • Lookalike relationships
  • Community reports
  • Chainabuse records
Download the dated observations and supporting metadata.

Blocklist records

2 · external source matches

Public Blocklist Status

Domain, network & archive

Fewmoretaps OU d/b/a Trustname.com · 45.74.7.27 · DNS, TLS and retained responses

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Steam report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-09activeall-domainsblocklistcontentcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar Fewmoretaps OU d/b/a T… BY(BY) PhishDestroy Investigation
RegistrationCreated Sep 3, 2026 (44d · New) — Expires Sep 3, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedSep 9, 2026
DOM Analysisanalyzed Sep 9, 2026score 100/1001 brand signal
Submitted URLhttps://musordrop2.com/plltm6g2y2u5.html
Favicon Hash

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
45.74.7.27
Network ASN
AS13335
Organization
CLOUDFLARENET - Cloudflare, Inc., US
Observed location
Rotterdam, NL
Server header
Microsoft-IIS/10.0

Edge-IP reputation is not attributed to this domain.

Nameservers 2
  • frost.majahan.com
  • prism.majahan.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR2
Valid from
2026-09-08 21:26:19
Valid until
2026-12-07 21:26:18
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-10-09 13:03:31 UTC
Collection source
PhishDestroy collector
Certificate fingerprintafc5ba4689bd527549c2f3673d736ad67e8c5e52d38a86560ca0c11940512bee

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

Latest Classified Outcome 2026-10-17 10:33:43 UTC

Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-17 10:33:43 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-17 10:33:43 UTC last content: 2026-10-17 10:33:43 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

16 / 89 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 15 detections
alphaMountain.ai
BitDefender
CRDF
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
LevelBlue
Lionic
SOCRadar
Sophos
VIPRE
Webroot

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of musordrop2.com · checked Sep 9, 2026

27
Poor
Performance
FCP
9.86s
First Contentful Paint
LCP
105.81s
Largest Contentful Paint
CLS
1.291
Cumulative Layout Shift
TBT
232ms
Total Blocking Time
SI
9.86s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Detection & evasion checks

Stored browser and crawler observations

Detection-evasion analysis

Cloaking and traffic-distribution check

Not yet scanned No crawler-versus-browser difference has been recorded yet

Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.

Stored cloaking flag
Not yet scanned
Last cloaking scan
Server header seen by scanner
Microsoft-IIS/10.0

Scanner note: alive_content: raw=ok; http=200; via=https_proxy; server=Microsoft-IIS/10.0

Live TDS fingerprint check
Seven Keitaro fingerprints and a browser-versus-crawler comparison. A new scan starts only when you press the button.
On demand

No live-check result has been retained.

Timeline & response

Collection history, report status and investigation channels

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
  1. Domain Status Transition 2026-09-29 02:03:25 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from dead to alive.
  2. Domain Status Transition 2026-09-10 22:36:43 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
  3. VirusTotal Detections Update 2026-09-09 12:22:04 UTC
    Source: VirusTotal
    Event details
    VirusTotal scanner detections updated from 1 to 2. Added scanner alerts: SOCRadar.
  4. VirusTotal Detections Update 2026-09-09 09:10:52 UTC
    Source: VirusTotal
    Event details
    VirusTotal scanner detections updated from 0 to 1. Added scanner alerts: alphaMountain.ai.
  5. Threat First Observed 2026-09-09 03:27:55 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as unknown pointing to IP 45.74.7.27.
Stored observation history38

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

  1. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

Earlier observations 33
  1. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  6. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  7. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  8. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  9. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  10. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  11. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  12. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  13. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  14. Availability monitor · Recorded state

    redirected→live_content

    content_served

  15. Availability monitor · Recorded state

    live_content→redirected

    http_redirect

  16. Availability monitor · Recorded state

    redirected→live_content

    content_served

  17. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  18. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  19. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  20. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  21. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  22. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  23. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  24. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  25. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  26. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  27. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  28. Availability monitor · Recorded state

    Unknown

    probe_inconclusive

  29. Availability monitor · Recorded state

    Unavailable→Reachable

  30. Availability monitor · Recorded state

    Reachable→Unavailable

  31. VirusTotal · Detection count

    1→2

  32. VirusTotal · Detection count

    0→1

  33. Availability monitor · First collection record

    Unknown

Threat Response Pipeline

Discovery
Analysis
Monitoring

18 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Threat Ingested
musordrop2.com detected and queued for full analysis
Sep 9, 2026
Spamhaus DBL
Spamhaus DBL recorded DBL_PHISH
Oct 9, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Sep 9, 2026
URLScan Verdict
URLScan returned a malicious verdict · score 100
Sep 9, 2026
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
Web Archive
Preserved in Wayback Machine — historical evidence archived
Oct 14, 2026
VirusTotal
16/89 recorded on VirusTotal
Sep 20, 2026
Blocklist Detection
Found in 2 blocklists: MetaMask, SEAL
Oct 17, 2026
OTX Community References
7 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
Oct 9, 2026
Registrar Context: Trustname
Separate registrar research is available. Registrar association is contextual and is not scored as an independent detection.
Brand Impersonation
Impersonation of Steam
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
Sep 9, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 17, 2026
Site Came Back Online
Domain is responding again — monitoring resumed
Sep 29, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response; the cause was not independently established.
Sep 11, 2026
VT Detection +1
+1 new detection (1 → 2): SOCRadar
Sep 9, 2026
VT Detection +1
+1 new detection (0 → 1): alphaMountain.ai
Sep 9, 2026
DestroyList Published
Sep 9, 2026
Monitoring Continues
The domain remains reachable or access-restricted; future checks may update this observation.
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.

Related infrastructure

Shared hosting, registrar records and related domains

Evidence & investigation tools

Original reports, independent checks and evidence links

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Were You Affected by This Site?

5 evidence signal groups linked 0 stored notification records Last known active

Listed domains receive at least one abuse report; this entry has no retained notification history.

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.

Official reporting routes
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 →
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

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 musordrop2.com)
  • 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

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
Read the evidence in context

About This Report: musordrop2.com

Stored evidence snapshot. Source timestamps appear where available.

Captured title: “Security Check”. Apparent target: Steam.

VirusTotal detections for musordrop2.com: 16 (2026-09-20 02:15:12 UTC).

Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.

Embed this report

A 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/musordrop2.com"
  title="PhishDestroy threat report for musordrop2.com"
  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>