Zum Sicherheitsbericht springen
Domänensicherheit und Bedrohungsinformationen
xm-signals.info favicon

xm-signals.info

“Xm-signal”

Registrar
TuringSign
Resolved IP
23.153.104.17
Registered
01.10.2025
PhishDestroy assessment Kritisch
Verfügbarkeit Inhalt nicht verfügbar Der Inhalt war in der letzten Beobachtung nicht verfügbar Beobachtet · HTTP probe
VirusTotal-Erkennungen: 6/91 Spamhaus DBL: DBL_PHISH Gespeicherte Sperrlistenübereinstimmungen: 2 URLQuery threat systems: 1 alert Automatische Markenkennung: Binance
OTX: 4 refs 11.09.2026 1 Report Sent
API
Diese Domain wurde als bösartig markiert.
Sicherheits-Engines melden eine Entdeckung: 6. Öffentliche Blocklisten, die eine Übereinstimmung melden: 2. Seien Sie äußerst vorsichtig – Geben Sie keine Anmeldeinformationen oder persönlichen Daten ein.
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 op_ct@cosmotown.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.

Elapsed since first report
1 month
Reports sent
1
Latest case ID
PD-20260911-C52A49
Current status
Observed active at latest stored check
VirusTotal
engine detections
Google Safe Browsing
URLQuery
threat alerts
OTX
community references
Page captures
open gallery
Domain age
Reports sent
view timeline
Berichtsübersicht

