On 2026-10-02, antigonastore.shop was recorded in the PhishDestroy internal listing, providing a publisher-specific catalogue entry for the domain. A PageSpeed performance score of 67 was also measured on the same date, offering insight into the site's technical performance.
Recorded Evidence
VirusTotal, checked on 2026-09-29, reported 11 detections out of 91 scanners for antigonastore.shop. OTX was checked on 2026-10-02 and recorded 2 pulses for the domain. The SSL scan on 2026-10-02 named Let's Encrypt / YE1 as the certificate issuer.
Interpretation
The VirusTotal and OTX records represent distinct observations from separate sources, each documenting their findings on different dates. The PhishDestroy internal listing and PageSpeed score are additional technical records that provide further context about antigonastore.shop without implying any specific activity or status.
Recommended Actions
For antigonastore.shop, retain the VirusTotal and OTX records as reference points for future comparison. Review the PhishDestroy internal listing and PageSpeed performance score alongside these sources to track changes or updates in subsequent checks. Keep the SSL scan record for monitoring certificate history.
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:26 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:08:26 UTClast content: 2026-10-11 10:08:26 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 antigonastore.shop· checked Oct 2, 2026
67
Needs Work
Performance
FCP
2.86s
First Contentful Paint
LCP
19.06s
Largest Contentful Paint
CLS
0.02
Cumulative Layout Shift
TBT
179ms
Total Blocking Time
SI
3.55s
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 18:04:28 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.207.
脅威対応 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)
