kapitaalkade.com returned HTTP status 200 on 2026-10-01, the date of the recorded HTTP check. The domain was first observed on 2026-09-15, according to the evidence record.
Recorded Evidence
The registrar recorded for kapitaalkade.com is NameCheap, Inc., with a registration date of 2025-09-09. VirusTotal recorded 14 detections across 89 scanners on 2026-09-18. OTX recorded 3 pulses on 2026-09-18. The PhishDestroy internal listing was recorded as true, and the blocklist check occurred on 2026-10-01. The IP address 104.219.250.37 is recorded in the United States with the organization 3402 East University.
Interpretation
The VirusTotal and OTX observations share the 2026-09-18 date, while the HTTP check and PhishDestroy blocklist check are dated 2026-10-01, so those sources describe different points in time. The first observation on 2026-09-15 predates all of these checks. Because the dates differ, the records cannot be treated as a single synchronized snapshot.
Recommended Actions
Reviewers should retain the dated records for kapitaalkade.com, including the HTTP, VirusTotal, OTX and PhishDestroy observations. Subsequent checks of kapitaalkade.com should be compared against these exact dates and values. During review, avoid submitting sensitive information to kapitaalkade.com.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Attributionmechanism: Lifecycle Notice Pagesource: Current Http Probe
Evidence layersAvailability: Non Threat ContentContent: Replaced Or ParkedDNS: ResolvedRegistration: Unknown
Latest HTTP observation非活动Expired Landing PageLifecycle Notice Page60%2026-10-13 01:16:19 UTC
RDAP registration未知
Observed timelinecurrent episode first observed: 2026-10-01 01:39:31 UTCfirst terminal observation: 2026-10-01 01:39:31 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.
Last analyzed Previous stored snapshot: 14 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
卡巴斯基
Lionic
SOCRadar
Sophos
VIPRE
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.
Domain Status Transition2026-09-15 22:00:21 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-15 18:42:20 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 104.219.250.37.
威胁响应 Pipeline
发现
Analysis
Monitoring
9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
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.
(US)
