On 2026-10-07, anekkeshop.shop was observed with a PageSpeed performance score of 70, and its inclusion in the PhishDestroy internal listing was also recorded. The domain was first noted on the same date, providing a reference point for its technical and security assessment.
Recorded Evidence
VirusTotal checked anekkeshop.shop on 2026-10-07, reporting 0 detections out of 92 scanners. OTX recorded two pulses for the domain on 2026-10-07. The PageSpeed assessment on that date reported a performance score of 70. The domain was listed in the PhishDestroy internal catalogue as of 2026-10-07.
Interpretation
These source records offer a snapshot of anekkeshop.shop's technical and security-related observations as of 2026-10-07. VirusTotal's scan results reflect no detections by its participating scanners, while OTX's two pulses indicate the domain drew some community or automated attention. The PageSpeed score provides a measure of web performance, and the PhishDestroy listing documents its presence in a publisher-managed catalogue.
Recommended Actions
For anekkeshop.shop, retain the VirusTotal, OTX, and PageSpeed source records for future reference and comparison. Review the domain's entry in the PhishDestroy internal catalogue alongside subsequent technical or security assessments. Preserving these dated records will support ongoing evaluation of the domain based on observed evidence.
DOM Analysisanalyzed 2026年10月9日score 68/1001 brand signal
Submitted URLhttp://anekkeshop.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:08:10 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:08:10 UTClast content: 2026-10-11 10:08:10 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
CyRadar
ESET
Forcepoint ThreatSeeker
G-Data
Gridinsoft
LevelBlue
ネットクラフト
SOCRadar
サイトパフォーマンス分析
Google PageSpeed Insights — mobile performance audit of anekkeshop.shop· checked Oct 7, 2026
70
Needs Work
Performance
FCP
2.91s
First Contentful Paint
LCP
8.13s
Largest Contentful Paint
CLS
0.004
Cumulative Layout Shift
TBT
69ms
Total Blocking Time
SI
2.91s
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-07 01:31:18 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.197.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
10 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)
