VirusTotal
15 / 91 engine detections
Bericht öffnen“Domain Suspended”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@ifastnet.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.
bhd16usuaril.yzz.me — Letzter bekanntermaßen aktiv (HTTP 200). Betrugstyp: Impersonation. Zusammenfassung der Beweislage: VirusTotal 15/91 (BitDefender, CRDF, ESET, Forcepoint ThreatSeeker, Fortinet); URLQuery 6 alerts; Google Safe Browsing flagged; Spamhaus DBL_PHISH; PhishDestroy score 100/100. Registrar: Porkbun.
Die ausführliche Analyse von PhishDestroy AI bleibt auf Englisch, damit der ursprüngliche forensische Bericht unverändert bleibt.
15 / 91 engine detections
Bericht öffnen6 threat-system alerts
Bericht öffnenThreat flag recorded
Bericht öffnenDBL_PHISH
no community references
Bericht öffnenprovider verdict: clean
Bericht öffnen80/100
Bericht öffnenNo malicious flag
Bericht öffnenResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | suspended-domain.net |
malicious | Sinkholed |
| DigiCert UltraDNS | suspended-domain.net |
malicious | Sinkholed |
| Cloudflare DNS | bhd16usuaril.yzz.me |
malicious | Sinkholed |
| OpenDNS | bhd16usuaril.yzz.me |
phishing | Phishing Block |
| DigiCert UltraDNS | bhd16usuaril.yzz.me |
malicious | Sinkholed |
| DNS4EU | bhd16usuaril.yzz.me |
malicious | Sinkholed |
AI-assisted evidence review
bhd16usuaril.yzz.me returned HTTP status 200 in an HTTP check dated 2026-10-01, a recorded response that describes only that request. Google Safe Browsing flagged the domain for social engineering on 2026-09-30, and the publisher-owned PhishDestroy catalogue also lists it.
Google Safe Browsing recorded a social engineering flag on 2026-09-30. VirusTotal reported 15 detections across 91 scanners on 2026-09-29. The HTTP check on 2026-10-01 returned status 200, and the domain was first observed on 2026-09-17. PhishDestroy's internal listing is recorded as true. The SSL certificate was issued by ZeroSSL GmbH / ZeroSSL ECC DV SSL CA 2, scanned 2026-09-17.
The Safe Browsing flag and the PhishDestroy listing are separate source records, each with its own scope and date. The VirusTotal detection count reflects the scanners that reported on the checked date, not a shared measurement with the other sources. The HTTP 200 response on 2026-10-01 shows only that the server answered that request; it does not describe page content. Because the dates differ, the records cannot be treated as one simultaneous snapshot.
For bhd16usuaril.yzz.me, preserve the Safe Browsing flag record and the PhishDestroy listing as separate items for later comparison. Keep the VirusTotal report and the HTTP check response alongside them, since each documents a distinct observation. Compare these saved records against future checks of the same domain rather than merging them into a single judgment.
Location describes the IP network.
19fb83e20f4838b97e1e0f848817a6fec53a9c88de05d2d6d5776b0a93ec521ayzz.meSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of bhd16usuaril.yzz.me · checked Sep 17, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
alive_content: raw=ok; http=200; via=https_proxy; server=nginx
bhd16usuaril.yzz.me
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
16→17
15→16
14→15
No flag recorded→Flag recorded
Erreichbar
Threat flag recorded
View source15/91 engine detections
View sourcePD-20260917-2D5F9F
Page captured
View sourcebhd16usuaril.yzz.me
View sourcePD-20260917-2D5F9F Recipient: abuse@ifastnet.com 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 ↗
bhd16usuaril.yzz.me)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.