As recorded on 2026-10-02, appellewear.shop appeared in PhishDestroy's internal listing during a blocklist check. The domain was also listed in the PhishDestroy internal catalogue, indicating a publisher-side record.
Recorded Evidence
VirusTotal checked appellewear.shop on 2026-09-27 and reported 7 detections out of 91 scanners. OTX pulses were recorded for the domain on 2026-10-02. The domain was first observed on 2026-10-02 and was included in the PhishDestroy internal listing.
Interpretation
The evidence for appellewear.shop covers several sources, each with its own date and focus. VirusTotal provides insight into how the domain was evaluated by multiple scanners, while OTX pulses reflect community-driven attention. The PageSpeed score offers a technical perspective, and the PhishDestroy listing shows publisher-side cataloguing. These records allow for comparison of technical and security-related observations without linking them to broader trends.
Recommended Actions
To address the findings for appellewear.shop, preserve the VirusTotal report and OTX pulse records for reference and comparison. Retain the PageSpeed performance score and PhishDestroy internal listing as part of the domain's technical and publisher-side history. Review these dated records to inform any further investigation or monitoring efforts related to appellewear.shop.
スキャナーに関する注記:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='appellewear.shop', port=80): Max retries exceeded with url: / (Caused by NewConnectionErro
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-11 10:08:31 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 01:41:42 UTClast content: 2026-10-11 01:41:42 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 appellewear.shop· checked Oct 2, 2026
78
Needs Work
Performance
FCP
2.86s
First Contentful Paint
LCP
4.28s
Largest Contentful Paint
CLS
0.005
Cumulative Layout Shift
TBT
129ms
Total Blocking Time
SI
3.61s
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 19:21:21 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.250.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
11 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.
Web Archive
Preserved in ウェイバック・マシン — historical evidence archived
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)
