On 2026-10-07, wi-rr.com was flagged by OpenPhish and Phishunt external blocklists for phishing risks. This domain was also listed internally by Phishdestroy on the same date.
Recorded Evidence
OpenPhish and Phishunt both included wi-rr.com on their blocklists as of 2026-10-07. VirusTotal reported 12 detections out of 92 scanners for this domain on the same date. OTX associated wi-rr.com with two pulses as of 2026-10-07. The domain was registered through Tucows Domains Inc. on 2026-01-15.
Interpretation
The presence of wi-rr.com on multiple external blocklists and its detection by several VirusTotal scanners indicate that it has been subject to scrutiny by various security sources. The OTX record with two pulses further suggests that this domain has drawn attention within threat intelligence communities. These observations, all from 2026-10-07, provide a snapshot of the domain's status across several independent monitoring platforms.
Recommended Actions
To address the findings related to wi-rr.com, review and preserve all blocklist entries from OpenPhish and Phishunt for reference. Retain the VirusTotal detection record and OTX pulse associations for ongoing comparison. It is advisable to monitor these sources for any future updates or changes regarding wi-rr.com.
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-11 01:41:01 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 01:41:01 UTClast content: 2026-10-11 01:41:01 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.
使用技術 · 1 identified
N
Nginx
Web serversReverse proxies
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
Last analyzed Previous stored snapshot: 12 detections
Abusix
alphaMountain.ai
BitDefender
Chong Lua Dao
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Lionic
VIPRE
Webroot
サイトパフォーマンス分析
Google PageSpeed Insights — mobile performance audit of wi-rr.com· checked Oct 7, 2026
100
Good
Performance
FCP
0.76s
First Contentful Paint
LCP
0.76s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.04s
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.
Status Check2026-10-09 04:00:43 UTC
Telemetry event observed.
Domain Status Transition2026-10-09 01:47:53 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-10-07 10:00:23 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-10-07 08:04:18 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 173.231.198.109.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
13 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.
(CA)