Binance-Imitation: xm-signals.info — Inhalt nicht verfügbar. Zusammenfassung der Beweislage: VirusTotal 6/91 (alphaMountain.ai, Forcepoint ThreatSeeker…

Die ausführliche Analyse von PhishDestroy AI bleibt auf Englisch, damit der ursprüngliche forensische Bericht unverändert bleibt.

Source evidenceVirusTotal 6 / 91 · OTX 4 references 7 sources

Spamhaus DBL

DBL_PHISH

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Erkenntnisse zur Netzwerksicherheit
Threat Detection Systems 1 alert
Detection System Indicator Verdict Alert
DNS4EU xm-signals.info malicious Sinkholed

Analysis

Kritisch
VirusTotal
6 / 91
OTX
4 community refs
Page captures
4

PhishDestroy threat report

Overview

xm-signals.info is an impersonation phishing page branded "Xm-signal". It borrows the XM name to pass as an official trading-signals offering and targets retail traders looking for copy-trade tips or premium signal packages. PhishDestroy first flagged it on 2026-09-11. On 2026-10-19 the site was still reported alive, but its content DNS was inactive, so it may come back without warning.

How the scam works

Fake signal services lure traders with screenshots of winning calls and the credibility of a recognised broker name. Victims are then pushed toward one of a few traps. They may pay a "VIP" subscription, deposit funds onto a platform the operators control, enter their real broker login on a lookalike form, or connect a crypto wallet to "activate" signals. Whatever the route, the money or account access goes to the scammers, and later requests for fees to unlock withdrawals are part of the same scheme.

Evidence

Six of 91 VirusTotal engines flagged the domain as of 2026-09-25: alphaMountain.ai, Forcepoint ThreatSeeker, Fortinet, Gridinsoft, Netcraft and SOCRadar. That count is modest, but the support comes from several independent sources. MetaMask and SEAL both list the domain alongside PhishDestroy, which means wallet users are warned at the point of connection. Spamhaus DBL classifies it as phishing, and it appears in four AlienVault OTX threat pulses.

Infrastructure

The domain was registered on 2025-10-01 through TuringSign Inc. d/b/a Cosmotown. It sat for roughly eleven months before we first detected it. That pattern fits domains bought early and held until a campaign is ready to launch. It is hosted on the Aquiryn LLC network in the United States.

What to do

If you paid a subscription or deposit here, contact your card issuer or bank immediately to dispute the charge. Do not pay any "withdrawal" or "verification" fee the operators demand. If you typed in broker or exchange credentials, change that password at once, enable app-based 2FA, and check for unfamiliar logins or transfers. Anyone who connected a crypto wallet should revoke token approvals granted during that session and move remaining funds to a fresh wallet. Defenders should block the domain at DNS and proxy level and watch for the same "Xm-signal" branding on newly registered names.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

URLScan · 2026-09-11T08:30:34Z

Beobachtet: · Retrieved:

Uuid
01a08f96-def9-7619-bf90-41578d8f7db7
Final url
https://xm-signals.info/
Status
200
Ip
23.153.104.17
Ptr
c4-17.my-control-panel.com
Contacted domains
[
    "www.youtube.com",
    "coin-images.coingecko.com",
    "fonts.gstatic.com",
    "jnn-pa.googleapis.com",
    "www.cryptocompare.com",
    "googleads.g.doubleclick.net",
    "static.getbutton.io",
    "cdn.gtranslate.net",
    "use.fontawesome.com",
    "i.ytimg.com",
    "www.google.com",
    "static.doubleclick.net",
    "widgets.cryptocompare.com",
    "api.coingecko.com",
    "fonts.googleapis.com",
    "widgets.coingecko.com",
    "code.tidio.co"
]
Contacted IP addresses
[
    "172.217.112.4",
    "104.18.30.136",
    "74.125.192.119",
    "142.251.153.119",
    "209.85.201.149",
    "172.253.122.156",
    "172.67.142.173",
    "104.26.15.221",
    "142.251.153.4",
    "20.126.215.223",
    "104.20.41.132",
    "173.194.66.94",
    "209.85.201.95",
    "104.18.4.118",
    "104.26.13.42"
]
Asns
[
    "15169",
    "13335",
    "8075",
    "32561"
]
Countries
[
    "US",
    "NL"
]
Linked domains
[
    "www.blockchain.com",
    "www.cryptocompare.com",
    "wa.me",
    "getbutton.io"
]
Social
[
    "https://wa.me/27603652404"
]
Document hash
47c84a77d1965bbd5bcef25434b817a70f10952d45697226d0d145cb18850638
Script hashes
[
    "160a426ff2894252cd7cebbdd6d6b7da8fcd319c65b70468f10b6690c45d02ef",
    "587c080125b135d29a931ed371e50ffc1a9641831c1087de2cd74532815f4560",
    "eb795deda8983fa5310627c9584cf3f3b95d272567113500059018b3941cb267",
    "23fc25133ed072cdf7dae575213067b1da3c6843b2a0e489c8b7fc984c60ce6b",
    "1fd8c0cfffd02e40cecbf9f313d1b86988a342d90bb7d16f1a67544f0064ea0b",
    "f2beb92898142c10e2661c03c9d7d6ac4931df2c95fe0ac6b06cda7a4a1b9e02",
    "96abf166b3cbb5f7df525d86fdeeeccea4af3c120b19bc26b0613530a94e8b44",
    "186e4c2c470e3c1c76997b7a4dfd0f618b38311582e0578db05ccada6fd43c6c",
    "f5118c2117300dcd406002417f201608dc046ee26b0680d4c1c93ecd01d7cc2d"
]
Globals
[
    "$",
    "jQuery",
    "Popper",
    "bootstrap",
    "moment",
    "EvEmitter",
    "imagesLoaded",
    "gtranslateSettings",
    "__core-js_shared__",
    "core",
    "nav",
    "functionConfirm",
    "scripts",
    "embedder",
    "baseUrl",
    "doGTranslate",
    "setImmediate",
    "clearImmediate",
    "GBBTN",
    "WhWidgetSendButton",
    "fabric",
    "saveAs",
    "XLSX",
    "XLS",
    "cccCurrentTheme",
    "cccCreateCSSSelector",
    "cccglobal_data",
    "cccupdating",
    "cccloading_counter",
    "cccfsym",
    "ccctsym",
    "cccscale",
    "ccclimit",
    "cccperiod",
    "cccaggregate",
    "cccminPeriod",
    "cccforceAll",
    "cccchart_type",
    "chartBTC",
    "colors"
]
Cookies
[
    "XSRF-TOKEN",
    "xm_signals_session",
    "__Secure-YNID",
    "YSC",
    "VISITOR_INFO1_LIVE",
    "VISITOR_PRIVACY_METADATA",
    "__Secure-ROLLOUT_TOKEN",
    "__cf_bm"
]
Tls
{
    "san": [
        "*.xm-signals.info",
        "xm-signals.info"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YR1",
    "subject": "*.xm-signals.info",
    "protocol": "TLS 1.3",
    "valid_to": "2026-11-03T07:15:27Z",
    "valid_from": "2026-08-05T07:15:28Z"
}
Domain age days
344
Apex age days
344
Tls age days
37
Tls valid days
89
Requests
77
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 99,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "LiteSpeed",
    "content-type": "text/html; charset=UTF-8"
}
Cloudflare Radar · 2026-09-11T09:03:53Z

Beobachtet: · Retrieved:

Uuid
f85ace2c-9c5d-4850-93d3-f1d87e8150f2
Final url
https://xm-signals.info/
Status
200
History
[
    {
        "url": "https://xm-signals.info/",
        "status": 200
    }
]
DOM structure hash
bda6616060ca5cd35f1fbf6c7906c9ed8677e304707a22bc7e390aa5f32174bb
Document hash
38e73be4e704bf8555f581ea7c161bc570d797d3ed1ffaf72da246d5eed54db3
Phishing v2
[
    "phishing"
]
Url risks
[
    "Scam"
]
Domain risks
[
    "Scam",
    "Security threats",
    "CIPA Filter",
    "CIPA",
    "Brokerage & Investing",
    "Business & Economy"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "xm-signals.info",
        "type": "A",
        "value": "23.153.104.17"
    }
]
Dnssec valid
false
Ip
23.153.104.17
Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask Gelistet View source
PhishDestroy PhishDestroy list View source
SEAL Gelistet View source

