Sicherheits-Engines melden eine Entdeckung: 8. Ö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 complaint@gname.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.
Stored evidence for kta.capital: VirusTotal recorded 5 detections among 91 scanners on 2026-08-28. That ratio reproduces the stored check in its original units and is not converted into another measure. MetaMask and SEAL appear as named external blocklist observations for kta.capital. Each item in this report remains at the scope supplied by its dated source record.
Detection Evidence
VirusTotal records 5 detections among 91 scanners in the stored snapshot dated 2026-08-28. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-08-28 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.
Source Context
MetaMask and SEAL are recorded as named external blocklist observations for kta.capital in the snapshot dated 2026-08-28. The stored MetaMask and SEAL blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains kta.capital as a publisher record. That PhishDestroy record is counted separately from the MetaMask and SEAL external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.
Reachability and Timeline
The record first observed kta.capital on 2026-08-28. The MetaMask and SEAL blocklist snapshot is dated 2026-08-28 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-04-27. A URLScan reference was stored on 2026-08-28 as a dated artifact for review. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.
Registration and Infrastructure
The source stores 104.21.0.86 as the observed address in this record. The registration date for kta.capital is recorded as 2026-04-27. The stored ASN observation records 13335 and Cloudflare, Inc. in this record. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.
Conclusion
The kta.capital record states that VirusTotal recorded 5 detections among 91 scanners on 2026-08-28. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-08-28. PhishDestroy remains a separate publisher catalogue entry in the stored record. The observed address field in this record contains 104.21.0.86. The supported conclusion is bounded to the exact stored observations for kta.capital. Any statement beyond those source values would require additional dated material.
Recommended Actions
Avoid submitting sensitive information to kta.capital during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain kta.capital as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and MetaMask and SEAL blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to kta.capital. The stored record does not justify extending that rule to 104.21.0.86 or to other infrastructure records.
Analyse von Erkennung und Umgehung
Überprüfung der Cloaking- und Traffic-Verteilung
Noch nicht eingescanntBislang wurde noch kein Unterschied zwischen Crawler und Browser festgestellt.
Gespeicherte Beobachtungen zum Vergleich zwischen Crawler und Browser für diesen Host sowie eine Echtzeit-Fingerabdruckprüfung für Verkehrsverteilungssysteme im Keitaro-Stil.
Gespeichertes Cloaking-Flag
Noch nicht eingescannt
Letzter Tarnungsscan
Vom Scanner erkannter Server-Header
cloudflare
Anmerkung des Scanners:alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare
Live-TDS-Fingerabdruckprüfung
Sieben Keitaro-Fingerabdrücke sowie ein Vergleich zwischen Crawler und Browser, der vom „PhishDestroy“-Scanner ausgeführt wird, wenn dieses Fenster geöffnet ist.
DOM Analysisanalyzed 09.10.2026score 95/1001 brand signal
Submitted URLhttp://kta.capital/
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.
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: ResolvedRegistration: Unknown
Latest HTTP observationAktive InhalteOrdinary HTTP content served90%2026-10-13 10:27:54 UTC
RDAP registrationUnbekannt
Observed timelinelast reachable: 2026-10-13 10:27:54 UTClast content: 2026-10-13 10:27:54 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 · 3 identified
H
HSTS
Sicherheit
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Last analyzed First positive detection Previous stored snapshot: 7 detections
alphaMountain.ai
Bfore.Ai PreCrime
CRDF
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
SOCRadar
VIPRE
Website-Performanceanalyse
Google PageSpeed Insights — mobile performance audit of kta.capital· checked Aug 28, 2026
56
Needs Work
Performance
FCP
4.66s
First Contentful Paint
LCP
7.95s
Largest Contentful Paint
CLS
0.006
Cumulative Layout Shift
TBT
73ms
Total Blocking Time
SI
11.15s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Threat First Observed2026-08-28 13:07:08 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 104.21.0.86.
Pipeline zur Reaktion auf Sicherheitsbedrohungen
Entdeckung
Analysis
Notifications
Monitoring
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Bedrohung erkannt
kta.capital erkannt und für eine vollständige Analyse in die Warteschlange gestellt
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
Die Domäne bleibt erreichbar oder zugriffsbeschränkt; Zukünftige Überprüfungen könnten diese Beobachtung aktualisieren.
How we investigate & report
Public scans, evidence and abuse channels
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.
6 evidence signal groups linked1 reports recordedLetzter 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.
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 →
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
Verwandte Infrastruktur und Berichte
Gespeicherte Beziehungen werden nach dem genau passenden Attribut gruppiert. Ein gemeinsam genutzter Anbieter oder Registrar allein beweist keinen gemeinsamen Besitz.
Direkter Link Verwendet eine Registrierung oder ein identisches Phishing-Kit.
Hilfssignal Gemeinsame Nutzung der Infrastruktur oder einer Zielmarke; kein Hinweis auf einen einzigen Betreiber.
Nur zur Einsicht Zur Navigation aufgeführt; keine gemeinsamen Attribute mit diesem Host.
Infrastrukturkarte · kta.capital
Jede Spalte gibt einen Grund an, warum eine Domain mit diesem Host verknüpft ist. Knoten in voller Größe kennzeichnen „VirusTotal“-Erkennungen, gestrichelte Knoten sind bereits offline. Die vollständigen Listen folgen weiter unten.
Inhaltliche Übereinstimmungen8
Derselbe Favicon-Hash oder derselbe Seitentitel wie bei diesem Host.
Weitere Berichte zur gemeinsamen Nutzung von Cloudflare Edge1
Diese Berichte werden auf dieselbe gemeinsame Edge-IP aufgelöst. Sie helfen bei der Berichtserkennung, bedeuten jedoch keinen gemeinsamen Besitz oder einen gemeinsamen Ursprungsserver.
Über denselben Registrar registriert. Ein Registrar betreut Millionen von Kunden, die in keiner Verbindung zueinander stehen; daher werden hier lediglich Berichte zusammengefasst, anstatt eine Verbindung nachzuweisen.
Beobachten Sie aktuelle Bedrohungen oder legen Sie Widerspruch gegen diesen Eintrag ein, wenn Sie der Meinung sind, dass es sich um einen Fehlalarm handelt
