On 2026‑08‑04 the domain qrsu.io was observed flagged as part of an elevated‑risk generic phishing campaign. VirusTotal reports indicate that 16 of 91 scanning engines returned a malicious classification for the host, demonstrating a moderate consensus of detection across multiple vendors. The domain is listed on a single public security blocklist and is actively blocked by the PhishDestroy filtering service, confirming that at least one commercial anti‑phishing solution has incorporated it into its deny list.
No additional intelligence such as registrar details, registration date, hosting IP, autonomous system, SSL certificate information, or page title has been published in the current feed, so the underlying infrastructure remains opaque. The absence of these data points limits the ability to attribute the infrastructure to a specific operator or to map its network relationships. Nonetheless, the presence on VirusTotal and a known blocklist, combined with the elevated risk rating, suggests that qrsu.io is being used to harvest credentials or otherwise deceive users.
Defenders should add qrsu.io to local deny lists, enforce URL filtering rules that block the domain, and monitor outbound DNS queries for any attempts to resolve it. Network traffic to the domain should be logged and, where possible, redirected to a sandbox for deeper analysis. Continuous re‑evaluation is advised, as additional indicators such as hosting IPs, certificate fingerprints, or page content may emerge in future threat‑intel updates.
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 observation内容在线Ordinary HTTP content served90%2026-10-13 22:06:26 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 22:06:26 UTClast content: 2026-10-13 22:06:26 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.
技术 · 2 identified
V
Vercel
PaaS
Vercel is a cloud platform for static frontends and serverless functions.
Google PageSpeed Insights — mobile performance audit of qrsu.io· checked Aug 4, 2026
99
Good
Performance
FCP
0.76s
First Contentful Paint
LCP
2.1s
Largest Contentful Paint
CLS
0.008
Cumulative Layout Shift
TBT
44ms
Total Blocking Time
SI
2.25s
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.
Domain Status Transition2026-10-13 22:29:42 UTC
Domain state transitioned from alive to dead.
Domain Status Transition2026-09-11 22:17:55 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-09-10 22:42:26 UTC
Domain state transitioned from alive to dead.
Domain Status Transition2026-08-04 22:14:37 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-08-04 04:15:11 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-08-04 01:04:35 UTC
Domain ingestion complete. Initial state is marked as unknown.
威胁响应 Pipeline
发现
Analysis
Monitoring
16 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.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
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)
