The domain qr2.it was observed in several monitoring sources, with VirusTotal recording 8 detections from 92 scanners on 2026-10-08. A PageSpeed performance score of 87 was also measured, reflecting a recorded assessment of the site's responsiveness on that date.
Recorded Evidence
On 2026-10-08, VirusTotal reported 8 detections out of 92 scanners for qr2.it. OTX included the domain in 4 pulses as of the same date. The domain was listed in the PhishDestroy internal catalogue. PageSpeed measured a performance score of 87 for qr2.it on 2026-10-08. The registrar was recorded as 1 Api GmbH, with the registration date noted as 2009-12-16.
Interpretation
These records from VirusTotal, OTX, and PhishDestroy provide a dated snapshot of qr2.it's status in security and performance monitoring systems. Each source offers different types of information: VirusTotal aggregates scanner results, OTX tracks pulse activity, and PhishDestroy maintains an internal listing. The PageSpeed score documents a specific performance measurement.
Recommended Actions
To support ongoing review of qr2.it, preserve the VirusTotal, OTX, and PhishDestroy records for future reference. Compare new source observations to these records to track any changes. Use the recorded PageSpeed score as a benchmark for future performance assessments.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not yet scanned
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-08 15:36:32 UTC
RDAP registrationUnknown
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: 8 detections
alphaMountain.ai
Forcepoint ThreatSeeker
G-Data
Gridinsoft
MalwareURL
SOCRadar
URLQuery
VIPRE
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of qr2.it· checked Oct 8, 2026
87
Needs Work
Performance
FCP
1.05s
First Contentful Paint
LCP
3.91s
Largest Contentful Paint
CLS
0.014
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
3.11s
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-10-08 15:15:55 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 54.201.223.196.
Threat Response Pipeline
Discovery
Analysis
Monitoring
7 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.
4 evidence signal groups linked0 reports recordedUnverified
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
