The domain rhdq.cc was observed with a VirusTotal record dated 2026-10-09, which recorded five detections out of 92 scanners. Additionally, rhdq.cc was listed in the PhishDestroy internal catalogue as of 2026-10-13, providing another reference for its security profile.
Recorded Evidence
VirusTotal checked rhdq.cc on 2026-10-09 and recorded five detections out of 92 scanners. The PhishDestroy internal listing included the domain as of 2026-10-13. OTX referenced three pulses for rhdq.cc on 2026-10-13. The domain was registered on 2026-10-08 with Gname.com Pte. Ltd., and its SSL certificate was issued by Let's Encrypt / YR1, as scanned on 2026-10-13.
Interpretation
The PhishDestroy record contains an internal listing of rhdq.cc, serving as a publisher catalogue entry. VirusTotal provides a quantitative measurement by recording the number of detections out of the total scanners, documenting how the domain was classified by various security vendors on a specific date. OTX records three pulses, reflecting community-driven intelligence activity related to rhdq.cc. These sources collectively offer a range of security-focused observations, each with its own methodology and scope.
Recommended Actions
For rhdq.cc, it is practical to retain the VirusTotal detection record and the PhishDestroy internal listing for ongoing reference and comparison. The OTX pulse count should also be preserved as part of the domain’s security evidence. Regularly reviewing these source records will help track any changes in detection or intelligence activity related to rhdq.cc.
Certificate hostname mismatch·
発行者 Let's Encrypt / YR1· stored validity ends in 84 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
141.11.85.15
Server header
nginx
ネームサーバー 4
a.share-dns.com
a5.share-dns.com
b.share-dns.net
b5.share-dns.net
Location describes the IP network.
TLS証明書
Issuer
Let's Encrypt / YR1
Valid from
2026-10-08 11:40:59
Valid until
2027-01-06 11:40:58
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-13 16:02:07 UTC
Collection source
PhishDestroy collector
Certificate fingerprinte2e429f9c87145f93a13c040c575cdc151bc520313211b4fec347cabfc705761Certificate names · 1 SANs
www.rhdq.cc
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-13 16:01:00 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-13 16:01:00 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.
Google PageSpeed Insights — mobile performance audit of rhdq.cc· checked Oct 13, 2026
57
Needs Work
Performance
FCP
7.33s
First Contentful Paint
LCP
7.39s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
68ms
Total Blocking Time
SI
8.42s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Stored Capture Evidence 1 snapshot
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
Archived HTTP responseHTTP 200
Requested URL:http://rhdq.cc/
Final URL:https://rhdq.cc/
対応 HTTP 200
HTML body 681 B
Compressed 350 B
Links 0 internal · 0 external
Detected technologies
nginx
Selected response headers
Server: nginx
Content-Type: text/html
Security headers present
Strict-Transport-Security
HSTS: observedDNSSEC: not observedWAF / firewall: not observedCloaking flag: not observed
Saved response-header values · 9
Accept-Ranges
bytes
Connection
keep-alive
Content-Length
681
Content-Type
text/html
Date
Tue, 13 Oct 2026 16:01:19 GMT
Etag
"6ac85b6a-2a9"
Last-Modified
Fri, 09 Oct 2026 03:11:38 GMT
Server
nginx
Strict-Transport-Security
max-age=31536000
Values retained by the collector; long values may be shortened during collection.
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-13 16:01:00 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 141.11.85.15.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
8 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.
