A suspicious listing for 'arcticleopardusagarage.shop' was observed on PhishDestroy's internal database on 2026-10-07. The domain has no VirusTotal detections but is listed in the publisher-owned PhishDestroy catalogue.
Recorded Evidence
On 2026-10-07 the domain was checked against the publisher-owned PhishDestroy catalogue and returned a listing status. Pagespeed recorded a performance score of 67 on 2026-10-07. OTX observed 2 pulses on 2026-10-07. VirusTotal detected 0 detections out of 92 scanners on 2026-09-15.
Interpretation
The listed status in the publisher-owned PhishDestroy catalogue indicates a publisher action taken on 2026-10-07. Pagespeed’s 67 performance score reflects measured loading characteristics recorded on the same date. OTX’s 2 pulses show security telemetry activity on 2026-10-07. VirusTotal’s zero detections from 92 scanners on 2026-09-15 indicate no antivirus flags at that time.
Recommended Actions
For arcticleopardusagarage.shop compare the Pagespeed performance score with future checks to observe changes. Review the publisher-owned PhishDestroy catalogue listing alongside future OTX pulses to assess consistency. Use the VirusTotal record from 2026-09-15 as a baseline for future scans.
DOM Analysisanalyzed 2026年10月9日score 93/1001 brand signal
Submitted URLhttp://arcticleopardusagarage.shop/
Favicon Hash
ICANN OVERSIGHT
認定と RAA の背景
Registrar accreditation and DNS abuse obligations
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:01:02 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:01:02 UTClast content: 2026-10-11 10:01:02 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.
Last analyzed First positive detection Previous stored snapshot: 0 detections
alphaMountain.ai
Bfore.Ai PreCrime
BitDefender
CRDF
ESET
Forcepoint ThreatSeeker
G-Data
Gridinsoft
LevelBlue
SOCRadar
URLQuery
VIPRE
サイトパフォーマンス分析
Google PageSpeed Insights — mobile performance audit of arcticleopardusagarage.shop· checked Oct 7, 2026
67
Needs Work
Performance
FCP
3s
First Contentful Paint
LCP
7.64s
Largest Contentful Paint
CLS
0.011
Cumulative Layout Shift
TBT
65ms
Total Blocking Time
SI
5.04s
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.
Domain Status Transition2026-10-09 01:00:12 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-10-07 01:00:22 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-10-07 00:09:56 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 37.72.142.22.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
12 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)
