cat.kwant.top returned HTTP 301 on 2026-10-01, according to the recorded HTTP check, and the domain was first observed on 2026-09-23. The same evidence set records an IP address of 93.152.223.78 in Germany under RMP Protection Limited.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 301 for cat.kwant.top. The first observation of the domain is dated 2026-09-23. A VirusTotal check on 2026-09-27 recorded 10 detections across 91 scanners. The SSL scan on 2026-09-24 named Let's Encrypt / YE1 as the issuer. The PhishDestroy internal listing is recorded as true, and the blocklist check is dated 2026-10-01.
Interpretation
The PhishDestroy internal listing and the VirusTotal detection count are separate source records with different dates, so they should be read as distinct observations rather than a combined signal. The first observation and the HTTP check fall on different dates, which shows the domain was recorded before the response was captured, but the records do not establish what changed between them. The SSL scan and VirusTotal check also come from different dates, so their values describe separate snapshots.
Recommended Actions
For cat.kwant.top, preserve the PhishDestroy internal listing and the VirusTotal record as separate items for later comparison. Compare the HTTP check record with the first observation record to see whether the recorded response aligns with the initial sighting. Retain the SSL scan record alongside the other source records so each dated snapshot remains available. Review the VirusTotal record independently from the PhishDestroy listing before deciding on any follow-up.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:timeout: raw=timeout; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='cat.kwant.top', port=80): Max retries exceeded with url: / (Caused by ConnectTimeoutError(
For the registrable domain kwant.top behind this subdomain, 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.
Latest HTTP observation未知Probe Inconclusive20%2026-10-14 10:09:02 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-09 10:06:53 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.
技术 · 3 identified
P
Python
Programming languages
Python is an interpreted and general-purpose programming language.
Last analyzed Previous stored snapshot: 2 detections
alphaMountain.ai
BitDefender
CRDF
Forcepoint ThreatSeeker
Fortinet
G-Data
卡巴斯基
SOCRadar
Sophos
Yandex Safebrowsing
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-10-09 01:47:49 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-10-06 22:14:26 UTC
Domain state transitioned from alive to dead.
VirusTotal Detections Update2026-09-24 05:44:02 UTC
VirusTotal scanner detections updated from 1 to 2. Added scanner alerts: SOCRadar.
Threat First Observed2026-09-23 20:27:22 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 93.152.223.78.
威胁响应 Pipeline
发现
Analysis
Monitoring
11 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.
(NL)
