ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@dynadot.com.
The latest stored availability evidence still shows the domain reachable; 7 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations.
This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
SSL certificate is invalid or expired. Issuer: Let's Encrypt / YE1
证据摘要
关键
VirusTotal
11/91
OTX
4 community refs
URLScan
Stored capture
Assessment
arizonafresh.shop was recorded in the PhishDestroy internal listing on 2026-10-04, providing a dated catalogue entry for the domain. The domain was also observed with a valid SSL certificate on the same date.
Recorded Evidence
The PhishDestroy internal listing for arizonafresh.shop was created on 2026-10-04. The domain's SSL certificate was issued by Let's Encrypt / YE1 and scanned on 2026-10-04. Registration occurred through Dynadot Inc. on 2026-07-23.
Interpretation
These source records document the domain's inclusion in a security catalogue and its technical setup as of their respective dates. The SSL certificate and registration details offer insight into the domain's configuration and timeline, while the PhishDestroy listing highlights its status in a publisher-owned catalogue.
Recommended Actions
For arizonafresh.shop, retain the PhishDestroy internal listing and SSL certificate record for ongoing review. Compare these dated records with future observations to track any changes in catalogue status or certificate configuration. Preserve the registration information for reference in any subsequent analysis.
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:34 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-11 10:38:34 UTClast content: 2026-10-11 10:38:34 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.
Google PageSpeed Insights — mobile performance audit of arizonafresh.shop· checked Oct 5, 2026
64
Needs Work
Performance
FCP
2.86s
First Contentful Paint
LCP
7.31s
Largest Contentful Paint
CLS
0.032
Cumulative Layout Shift
TBT
309ms
Total Blocking Time
SI
3.16s
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 03:02:59 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 46.245.239.195.
威胁响应 Pipeline
发现
Analysis
Notifications
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.
