SSL certificate is invalid or expired. Issuer: Let's Encrypt / YE1
証拠の概要
クリティカル
VirusTotal
6/92
OTX
4 community refs
URLScan
Stored capture
Assessment
The domain arganour.shop was first observed on 2026-10-04 and listed internally by PhishDestroy on 2026-10-05. Its PageSpeed performance score of 86 was also recorded on 2026-10-05.
Recorded Evidence
PhishDestroy added arganour.shop to its internal listing on 2026-10-05. OTX recorded four pulses for the domain on the same date. The SSL certificate was issued by Let's Encrypt / YE1 on 2026-10-04.
Interpretation
Multiple dated observations indicate recent monitoring of arganour.shop by security and performance tools. The combination of PhishDestroy listing and OTX pulses reflects cataloguing and threat intelligence activity. The PageSpeed score offers a technical benchmark for the site’s performance.
Recommended Actions
Retain the OTX pulse records and PhishDestroy internal listing entry for arganour.shop. Compare future PageSpeed scores and OTX pulses to these records to assess any changes in the domain’s status.
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.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observationコンテンツ公開中Ordinary HTTP content served90%2026-10-11 10:38:28 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:38:28 UTClast content: 2026-10-11 10:38:28 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.
Last analyzed First positive detection Previous stored snapshot: 5 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
G-Data
Gridinsoft
SOCRadar
サイトパフォーマンス分析
Google PageSpeed Insights — mobile performance audit of arganour.shop· checked Oct 5, 2026
86
Needs Work
Performance
FCP
2.89s
First Contentful Paint
LCP
2.89s
Largest Contentful Paint
CLS
0.021
Cumulative Layout Shift
TBT
194ms
Total Blocking Time
SI
3.53s
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-04 02:51:22 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.212.
脅威対応 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)
