The domain onchnia.qpon was recorded in a PhishDestroy internal listing on 2026-10-14, and a PageSpeed check on the same date measured a performance score of 36. The domain was first observed on 2026-10-14, providing a recent context for these findings.
Recorded Evidence
A PhishDestroy internal listing entry was created for onchnia.qpon on 2026-10-14. OTX referenced the domain in three pulses as of 2026-10-14. VirusTotal checked the domain on 2026-10-14, recording 0 detections out of 92 scanners. The PageSpeed check on 2026-10-14 reported a performance score of 36. The registrar was listed as Gname.com Pte. Ltd., with a registration date of 2026-04-17.
Interpretation
PhishDestroy contains a record for onchnia.qpon, documenting its presence in an internal listing as of 2026-10-14. VirusTotal provides a measurement of the domain’s detection status across multiple security scanners, while OTX records its inclusion in three separate pulses. These sources collectively offer a technical profile of the domain’s observed infrastructure and detection history as of the recorded dates.
Recommended Actions
For onchnia.qpon, retain the PhishDestroy internal listing and VirusTotal detection record for future reference and comparison. Review the OTX pulse entries and PageSpeed performance measurement to monitor any changes in the domain’s technical or security profile over time.
The linked repository preserves daily zone observations across seven ShortDot-operated TLDs, including registration volume and abuse-related indicators. This registry context is supporting background and is not an independent detection for the domain in this report.
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 19:58:15 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-14 19:58:15 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.
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 19:39:19 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 172.67.199.242.
威胁响应 Pipeline
发现
Analysis
Notifications
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.
OTX Community References
3 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
2026年10月14日
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
2026年10月14日
Sent Report Recorded
Stored outgoing record associated with registrar Gname.com Pte. Ltd., 1 abuse contact
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.
(SG)
