Skip to security report
Analytics Dashboard
Domain security report
amberyak.buzz favicon

amberyak.buzz

“QUANTUM AI TRADING”

Threat verdict
CriticalDomain Appeal
Assessment sources

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

Availability Reachable · access restricted Reachable response; page content was not verified Observed · HTTP probe
Risk signals
VirusTotal detections: 19/91 URLQuery threat systems: 5 alerts Scam type: Crypto Scam Last known active
OTX: 17 refs May 31, 2026 1 Report Sent
API
Registrar
GoDaddy
Resolved IP
198.105.126.181
Registered
May 2, 2026
3 sources
The capture source is temporarily unavailable.
1 / 3
Source
Primary capture
Collected · UTC
Open capture
In this reportGet help
This domain has been flagged as malicious
Security engines reporting a detection: 19. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@syn.one. The latest stored availability evidence still shows the domain reachable; 4 months 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.

Elapsed since first report
4 months
Reports sent
1
Latest case ID
PD-20260531-168A2C
Current status
HTTP 403 at latest stored check

Additional indicators at a glance

VirusTotal
VirusTotal
19 det.
URLQuery
URLQuery
5 threat alerts
OTX references
17 community refs
CF Radar
Malicious
URLScan
URLScan
Report ↗
TLS Certificate
Within stored validity dates
Let's Encrypt / YR2 · Hostname coverage not recorded
Age
6 mo
Observed status
Reachable · access restricted 403
PhishDestroy
DestroyList
Listed
Reports Sent
1

Source evidence

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

19 / 91

Report
Interpretation & limits

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

URLQuery

5 threat-system alerts

Report
Interpretation & limits

Alerts refer to the preserved scan. They do not describe the current state of the site.

CF Radar

provider verdict: malicious

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.

OTX

17 community references

Report
Interpretation & limits

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

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.

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.

Public blocklists

0 external matches

Details
Interpretation & limits

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

Network Security Intelligence
Threat Detection Systems 5 alerts
Detection System Indicator Verdict Alert
DigiCert UltraDNS amberyak.buzz malicious Sinkholed
OpenDNS amberyak.buzz phishing Phishing Block
DNS4EU amberyak.buzz malicious Sinkholed
Quad9 DNS amberyak.buzz malicious Sinkholed
Cloudflare DNS amberyak.buzz malicious Sinkholed
Stored URLQuery scan evidence · May 31, 2026 11:25 UTC Open source report
CF Cloudflare Radar Verdict Malicious
Phishing
View full Cloudflare Radar report

Evidence Summary

Critical
VirusTotal
19/91
OTX
17 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.

This domain is flagged as a high-risk crypto scam operating under the title QUANTUM AI TRADING. Analysis confirms the domain was registered on May 02, 2026 through GoDaddy.com, LLC, and utilizes nameservers ns67.domaincontrol.com and ns68.domaincontrol.com. The site resolves to IP 198.105.126.181, hosted by AS149440 Evoxt Sdn. Bhd. in the United States, with infrastructure leveraging Nginx, HTTP/3, Cloudflare Browser Insights, HSTS, Google Analytics, and a Facebook Pixel. An SSL certificate from Let's Encrypt / R12 is present. Security telemetry is strong: 23 out of 91 security vendors on VirusTotal flag this domain as malicious, and it appears on at least one security blocklist. The Gridinsoft trust score is 0/100, indicating a complete lack of trustworthiness. The domain is currently active and has been blocked by PhishDestroy. For defenders, this domain should be added to blocklists immediately. Investigate the deployment of tracking scripts (Google Analytics, Facebook Pixel) for potential attribution to the threat actor. Monitor the IP 198.105.126.181 and associated AS149440 for related infrastructure. The exact phishing mechanism on the site is not yet analyzed, but the combination of a zero-trust score, high vendor detection rate, and crypto scam classification makes this a confirmed threat requiring no further confirmation before blocking.

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
19 / 91 · engine detections
URLScan analysis
Automated verdict retained
URLQuery
5 · recorded detections / alerts
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
17 · community references
External blocklists
0 · external matches
Cloudflare Radar
maliciousCollection time not recorded
Spamhaus DBL
Collection time retained; verdict missing
Domain registration
GoDaddy.com, LLCCollection time not recorded
Network & DNS
198.105.126.181 · 1 · nameserversCollection time not recorded
TLS certificate
Let's Encrypt / YR2
Page captures
3 · retained captures
Page analysis
0 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
PageSpeed performance
92/100 · mobile performance
Response records
1 · outgoing report records
Availability history
31 · stored state changes
Community reports
Aggregate report counts and dates
IP reputation
Network-level observations
Not recorded in this report 11

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

  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • HTML archives
  • Site configuration files
  • Recorded subdomains
  • Source observation history
  • Lookalike relationships
  • Chainabuse records
  • Wayback archive
