The domain flax-loafers.shop was first observed on 2026-10-08, with VirusTotal recording a scan on the same date that reported 17 detections out of 92 scanners. This domain is also included in the PhishDestroy internal listing, indicating it has been catalogued for monitoring purposes.
Recorded Evidence
On 2026-10-08, VirusTotal reported 17 detections from 92 scanners for flax-loafers.shop. OTX pulses included this domain as of 2026-10-08, and PhishDestroy recorded an internal listing on that date. The domain's first observation date is also 2026-10-08.
Interpretation
These records show that flax-loafers.shop was noted by several monitoring sources on 2026-10-08. The VirusTotal scan, OTX pulse, and PhishDestroy listing all provide separate perspectives on the domain's status, reflecting attention from multiple security platforms at the time of observation.
Recommended Actions
To support further review of flax-loafers.shop, retain the VirusTotal, OTX, and PhishDestroy records as reference points. Compare these source records to track any changes or additional observations over time, and use them to inform any future investigation or monitoring actions involving this domain.
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-13 23:01:07 UTC
RDAP registration未知
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:33:07 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 104.18.71.116.
威胁响应 Pipeline
发现
Analysis
Monitoring
9 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)
