lookmark.net was listed in the PhishDestroy internal catalogue on 2026-10-08, the same date it was first observed. The catalogue entry indicates the domain was flagged by a publisher-owned source on that day.
Recorded Evidence
lookmark.net was registered on 2022-05-21 with TUCOWS.COM, CO. VirusTotal scanned the domain on 2026-09-23, reporting 8 detections out of 92 scanners. PhishDestroy included the domain in its internal listing as of 2026-10-08.
Interpretation
The VirusTotal and PhishDestroy records provide dated observations about lookmark.net’s status in 2026. These sources offer a snapshot of detection data and catalogue inclusion during the same general period, without implying causation or change over time.
Recommended Actions
Review the VirusTotal scan and PhishDestroy catalogue entry for lookmark.net to inform decisions about the domain. Preserve the dated VirusTotal scan and the PhishDestroy catalogue entry for ongoing monitoring and future comparisons of its status.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-11 10:03:22 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:03:22 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.
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-08 14:26:35 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 216.40.34.41.
脅威対応 Pipeline
ディスカバリー
Analysis
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.
(CA)