Download the dated observations and supporting metadata.

Blocklist records

0 · external source matches

Public Blocklist Status

Domain, network & archive

GoDaddy.com, LLC · 198.105.126.181 · DNS, TLS and retained responses

Domain details

Domain
IP Reputation abuse score 0/100 0 reports checked Oct 11, 2026
OTX tags 2026-05activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar GoDaddy (Unknown)
Abuse contactabuse@syn.one
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for amberyak.buzz →
RegistrationCreated May 2, 2026 (168d) — Expires May 2, 2027
HTTP Status403 Forbidden
Technical detailsProvenance & timestamps
First DetectedMay 31, 2026
DOM Analysisanalyzed May 31, 2026score 98/100
Submitted URLhttp://amberyak.buzz/
Case ID
SHORTDOT ZONE · PUBLIC EVIDENCE .buzz

ShortDot zone evidence

The linked repository preserves daily zone observations across seven ShortDot-operated TLDs, including registration volume and abuse-related indicators. This registry context is supporting background and is not an independent detection for the domain in this report.

ShortDot SA · Luxembourg 7 zones · full-zone evidence updated daily Open the ShortDot evidence repository
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

Resolved IP
198.105.126.181
Network ASN
AS149440
Organization
Evoxt Sdn. Bhd.
Observed location
Los Angeles, US
Server header
nginx
Nameservers 1
  • ns68.domaincontrol.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR2
Valid from
2026-09-01 19:05:05
Valid until
2026-11-30 19:05:04
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-10-10 04:03:30 UTC
Collection source
PhishDestroy collector
Certificate fingerprintb6588db1b1ed5f3a968ce09e7d67ff31238193734104433b4b91e7e3120f28a3

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

viewdns.info · 198.105.126.181rapiddns.io

Latest Classified Outcome 2026-10-17 10:19:54 UTC

Primary outcome Reachable but protected reason: HTTP access restricted 50% confidence
Attribution mechanism: Access Restriction source: Current Http Probe
Evidence layers Availability: Reachable but protected Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Reachable but protected HTTP access restricted Access Restriction 50% 2026-10-17 10:19:54 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-17 10:19:54 UTC last content: 2026-10-13 22:29:22 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 · 6 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

19 / 91 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 24 detections
Criminal IP
alphaMountain.ai
BitDefender
Chong Lua Dao
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
LevelBlue
Lionic
Netcraft
SafeToOpen
Seclookup
Sophos
VIPRE
Webroot
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of amberyak.buzz · checked May 31, 2026

92
Good
Performance
FCP
1.38s
First Contentful Paint
LCP
2.31s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
268ms
Total Blocking Time
SI
3.05s
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 suspected: scanner and visitor titles differ

Not observed No cloaking was observed in the stored scan

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

Stored cloaking flag
Not observed
Cloaking score
0/6
Last cloaking scan
Server header seen by scanner
nginx

Scanner note: alive_content: raw=content_403; http=403; via=https_proxy; server=nginx

Title shown to the security scanner403 Forbidden
Title shown to a browser visitorQUANTUM AI TRADING
Live TDS fingerprint check
Seven Keitaro fingerprints and a browser-versus-crawler comparison. A new scan starts only when you press the button.
Saved result
Cloaked / Filtered

