Stored VirusTotal result: 5/92 engines flagged. malicious: 4. suspicious: 1. Analysis time (as stored): 2026-10-06 02:02 UTC. Retrieved (as stored): 2026-10-29 01:24 UTC. Listed by external blocklists: MetaMask, SEAL. Use caution — do not enter credentials or personal information.
PhishDestroy first recorded compliance-direkt.net on 2026-07-03. Stored VirusTotal result: 5/92 engines flagged. malicious: 4. suspicious: 1. Analysis time (as stored): 2026-10-06 02:02 UTC. Retrieved (as stored): 2026-10-29 01:24 UTC. Listed by external blocklists: MetaMask, SEAL.
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@hetzner.com. 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-20260703-39628F
Current status
HTTP 200 at latest stored check
Analysis
Domain summary
PhishDestroy first recorded compliance-direkt.net on 2026-07-03. Stored VirusTotal result: 5/92 engines flagged. malicious: 4. suspicious: 1. Analysis time (as stored): 2026-10-06 02:02 UTC. Retrieved (as stored): 2026-10-29 01:24 UTC. Listed by external blocklists: MetaMask, SEAL. Risk: critical (95/100). Registrar: Hetzner Online. Status: Last known active. Hosting: HETZNER-AS Hetzner Online GmbH, DE. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.
This domain, compliance-direkt.net, is flagged for credential theft activity targeting users through impersonation of asema.de, a known corporate platform. Analysis indicates the threat actor aims to harvest login credentials, likely for unauthorized access to internal systems or financial fraud. The page title explicitly displays 'asema.de,' reinforcing the deception and increasing the likelihood of successful social engineering attacks against employees or clients of the legitimate entity. Infrastructure analysis reveals the following technical indicators: the domain was registered on June 30, 2026, through Hetzner Online GmbH, a registrar frequently abused for malicious campaigns. It resolves to the IP address 188.40.28.32, which has not been widely blocklisted at this time. VirusTotal reports 0 detections out of 95 engines, suggesting the domain has not yet been flagged by major security vendors. The SSL certificate is issued by DigiCert Inc, a legitimate provider, which may lend a false sense of security to unsuspecting users. No Google Safe Browsing (GSB) alerts or other blocklist entries were identified during the initial assessment. The domain remains active, and no takedown actions have been observed as of this analysis. The lack of detections on VirusTotal and the use of a reputable SSL certificate increase the risk of successful exploitation, particularly against users who rely on visual indicators like HTTPS or brand familiarity. Organizations are advised to block the domain at the network level and monitor for unusual login attempts or data exfiltration. Users should be educated on verifying domain authenticity, especially when prompted for credentials, and multi-factor authentication should be enforced to mitigate the impact of stolen credentials. Further monitoring of the IP address 188.40.28.32 is recommended to identify additional malicious domains that may emerge on the same infrastructure.
This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.
compliance-direkt.net targets users via credential theft, impersonating asema.de. Domain active, 0/95 VirusTotal detections, posing immediate risk to corporate.
Ai summary
This domain, compliance-direkt.net, is flagged for credential theft activity targeting users through impersonation of asema.de, a known corporate platform. Analysis indicates the threat actor aims to harvest login credentials, likely for unauthorized access to internal systems or financial fraud. The page title explicitly displays 'asema.de,' reinforcing the deception and increasing the likelihood of successful social engineering attacks against employees or clients of the legitimate entity. Infrastructure analysis reveals the following technical indicators: the domain was registered on June 30, 2026, through Hetzner Online GmbH, a registrar frequently abused for malicious campaigns. It resolves to the IP address 188.40.28.32, which has not been widely blocklisted at this time. VirusTotal reports 0 detections out of 95 engines, suggesting the domain has not yet been flagged by major security vendors. The SSL certificate is issued by DigiCert Inc, a legitimate provider, which may lend a false sense of security to unsuspecting users. No Google Safe Browsing (GSB) alerts or other blocklist entries were identified during the initial assessment. The domain remains active, and no takedown actions have been observed as of this analysis. The lack of detections on VirusTotal and the use of a reputable SSL certificate increase the risk of successful exploitation, particularly against users who rely on visual indicators like HTTPS or brand familiarity. Organizations are advised to block the domain at the network level and monitor for unusual login attempts or data exfiltration. Users should be educated on verifying domain authenticity, especially when prompted for credentials, and multi-factor authentication should be enforced to mitigate the impact of stolen credentials. Further monitoring of the IP address 188.40.28.32 is recommended to identify additional malicious domains that may emerge on the same infrastructure.
Earlier stored analysis, not reviewed; text generation time is separate from source observation dates.
Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
Collected source details
Stored page, network and scanner observations, grouped by source and observation time.
Every stored field, with its source and date
Network Security Intelligence
SSL CertificateInvalid
SSL certificate is invalid or expired. Issuer: DigiCert Inc
Questions about compliance-direkt.net
Is compliance-direkt.net legit?
PhishDestroy rates compliance-direkt.net as critical risk (95/100) from the recorded evidence; it was first recorded on 2026-07-03. Stored VirusTotal result: 5/92 engines flagged. malicious: 4. suspicious: 1. Analysis time (as stored): 2026-10-06 02:02 UTC. Retrieved (as stored): 2026-10-29 01:24 UTC. Listed by external blocklists: MetaMask, SEAL. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
Is compliance-direkt.net safe to connect a wallet?
This report does not record which wallet requests compliance-direkt.net makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.
What should I do if I used compliance-direkt.net?
It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.
Certificate fingerprintbc0e5962bf3749dad195fa3b3f387a88c847054f1b13840de54d436a4e10b4d6Certificate names · 1 SAN
your-server.de
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: Resolved
Latest HTTP observationLive contentOrdinary HTTP content served90%2026-11-17 11:19:10 UTC
RDAP registration
Observed timelinelast reachable: 2026-11-17 11:19:10 UTClast content: 2026-11-17 11:19:10 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.
Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-29 03:43 UTC.
Recorded events: 13. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Pre-emptive Discovery & IngestionThreat Ingested1/1Recorded: 1 of 1
Threat Ingested
compliance-direkt.net detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Blocklist Detection · OTX Community References · Forensic Evidence Collected · Technical Analysis Recorded · Site Came Back Online · Content Observed Unavailable10/10Recorded: 10 of 10
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+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
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.
Discovery only — Same registrar or CDN edge: listed for navigation, not evidence of a link.
Each spoke is one reason a domain is linked to this report. Node size marks VirusTotal detections, dashed nodes are already offline, and the full lists follow below. Full list of related reports
PDF notice generated Notice text archived (594 characters)
Abuse notice text as sent to the provider
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (DE):
German Criminal Code § 263 (Fraud)
German Criminal Code § 263a (Computer Fraud)
Telemedia Act (TMG)
German law prohibits fraud and computer-based deception.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
6 evidence signal groups linked1 stored notification recordsLast known active
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.
Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.
If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.
Scammers are criminals. Filing a report creates a legal record and helps protect others.
97-country directory
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.
Entered a password — change it on that service and on every other site where you used the same password
Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
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 compliance-direkt.net)
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)
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
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 →
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.