Stored registration data identifies NameSilo as the registrar. PhishDestroy maintains separate registrar investigations; that broader material is contextual and is not an independent detection for this domain.
hgdj9.wiki was recorded in the PhishDestroy internal listing on 2026-10-14, providing a documented entry for the domain in that catalogue. A PageSpeed performance score of 65 was also measured for the domain on the same date, offering a technical performance reference.
Recorded Evidence
VirusTotal checked hgdj9.wiki on 2026-10-12, recording 5 detections from 92 total scanners. The PhishDestroy internal listing included the domain as of 2026-10-14. The domain's registration date is recorded as 2026-10-08 with NameSilo, LLC. The PageSpeed performance score was measured on 2026-10-14.
Interpretation
The VirusTotal record contains a quantitative measurement of detections by multiple scanners, documenting how hgdj9.wiki was evaluated for security-related findings. The PhishDestroy listing provides a reference entry within the publisher's catalogue, while the PageSpeed score offers insight into the domain's technical performance at a specific time. These sources together allow for cross-referencing security and technical observations from different perspectives.
Recommended Actions
Future reviews of hgdj9.wiki should retain the VirusTotal detection record and the PhishDestroy listing for comparison. The PageSpeed performance score should also be preserved to monitor technical changes. Comparing these records over time will support ongoing assessment of the domain's recorded profile.
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
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.
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-14 18:51:12 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-14 18:51:12 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.
Values retained by the collector; long values may be shortened during collection.
Crawler & disclosure files
Site configuration evidence
1 recorded files
Files, paths and sitemap entries retained by the collector.
robots.txt
Reachable (legacy)/robots.txt
HTTP response
200
Observed at
2026-10-14 20:52:09 UTC
来源
legacy scan archive
A legacy scan recorded a successful response. The file contents were not retained.
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-14 18:51:12 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 188.114.96.3.
威胁响应 Pipeline
发现
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.
(US)
PhishDestroy Investigation