Timeline & response

1 · outbound report records

Stored observation history31

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→protected

    http_access_restricted · access_restriction

  2. Availability monitor · Recorded state

    protected→Unknown

    probe_inconclusive

  3. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · access_restriction

  4. Availability monitor · Recorded state

    protected→Unknown

    probe_inconclusive

  5. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · access_restriction

Earlier observations 26
  1. Availability monitor · Recorded state

    protected→Unknown

    probe_inconclusive

  2. Availability monitor · Recorded state

    live_content→protected

    http_access_restricted · access_restriction

  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

  6. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  7. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  8. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  9. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  10. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  11. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  12. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  13. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  14. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  15. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  16. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  17. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  18. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  19. Availability monitor · Recorded state

    live_content→Unknown

    stale_current_evidence

  20. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  21. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  22. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  23. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  24. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  25. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  26. Availability monitor · Recorded state

    Unknown

    probe_inconclusive

Threat Response Pipeline

Discovery
Analysis
Notifications
Monitoring

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

Threat Ingested
amberyak.buzz detected and queued for full analysis
May 31, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Jun 23, 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.
VirusTotal
19/91 recorded on VirusTotal
Sep 28, 2026
OTX Community References
17 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
Oct 3, 2026
CF Radar: Malicious
Cloudflare Radar classified this domain as phishing
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
Jun 23, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 17, 2026
Sent Report Recorded
Stored outgoing record associated with registrar GoDaddy.com, LLC, 1 abuse contact
abuse@syn.one
May 31, 2026
DestroyList Published
Listed in the public PhishDestroy/DestroyList repository
May 31, 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.

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

Related infrastructure

Shared hosting, registrar records and related domains

Community records

Retained community reports and observations

Community reports

Reported by 1 community member, first seen May 31, 2026

Stored reports
1
Unique reported URLs
1
Accepted1

Evidence & investigation tools

Original reports, independent checks and evidence links

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 19 det. ChainPatrol URLQuery 5 threat alerts SSL Labs Hostname coverage not recorded CF Radar Malicious OTX 17 refs WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20260531-168A2C Recipient: abuse@syn.one
Page title stored with report: QUANTUM AI TRADING
PDF notice generated Notice text archived (1,180 chars)
Abuse notice text as sent to the provider 
Policy Violations:
Acceptable Use Policy (AUP): The domain amberyak.buzz is engaged in phishing activities, which directly contravenes the AUP's prohibition against illegal activities, fraud, and deception.
Terms of Service (TOS): The continued operation of this domain constitutes a violation of the TOS, which reserves the right to suspend or terminate services for any actions that facilitate fraudulent activities.
Applicable Laws (Unknown):
Computer Fraud and Abuse Act (CFAA): This U.S. law prohibits unauthorized access to computers and the exploitation of such access for fraudulent purposes.
Wire Fraud Statute (18 U.S.C. § 1343): This law criminalizes schemes to defraud individuals or entities using electronic communications, which includes phishing schemes.
Anti-Phishing Act of 2004: This legislation specifically targets phishing and related fraudulent activities, making it illegal to use deceptive means to solicit sensitive information.
Regulatory Note: Failure to act on this report may expose your organization to legal liability and regulatory scrutiny. Immediate action is recommended to mitigate potential risks associated with hosting this phishing domain.
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

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Were You Affected by This Site?

6 evidence signal groups linked 1 stored notification records Reachable · access restricted
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
PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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 amberyak.buzz)
  • 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

Live Threat Feed Appeal This Listing
Read the evidence in context

About This Report: amberyak.buzz

Stored evidence snapshot. Source timestamps appear where available.

Captured title: “QUANTUM AI TRADING”.

VirusTotal detections for amberyak.buzz: 19 (2026-09-28 02:29:33 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.

submit an appeal or review the FAQ page.

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/amberyak.buzz"
  title="PhishDestroy threat report for amberyak.buzz"
  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>