VirusTotal
10 / 91
“cat.kwant.top”
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.
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.
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.
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.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: 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.
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.
marlowe.ns.cloudflare.com.Location describes the IP network.
466071d4e9556bd8fdb426969db8c22662a06eb7b3ab19bcc42723b333cde912Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
93.152.223.78. 11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive