Zum Sicherheitsbericht springen
Analytics-Dashboard
Domänensicherheit und Bedrohungsinformationen
kapithaven.digital favicon

kapithaven.digital

“KapitHaven | AI Trading Platform | Authorized Web Resource”

Registrar
NETIM SAS
Resolved IP
188.114.96.3
Registered
22.07.2026
PhishDestroy assessment Kritisch
Verfügbarkeit Letzter bekanntermaßen aktiv Letzte gespeicherte Erreichbarkeitsbeobachtung Beobachtet · HTTP probe
Risikosignale
VirusTotal-Erkennungen: 15/89 URLQuery threat systems: 4 alerts Betrugstyp: Fake Exchange
OTX: 5 refs 14.09.2026 1 Report Sent CDN
API
Diese Domain wurde als bösartig markiert.
Sicherheits-Engines melden eine Entdeckung: 15. 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 abuse@netim.net. 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-20260914-596E14
Current status
HTTP 200 at latest stored check
VirusTotal
15 / 89
engine detections
Google Safe Browsing
No threat flag
URLQuery
4
threat alerts
OTX
5
community references
Page captures
7
open gallery
Domain age
91 days
Reports sent
1
view timeline
Berichtsübersicht

Phishing: kapithaven.digital — Letzter bekanntermaßen aktiv (HTTP 200). Zusammenfassung der Beweislage: VirusTotal 15/89 (alphaMountain.ai, BitDefender, Chong…

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

Source evidenceVirusTotal 15 / 89 · OTX 5 references 6 sources

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

Erkenntnisse zur Netzwerksicherheit
Threat Detection Systems 4 alerts
Detection System Indicator Verdict Alert
Quad9 DNS kapithaven.digital malicious Sinkholed
DNS4EU kapithaven.digital malicious Sinkholed
DigiCert UltraDNS kapithaven.digital malicious Sinkholed
Cloudflare DNS kapithaven.digital malicious Sinkholed
Stored URLQuery scan evidence · Sep 14, 2026 18:41 UTC Open source report
CF Cloudflare Radar Verdict Schädlich
Malware
View full Cloudflare Radar report

Analysis

Kritisch
VirusTotal
15 / 89
OTX
5 community refs
Page captures
7
Page captures Source results Registration record

PhishDestroy threat report

Overview

kapithaven.digital operates as a fraudulent cryptocurrency trading platform under the KapitHaven brand, targeting retail investors seeking automated or AI-assisted trading returns. PhishDestroy first identified it on 2026-09-14, and it remains fully live with active content as of 2026-10-19. The site carries no legitimate regulatory standing and exists to defraud users who deposit funds expecting genuine trading activity.

How the scam works

Fake exchange platforms like KapitHaven draw victims in with polished dashboards, promises of AI-driven profits, and fabricated account balances that appear to grow over time. The page title — 'KapitHaven | AI Trading Platform | Authorized Web Resource' — is consistent with this approach, projecting legitimacy to lower a visitor's guard. When a user attempts to withdraw, the platform typically blocks the request or demands additional fees, taxes, or identity verification payments that never result in a real payout. Every deposit goes directly to the fraudsters.

Evidence

Fifteen of 89 engines on VirusTotal flagged this domain as malicious as of 2026-09-24, with detections from BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, CRDF, CyRadar, alphaMountain.ai, and Chong Lua Dao, among others. The domain appears on the PhishDestroy blocklist and has generated five independent threat intelligence pulses on OTX, confirming it has been corroborated across multiple research communities.

Infrastructure

The domain was registered on 2026-07-22 through NETIM SAS, less than two months before PhishDestroy first flagged it. It runs behind Cloudflare infrastructure on an IP geolocated to Canada, with a TLS certificate issued by Google Trust Services under the WE1 intermediate. This combination of CDN-based hosting and an automated certificate keeps the operator's true location obscured.

What to do

If you deposited funds on this platform, treat them as unrecoverable and do not send further money in response to any withdrawal fee or verification demand. Report the fraud to your national financial regulator and contact your bank or card provider immediately to explore a chargeback or payment recall. Security teams should block kapithaven.digital at the DNS and firewall level and notify any users who accessed it on managed networks.

Useful links

urlscan.io scan and screenshotVirusTotal reportGoogle Safe Browsing statusArchived copyToken-Genehmigungen widerrufenReport crypto fraud (Chainabuse)Report phishing to GoogleSite owner? Request a review

Collected source details

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

URLScan · 2026-09-14T18:37:07Z

Beobachtet: · Retrieved:

Uuid
01a0a135-4f14-73da-8d8f-43488021a21b
Final url
https://kapithaven.digital/
Status
200
Weitergeleitet
https-only
Redirects
[
    {
        "to": "https://kapithaven.digital/",
        "from": "http://kapithaven.digital/",
        "status": 307
    }
]
Ip
2a06:98c1:3121::3
Contacted domains
[
    "cdnjs.cloudflare.com",
    "fonts.gstatic.com",
    "cdn.jsdelivr.net",
    "fonts.googleapis.com",
    "static.cloudflare.com"
]
Contacted IP addresses
[
    "142.251.20.94",
    "2606:4700::6811:cf05",
    "188.114.96.3",
    "2a00:1450:4001:c0f::5f",
    "104.17.25.14",
    "2a06:98c1:3121::3"
]
Asns
[
    "15169",
    "13335"
]
Countries
[
    "US",
    "DE"
]
Document hash
674424f521176f61ff4984392abd6ecfc178a623f2b86b433c6ffd6d77d9e239
Script hashes
[
    "ccf00d1923b0131a10e0c6d26f95e5dee6ebf8621a27e83c5a2f68a2e0093142"
]
Globals
[
    "LANG_MSGS",
    "ClientJS",
    "_q9cd5v",
    "toggleTermsPopup",
    "__cfQR",
    "__cfRLUnblockHandlers",
    "__lgT0"
]
Cookies
[
    "entry_url"
]
Tls
{
    "san": [
        "kapithaven.digital"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE1",
    "subject": "kapithaven.digital",
    "protocol": "TLS 1.3",
    "valid_to": "2026-10-29T01:05:18Z",
    "valid_from": "2026-07-31T00:05:22Z"
}
Domain age days
54
Apex age days
54
Tls age days
45
Tls valid days
90
Requests
20
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 99,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=utf-8",
    "strict-transport-security": "max-age=31536000; includeSubDomains; preload",
    "content-security-policy": "script-src 'self' 'unsafe-inline' 'unsafe-eval' https://static.cloudflare.com https://cdn.jsdelivr.net; connect-src 'self' https://cloudflareinsights.com; style-src 'self' 'unsafe-inline' https://font",
    "x-frame-options": "SAMEORIGIN",
    "x-content-type-options": "nosniff",
    "referrer-policy": "no-referrer-when-downgrade",
    "permissions-policy": "camera=(), microphone=(), geolocation=()",
    "cross-origin-opener-policy": "same-origin"
}
Cloudflare Radar · 2026-09-14T18:39:30Z

Beobachtet: · Retrieved:

Uuid
aabb325f-8187-4ded-8482-23aab5b3ecd8
Final url
https://kapithaven.digital/
Status
200
History
[
    {
        "url": "https://kapithaven.digital/",
        "status": 200
    }
]
DOM structure hash
e68cca8f8f7bf2db3ead28aeb438076c5bc0c03936bba305f948380d13f82b9a
Document hash
01ced3281bf2a39ccb6dfccf0f34eff791b7f4960a1f99f59e81ab14600560f8
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Malware",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "kapithaven.digital",
        "type": "A",
        "value": "188.114.96.0"
    },
    {
        "name": "kapithaven.digital",
        "type": "A",
        "value": "188.114.97.0"
    },
    {
        "name": "kapithaven.digital",
        "type": "AAAA",
        "value": "2a06:98c1:3121::"
    },
    {
        "name": "kapithaven.digital",
        "type": "AAAA",
        "value": "2a06:98c1:3120::"
    }
]
Dnssec valid
false
Ip
188.114.96.0
Verdict
{
    "tags": [
        "malware"
    ],
    "malicious": true,
    "categories": [
        "malware"
    ]
}
Registration record
{
    "registrar": "NETIM SAS",
    "created": "2026-07-22T14:46:36Z",
    "updated": "2026-08-12T02:08:52Z",
    "expires": "2027-07-22T14:46:36Z",
    "nameservers": [
        "monika.ns.cloudflare.com",
        "razvan.ns.cloudflare.com"
    ]
}
Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Gespeicherte Aufnahme · 7 captures

