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@rashost.com.
The latest stored availability evidence still shows the domain reachable; 13 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.
aishajewelryhq.shop returned an HTTP status 301 on 2026-10-01, according to the recorded HTTP check. The same domain was first observed on 2026-09-28, and a PhishDestroy internal listing is also recorded.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 301, while the first observation of aishajewelryhq.shop dates to 2026-09-28. VirusTotal recorded 8 detections across 91 scanners on 2026-10-01, and OTX recorded 4 pulses on the same date. The PhishDestroy internal listing is recorded as true, and the SSL scan on 2026-09-28 identified Let's Encrypt / YE1 as the issuer.
Interpretation
The HTTP check, VirusTotal, and OTX observations all share the 2026-10-01 date, so they describe the same point in time, whereas the first observation and SSL scan come from 2026-09-28. Because the PhishDestroy listing has no separate dated snapshot in this evidence, its timing cannot be aligned with the other sources. These dated records allow comparison of what each source reported, not a conclusion about the domain.
Recommended Actions
Retain the dated records for aishajewelryhq.shop so that later checks can be compared against the 2026-09-28 and 2026-10-01 observations. When reviewing the domain, avoid submitting sensitive information until the recorded status and listings are independently confirmed. Subsequent observations should be logged with their own dates to show how the recorded values change over time.
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:09:31 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-11 10:09:31 UTClast content: 2026-10-11 01:42:37 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: 8 detections
alphaMountain.ai
Bfore.Ai PreCrime
BitDefender
ESET
G-Data
Gridinsoft
LevelBlue
Webroot
网站性能分析
Google PageSpeed Insights — mobile performance audit of aishajewelryhq.shop· checked Sep 28, 2026
72
Needs Work
Performance
FCP
2.86s
First Contentful Paint
LCP
4.65s
Largest Contentful Paint
CLS
0.012
Cumulative Layout Shift
TBT
307ms
Total Blocking Time
SI
2.86s
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-09-28 00:30:54 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 162.222.90.31.
威胁响应 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.
