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; 15 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.
On 2026-10-01, alessandrastyle.shop returned an HTTP 301 response, a recorded status from that check. The domain was first observed on 2026-09-26, and the PhishDestroy internal listing is also recorded for this domain.
Recorded Evidence
VirusTotal recorded 6 detections across 91 scanners on 2026-09-29. OTX listed 4 pulses on 2026-09-29. The HTTP check on 2026-10-01 returned status 301. Registration occurred on 2026-06-09 with registrar Dynadot Inc., and the SSL certificate was issued by Let's Encrypt / YE1 and scanned on 2026-09-26. PageSpeed recorded a performance score of 56 on 2026-09-26, and the IP address 195.96.130.213 resolved to the US under HMZ Web Hosting Co.
Interpretation
The VirusTotal and OTX records describe separate source observations, so their counts should be read apart rather than merged. The HTTP 301 response on 2026-10-01 documents only that status at that moment, not the full content or current availability of the domain. The PhishDestroy internal listing is a publisher-owned catalogue entry, and its presence does not by itself show behavior or purpose.
Recommended Actions
Preserve the VirusTotal and OTX records for alessandrastyle.shop so future comparisons use the same source baselines. Separately retain the PhishDestroy internal listing and the recorded HTTP response, since each documents a different observation type. Compare later checks against these saved records rather than treating any single source as final, and review the domain's HTTP behavior directly if further clarity is needed.
DOM Analysisanalyzed 2026年10月9日score 88/1001 brand signal
Submitted URLhttp://alessandrastyle.shop/
Favicon Hash
ケース ID
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:12:02 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:12:02 UTClast content: 2026-10-11 10:12:02 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 alessandrastyle.shop· checked Sep 26, 2026
56
Needs Work
Performance
FCP
2.86s
First Contentful Paint
LCP
14.78s
Largest Contentful Paint
CLS
0.034
Cumulative Layout Shift
TBT
441ms
Total Blocking Time
SI
4.11s
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.
VirusTotal Detections Update2026-09-28 08:26:35 UTC
VirusTotal scanner detections updated from 5 to 6. Added scanner alerts: SOCRadar.
VirusTotal Detections Update2026-09-26 04:48:58 UTC
VirusTotal scanner detections updated from 6 to 5. Resolved alerts: Fortinet.
Threat First Observed2026-09-26 00:41:11 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.213.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
14 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.