Primary capture 1 / 7
QuellePrimary capture
Recorded2026-09-14 18:38 UTC
StateStored capture
Position1 / 7
Open capture Wayback Herunterladen
Observed page title
KapitHaven | AI Trading Platform | Authorized Web Resource
Automated brand references
Across
TLS-Zertifikat
Ausgestellt von Google Trust Services / WE1 · stored validity ends in 65 days

Domain details

Domain
URLScan verdict Analyse abgeschlossen score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Die Edge-IP-Reputation wird dieser Domäne nicht zugeordnet.
OTX tags 2026-09activeall-domainsblocklistcontentcryptoDomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar NETIM SAS (Unknown)
Abuse-Kontaktabuse@netim.net
ICANN-RegistrierungsstelleICANN Lookup (RDAP) →
WHOIS-AbfrageICANN RDAP für kapithaven.digital →
RegistrierungErstellt 22.07.2026 (91d) — Expires 22.07.2027
HTTP-Status200
Technische DetailsProvenance & timestamps
Erstmals entdeckt14.09.2026
DOM Analysisanalyzed 15.09.2026score 98/1001 brand signal
Submitted URLhttp://kapithaven.digital/
Favicon Hash
Fall-ID
ICANN OVERSIGHT

Akkreditierung und RAA-Kontext

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.