Last checked

Gespeicherte Aufnahme · 4 captures

Domain details

Domain
URLScan verdict Analyse abgeschlossen score 0 report ↗
IP-Reputation abuse score 2/100 3 reports PhishingBad Web Bot checked 11.10.2026
OTX tags 2026-09activeall-domainsblocklistcontentcryptoDomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar TuringSign (Unknown)
ICANN-RegistrierungsstelleICANN Lookup (RDAP) →
RegistrierungErstellt 01.10.2025 — Expires 01.10.2026
Technische DetailsProvenance & timestamps
Erstmals entdeckt11.09.2026
DOM Analysisanalyzed 11.09.2026score 95/1005 brand signals
Submitted URLhttps://xm-signals.info/
Favicon Hash
Fall-ID
Observed page title
Xm-signal
Automated brand references
Binance Coinbase Ethereum Kraken Signal
TLS-Zertifikat
Ausgestellt von YR1 · stored validity ends in 12 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
23.153.104.17
Network ASN
AS32561
Organization
Aquiryn LLC
Observed location
Sheridan, US
Server header
LiteSpeed

Nameserver 2

  • ns7.my-control-panel.com
  • ns8.my-control-panel.com

Mail routing 1 MX record

  • xm-signals.infopriority 0

Location describes the IP network.

TLS-Zertifikat

Issuer
YR1
Valid from
2026-08-05 07:15:28
Valid until
2026-11-03 07:15:27
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-10-20 16:02:21 UTC
Collection source
PhishDestroy collector
Certificate names · 2 SANs
  • *.xm-signals.info
  • xm-signals.info

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-21 14:53:36 UTC

Primary outcome DNS inaktiv reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Unbekannt Probe Inconclusive 20% 2026-10-21 10:07:02 UTC
RDAP registration Unbekannt
Observed timeline last reachable: 2026-10-01 22:00:33 UTC last content: 2026-10-01 22:00:33 UTC current episode first observed: 2026-10-02 16:16:28 UTC observed RIP window: 2026-10-01 22:00:33 UTC → 2026-10-02 16:16:28 UTC · 18.27h midpoint estimate ≈ 2026-10-02 07:08:30 UTC · precision medium · basis bounded
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.
Technologien · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Diese Domain melden Reichen Sie Beweismaterial ein und helfen Sie mit, andere zu schützen

VirusTotal-Analyse

6 / 91 Sicherheitsanbieter haben diese Domain markiert
View on VT
Last analyzed First positive detection Previous stored snapshot: 6 detections
alphaMountain.ai
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
Netcraft
SOCRadar

Archivierte Beweise

Wayback Machine Snapshot
Zur Beweisüberprüfung steht ein historischer Schnappschuss zur Verfügung
View Archive
Website-Performanceanalyse

Google PageSpeed Insights — mobile performance audit of xm-signals.info · checked Sep 11, 2026

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

Availability observations

Last reachable observation
Last content observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
18.27
Estimate basis
Bounded by observations
Estimate precision
Mittel

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

Check for cloaking

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

xm-signals.info
Gespeichertes Ergebnis
Cloaked / Filtered
Stored observation history21

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

    Unbekannt→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Unbekannt→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Unbekannt→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Unbekannt→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    Unbekannt→dns_inactive

    dns_nxdomain

