On 2026-10-02, anoncopenhagen.shop was observed and included in the PhishDestroy internal listing, marking its earliest recorded appearance in this publisher's system. The same date is noted as the domain's first observation in the available evidence.
Recorded Evidence
The PhishDestroy internal listing recorded anoncopenhagen.shop on 2026-10-02. The domain was also first observed on 2026-10-02, and its IP address was documented as 195.96.130.225 at that time.
Interpretation
These records from PhishDestroy indicate that anoncopenhagen.shop was both detected and catalogued on the same day, providing a clear reference point for its initial appearance in the monitored data. The evidence does not include further details about the domain's content or activity beyond this observation date.
Recommended Actions
Retain the PhishDestroy internal listing and first observation records for anoncopenhagen.shop for future reference. Compare these records with any subsequent findings to track changes or new observations related to the domain.
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 10:08:32 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-11 10:08:32 UTClast content: 2026-10-11 10:08:32 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
H
HTTP/3
Miscellaneous
HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.
Google PageSpeed Insights — mobile performance audit of anoncopenhagen.shop· checked Oct 2, 2026
83
Needs Work
Performance
FCP
2.89s
First Contentful Paint
LCP
3.39s
Largest Contentful Paint
CLS
0.016
Cumulative Layout Shift
TBT
153ms
Total Blocking Time
SI
3.96s
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-02 17:50:01 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.225.
威胁响应 Pipeline
发现
Analysis
Monitoring
10 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.