Eine Akkreditierung ist ein Vertrag, kein Sicherheitssiegel. ICANN-Gebühren prüfen RAA §3.18 lesen PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nichts wird automatisch gesendet.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
188.114.96.3
Network ASN
AS13335
Organization
CloudFlare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Die Edge-IP-Reputation wird dieser Domäne nicht zugeordnet.

Nameserver 2

  • monika.ns.cloudflare.com
  • razvan.ns.cloudflare.com

Location describes the IP network.

TLS-Zertifikat

Issuer
Google Trust Services / WE1
Valid from
2026-09-27 17:18:16
Valid until
2026-12-26 18:18:14
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-10-11 01:03:25 UTC
Collection source
PhishDestroy collector
Certificate fingerprint35d050fe11b134211914252e107ce8c1f7ed3766fc3e4dcf1965c023f2e68287
Certificate names · 1 SANs
  • kapithaven.digital

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

viewdns.info · 188.114.96.3rapiddns.io

Latest Classified Outcome 2026-10-21 22:32:08 UTC

Primary outcome Aktive Inhalte reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Aktive Inhalte Ordinary HTTP content served 90% 2026-10-21 22:32:08 UTC
RDAP registration Unbekannt
Observed timeline last reachable: 2026-10-21 22:32:34 UTC last content: 2026-10-21 22:32:08 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.
Technologien · 5 identified
Detected via Cloudflare Radar · Wappalyzer engine
Diese Domain melden Reichen Sie Beweismaterial ein und helfen Sie mit, andere zu schützen

VirusTotal-Analyse

15 / 89 Sicherheitsanbieter haben diese Domain markiert
View on VT
Last analyzed Previous stored snapshot: 15 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
CRDF
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Lionic
Seclookup
SOCRadar
Sophos
VIPRE

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 kapithaven.digital · checked Sep 14, 2026

91
Good
Performance
FCP
2.56s
First Contentful Paint
LCP
2.71s
Largest Contentful Paint
CLS
0.074
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.56s
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.

Stored observation history20

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

    content_served

  2. Availability monitor · Recorded state

    Unbekannt→live_content

    content_served

  3. Availability monitor · Recorded state

    Unbekannt→live_content

    content_served

  4. Availability monitor · Recorded state

    Unbekannt→live_content

    content_served

  5. Availability monitor · Recorded state

    Unbekannt→live_content

    content_served