Earlier observations 16
  1. Availability monitor · Recorded state

    Unbekannt→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Unbekannt→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Unbekannt→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Unbekannt→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    Unbekannt→dns_inactive

    dns_nxdomain

  6. Availability monitor · Recorded state

    Unbekannt→dns_inactive

    dns_nxdomain

  7. Availability monitor · Recorded state

    Unbekannt→dns_inactive

    dns_nxdomain

  8. Availability monitor · Recorded state

    Unbekannt→dns_inactive

    dns_nxdomain

  9. Availability monitor · Recorded state

    Unbekannt→dns_inactive

    dns_nxdomain

  10. Availability monitor · Recorded state

    Unbekannt→dns_inactive

    dns_nxdomain

  11. Availability monitor · Recorded state

    Unbekannt→dns_inactive

    dns_nxdomain

  12. Availability monitor · Recorded state

    Unbekannt→dns_inactive

    dns_nxdomain

  13. Availability monitor · Recorded state

    Unbekannt→live_content

    content_served

  14. Availability monitor · Recorded state

    Unbekannt→live_content

    content_served

  15. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

  16. Availability monitor · First collection record

    Erreichbar

Recorded activity

6 entries
  1. AlienVault OTX

    4 community references

    View source
  2. VirusTotal

    6/91 engine detections

    View source
  3. Google Safe Browsing

    No threat flag

    View source
  4. Abuse report sent

    PD-20260911-C52A49

    op_ct@cosmotown.com
  5. Added to PhishDestroy

    xm-signals.info

    View source
  6. URLScan

    Page captured

    View source

Ähnliche Domains

187 gespeicherte ähnliche Domains

Alle anzeigen (88)
binabce.com replacement binacne.com transposition binan.ce.com subdomain binancecom.com various binanci.com vowel-swap binanco.com vowel-swap binancr.com replacement binancs.com replacement binancw.com replacement binande.com replacement binanfe.com replacement binanve.com replacement binanxe.com replacement binnace.com transposition binonce.com vowel-swap binsnce.com replacement binunce.com vowel-swap binynce.com replacement binznce.com replacement bniance.com transposition bunance.com replacement ibnance.com transposition ninance.com replacement b-inance.com hyphenation b8inance.com insertion b8nance.com replacement b9nance.com replacement bbinance.com repetition bhinance.com insertion bi-nance.com hyphenation biance.com omission bibance.com replacement bibnance.com insertion bihance.com replacement bihnance.com insertion biinance.com repetition bijnance.com insertion biknance.com insertion bimance.com homoglyph bimnance.com insertion bin-ance.com hyphenation binaance.com repetition binabnce.com insertion binace.com omission binahce.com replacement binamnce.com insertion binan-ce.com hyphenation binanbce.com insertion binanc-e.com hyphenation binanc.com omission binanc3.com replacement binancce.com repetition binancve.com insertion binancxe.com insertion binancz.com replacement binandce.com insertion binane.com omission binanec.com homoglyph binanhce.com insertion binanmce.com insertion binannce.com homoglyph binanvce.com insertion binanxce.com insertion binarnce.com homoglyph binasnce.com insertion binawnce.com insertion binbance.com insertion binhance.com insertion binmance.com insertion binnance.com homoglyph binnce.com omission binqance.com insertion binsance.com insertion binwnce.com replacement binyance.com insertion bionance.com insertion birnance.com homoglyph biunance.com insertion bjnance.com replacement bnance.com omission bninance.com insertion boinance.com insertion bonance.com replacement buinance.com insertion bvinance.com insertion clinance.com homoglyph dinarce.com homoglyph ginance.com replacement

100 von 187 angezeigt

Community-Meldungen

Von 1 Community-Mitglied gemeldet; erstmals gesehen am 06.12.2025

Gespeicherte Meldungen
1
Eindeutige gemeldete URLs
1
Abgelehnt1

Nachweise und externe Berichte

Momentaufnahme der übermittelten Beweise
Sent: Ledger records: 1 Case ID: PD-20260911-C52A49 Recipient: op_ct@cosmotown.com
Page title stored with report: New Private Tab
PDF notice generated
Eingehende Analyse
Help & reporting

Wurden Sie von dieser Website betroffen?

6 evidence signal groups linked 1 stored notification records Inhalt nicht verfügbar
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Wenn Sie Kontoanmeldeinformationen, persönliche oder Zahlungsinformationen eingegeben oder eine Datei von dieser Domain heruntergeladen haben, ergreifen Sie sofort Maßnahmen. Nachfolgend finden Sie Ressourcen, die Ihnen helfen, den Vorfall zu melden und sich zu schützen.

