VirusTotal
2 / 89 engine detections
Bericht öffnenDomain auf Blocklisten: emanon.co — Letzter bekanntermaßen aktiv (HTTP 200). Zusammenfassung der Beweislage: VirusTotal 2/89 (Forcepoint ThreatSeeker…
Die ausführliche Analyse von PhishDestroy AI bleibt auf Englisch, damit der ursprüngliche forensische Bericht unverändert bleibt.
2 / 89 engine detections
Bericht öffnen3 community references
Bericht öffnenprovider verdict: clean
Bericht öffnenNo threat flag
Bericht öffnenResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
emanon.co is a suspicious domain on the PhishDestroy blocklist. No impersonated brand or scheme type has been confirmed for it yet. PhishDestroy first flagged the name on 2026-07-28, and as of 2026-10-19 the site was still online and serving live content. Anyone landing on it from a link, ad or direct message should treat it as untrusted.
No specific scheme has been confirmed. The risk is the usual one for flagged domains that target crypto users: a page that asks you to connect a wallet, sign a transaction, or type in a seed phrase, password or personal details. Any of these can hand an attacker control of funds or accounts. Because the site is still serving content, that risk is current, not historical.
On 2026-09-14, two of 89 VirusTotal engines, Forcepoint ThreatSeeker and SOCRadar, marked the domain as malicious. That is a thin consensus, but it comes from two vendors independent of PhishDestroy. The domain also appears in three AlienVault OTX threat pulses, so other researchers have tied it to tracked activity. PhishDestroy is currently the only blocklist carrying it, so most browser and wallet warnings will not stop a visit yet.
The timeline is unusual. PhishDestroy listed emanon.co on 2026-07-28, but the current registration through Spaceship, Inc. dates to 2026-09-01. The present registration therefore began after the name was already on our blocklist. The site resolves to Amazon.com, Inc. network space geolocated to Canada and uses a domain-validated GoDaddy certificate. That padlock only proves control of the domain and says nothing about who runs the site.
If you only browsed the site, close it and do not return. If you connected a wallet or signed anything there, treat that wallet as exposed and move remaining assets to a newly created wallet whose recovery phrase has never been typed into a website. If you entered a seed phrase, assume the wallet is compromised. If you entered a password, change it everywhere you reused it and turn on app-based two-factor authentication. Defenders should block emanon.co at DNS and proxy level, add it to email and chat link filters, and watch for repeat visits in logs, since the site remains live and few blocklists cover it.
verification-hegmxyoxv95qmrgtt3aukn.ns101.verify.hnLocation describes the IP network.
9f3e85dc8facb5b0005c85bcdaa60dc7703916a3a1cf55b1ae14e0456b7dac02Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unbekannt→live_content
content_served
Unbekannt→live_content
content_served
Unbekannt→live_content
content_served
Unbekannt→live_content
content_served
Unbekannt→live_content
content_served
Unbekannt→live_content
content_served
Unbekannt→live_content
content_served
Unbekannt→live_content
content_served
Unbekannt→live_content
content_served
Unbekannt→live_content
content_served
Unbekannt→live_content
content_served
Unbekannt→live_content
content_served
Unbekannt→live_content
content_served
Unbekannt→live_content
content_served
Unbekannt→live_content
content_served
Unbekannt→live_content
content_served
Unbekannt→live_content
content_served
0→2
Erreichbar
3 community references
View sourceNo threat flag
View source2/89 engine detections
View sourceemanon.co
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
emanon.co
Listed domains receive at least one abuse report; this entry has no retained notification history.
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.
Wählen Sie Ihr Land aus, um Offizielle Kontakte im Bereich Cyberkriminalität oder einen Beschwerdeentwurf erstellen → zu erhalten.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
emanon.co)Auch wenn dir nicht alle Details bekannt sind — trotzdem Anzeige erstatten. Auch unvollständige Informationen sind für die Ermittlungen hilfreich.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Bedrohungsanalyse anhand gespeicherter Blocklisten, WHOIS, DNS und öffentlicher Scan-Beweise
Jetzt scannenMelden Sie verdächtige Domains an unsere Bedrohungsdatenbank – schützen Sie die Community
MeldenAktuelle Phishing-Meldungen und beobachtete Verfügbarkeitsänderungen
ÜberwachenBeobachten Sie aktuelle Bedrohungen oder legen Sie Widerspruch gegen diesen Eintrag ein, wenn Sie der Meinung sind, dass es sich um einen Fehlalarm handelt
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.