Earlier observations 15
  1. Availability monitor · Recorded state

    Unbekannt→live_content

    content_served

  2. Availability monitor · Recorded state

    Unbekannt→live_content

    content_served

  3. Availability monitor · Recorded state

    Unbekannt→live_content

    content_served

  4. Availability monitor · Recorded state

    Unbekannt→live_content

    content_served

  5. Availability monitor · Recorded state

    Unbekannt→live_content

    content_served

  6. Availability monitor · Recorded state

    Unbekannt→live_content

    content_served

  7. Availability monitor · Recorded state

    Unbekannt→live_content

    content_served

  8. Availability monitor · Recorded state

    Unbekannt→live_content

    content_served

  9. Availability monitor · Recorded state

    Unbekannt→live_content

    content_served

  10. Availability monitor · Recorded state

    Unbekannt→live_content

    content_served

  11. Availability monitor · Recorded state

    Unbekannt→live_content

    content_served

  12. Availability monitor · Recorded state

    Unbekannt→live_content

    content_served

  13. Availability monitor · Recorded state

    Unbekannt→live_content

    content_served

  14. Availability monitor · Recorded state

    live_content

    content_served

  15. Availability monitor · First collection record

    Erreichbar

Recorded activity

6 entries
  1. AlienVault OTX

    5 community references

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. VirusTotal

    15/89 engine detections

    View source
  4. Abuse report sent

    PD-20260914-596E14

    abuse@netim.net
  5. URLScan

    Page captured

    View source
  6. Added to PhishDestroy

    kapithaven.digital

    View source

Check for cloaking

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

kapithaven.digital

Nachweise und externe Berichte

Sicherheitsanalyse
URLScan Analyzed VirusTotal 15 det. ChainPatrol URLQuery 4 threat alerts SSL Labore Stored certificate dates valid CF-Radar Schädlich OTX 5 refs WOT ScamAdviser Blacklist-Prüfung URLVoid Sucuri SiteCheck MDN-Beobachtungsstelle
Momentaufnahme der übermittelten Beweise
Sent: Ledger records: 1 Case ID: PD-20260914-596E14 Recipient: abuse@netim.net
Page title stored with report: KapitHaven | AI Trading Platform | Authorized Web Resource
PDF notice generated Notice text archived (275 chars)
Abuse notice text as sent to the provider 
Registrar: Netim SARL (France)
Policy Violations: “Strict abuse policy classifying phishing, malware, fraud and botnet activity as illegal domain use; registrar may suspend or terminate affected domains.”
Applicable Laws: French Penal Code Art.323-1+; EU Directive 2013/40/EU
OSINT und Nachrichtendienst
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Zertifikate WHOIS Wayback Archived
DNS & Netzwerk
nslookup.io DNS bgp.tools ASN /Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Eingehende Analyse
Eingehende Analyse
Help & reporting

Wurden Sie von dieser Website betroffen?

6 evidence signal groups linked 1 stored notification records Letzter bekanntermaßen aktiv
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.

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review Kein Strafverfolgungsbericht
Domain-Einspruch
Fordern Sie eine Überprüfung an, wenn Sie Inhaber dieser Domain sind und der Meinung sind, dass der Eintrag falsch ist
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 kapithaven.digital)
  • 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

Jede beliebige Domain prüfen

Bedrohungsanalyse anhand gespeicherter Blocklisten, WHOIS, DNS und öffentlicher Scan-Beweise

Jetzt scannen

Phishing melden

Melden Sie verdächtige Domains an unsere Bedrohungsdatenbank – schützen Sie die Community

Melden

Echtzeit-Bedrohungsfeed

Aktuelle Phishing-Meldungen und beobachtete Verfügbarkeitsänderungen

Überwachen

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.

Request a correction or appeal How PhishDestroy works
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/kapithaven.digital"
  title="PhishDestroy threat report for kapithaven.digital"
  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>