ABUSE NOTICE · 72H+ 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@rashost.com.
The latest stored availability evidence still shows the domain reachable; 4 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.
amazfittech.shop was recorded in the PhishDestroy internal listing and referenced by OTX pulses on 2026-10-07, reflecting recent monitoring activity. The domain was first observed on 2026-10-06, indicating its presence in public records began shortly before these observations.
Recorded Evidence
VirusTotal scanned amazfittech.shop on 2026-10-07 and reported zero detections out of 92 scanners. OTX included the domain in four pulses on 2026-10-07. The PhishDestroy internal listing also recorded the domain on 2026-10-07. The SSL certificate for amazfittech.shop was issued by Let's Encrypt / YE2, and its first observation date was 2026-10-06.
Interpretation
These source records show that amazfittech.shop was noted by multiple monitoring services soon after its initial appearance. The lack of detections in the VirusTotal scan provides a contrast to its inclusion in OTX and the PhishDestroy listing. The SSL certificate and observation date offer additional context for the domain's timeline in public monitoring systems.
Recommended Actions
Further review of amazfittech.shop should reference the VirusTotal scan, OTX pulses, and the PhishDestroy internal listing. It is advisable to retain these source records for comparison and to track any future changes in the domain's monitoring status.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-11 10:07:57 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:07:57 UTClast content: 2026-10-11 01:41:09 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
Forcepoint ThreatSeeker
G-Data
Gridinsoft
LevelBlue
Webroot
サイトパフォーマンス分析
Google PageSpeed Insights — mobile performance audit of amazfittech.shop· checked Oct 7, 2026
72
Needs Work
Performance
FCP
2.89s
First Contentful Paint
LCP
6.15s
Largest Contentful Paint
CLS
0.004
Cumulative Layout Shift
TBT
58ms
Total Blocking Time
SI
3.45s
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-06 21:58:09 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 193.162.133.218.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
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.
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.
PDF notice generated Notice text archived (650 chars)
Abuse notice text as sent to the provider
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