Official reporting routes

Vorsicht vor Betrügern, die mit der Rückforderung von Geldern locken! Kriminelle nehmen unter Umständen erneut Kontakt zu Opfern auf und geben dabei vor, Ermittler, Anwälte oder Beitreibungsbeamte zu sein. Zahlen Sie keine Vorabgebühren und geben Sie keine Anmeldeinformationen weiter. Erfahren Sie mehr über Betrug im Zusammenhang mit Wiederaufbaumaßnahmen →

Melden Sie sich bei Ihren örtlichen Behörden

Wählen Sie Ihr Land aus, um Offizielle Kontakte im Bereich Cyberkriminalität oder einen Beschwerdeentwurf erstellen → zu erhalten.

97-Länder-Verzeichnis

Template-based draft · optional AI wording assistance requires separate consent

KI-gestützter Entwurf – Vorfalldetails werden vom KI-Anbieter verarbeitet · Überprüfen Sie es und reichen Sie es selbst ein
After a phishing incident

Empfehlungen und Ratschläge für Betroffene

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

Was soll ich sofort tun?

Dringend

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Alle Passwörter ändern — E-Mail, Exchange-Konten, alles, wofür dasselbe Passwort verwendet wird
  • 2FA aktivieren mit einer Authentifizierungs-App (nicht per SMS). Deaktivieren Sie die SMS-basierte Wiederherstellung
  • Karten einfrieren Falls Sie auf der Phishing-Seite Ihre Bankdaten eingegeben haben

Welche Informationen sollte ich für meinen Bericht sammeln?

FBI-Richtlinien

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.
  • Genaue Daten und Uhrzeiten — jeder Transaktion und des ersten Kontakts mit dem Betrüger
  • Screenshots — betrügerische Websites, Chat-Nachrichten, E-Mails, Wallet-Transaktionen, soziale Medien
  • Alle URLs und Domains die der Betrüger verwendet (einschließlich xm-signals.info)
  • Kommunikation — E-Mails, SMS, Telefonnummern, Benutzernamen, die der Betrüger verwendet hat

Auch wenn dir nicht alle Details bekannt sind — trotzdem Anzeige erstatten. Auch unvollständige Informationen sind für die Ermittlungen hilfreich.

Wo soll ich den Betrugsfall melden?

  • FBI IC3 — Internet Crime Complaint Center (Meldestelle der US-Bundesbehörden)
  • Europol — Meldungen zu Cyberkriminalität in Europa (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Ortspolizei — sorgt für eine offizielle Dokumentation, auch wenn sie nicht sofort handeln können

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?

  • Gefälschte Websites — pixelgenaue Kopien legitimer Websites mit leicht abgeänderten Domains
  • Schweineschlachtung — über Wochen hinweg über Telegram, WhatsApp und Dating-Apps aufgebautes Vertrauen, dann wurde Geld gestohlen
  • Betrugsmaschen im Zusammenhang mit der Rückforderung von Geldern — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Durch KI gestützte Betrugsmaschen — Deepfakes, automatisiertes Phishing und KI-generierte Websites, die es erschweren, Betrugsversuche zu erkennen

Wie kann ich mich in Zukunft schützen?

  • Offizielle Websites als Lesezeichen speichern — Klicken Sie niemals auf Links in E-Mails, Direktnachrichten oder Anzeigen
  • Domains überprüfen — nachsehen, ob PhishDestroy Bevor Sie Kontakt aufnehmen: Überprüfen Sie HTTPS, die Rechtschreibung und das Alter der Domain.
  • „Zu schön, um wahr zu sein“ = Betrug — garantierte Renditen, Prominente als Werbeträger, dringende Fristen

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Bleiben Sie auf dem Laufenden, bleiben Sie sicher

Beobachten Sie aktuelle Bedrohungen oder legen Sie Widerspruch gegen diesen Eintrag ein, wenn Sie der Meinung sind, dass es sich um einen Fehlalarm handelt

Echtzeit-Bedrohungsfeed Einspruch gegen diesen Eintrag einlegen
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Diesen Bericht einbetten

Teilen Sie diese Bedrohungsinformationen auf Ihrer Website oder in Ihrem Blog

embed.html
<iframe
  src="https://phishdestroy.io/de/embed/domain/xm-signals.info"
  title="PhishDestroy threat report for xm-signals.info"
  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>