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; 1 month 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.
aagrahfinejewelsstudio.shop returned HTTP status 200 when checked on 2026-10-01, according to the recorded HTTP observation. The same record set shows a first observation on 2026-09-09, roughly three weeks earlier.
Recorded Evidence
The domain was first observed on 2026-09-09, the same date as its PageSpeed check, which recorded a performance score of 83. An SSL scan on 2026-09-09 identified the issuer as Let's Encrypt / YE2. OTX recorded 4 pulses on 2026-09-10. VirusTotal, checked on 2026-09-18, reported 13 detections across 89 scanners. The registration date is 2026-05-06 with registrar Dynadot Inc., and the publisher-owned PhishDestroy catalogue lists the domain internally.
Interpretation
The OTX pulses and VirusTotal detections are separate source observations, each with its own scope and collection method, so they should be read alongside one another rather than merged into a single score. The PageSpeed score describes only the recorded performance measurement on its check date, not the site's content or purpose. Because the HTTP, SSL, and PageSpeed checks share a calendar date, that does not establish that they were measured simultaneously or that they describe the same page state.
Recommended Actions
Preserve the recorded HTTP, OTX, and VirusTotal observations for aagrahfinejewelsstudio.shop so later checks can be compared against them. Compare future HTTP responses and detection totals separately, since each source measures a different thing. Treat the PhishDestroy catalogue entry as a publisher-owned listing and review it directly before deciding on any blocking or takedown step.
DOM Analysisanalyzed 2026年9月9日score 98/1001 brand signal
Submitted URLhttp://aagrahfinejewelsstudio.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:07:22 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:07:22 UTClast content: 2026-10-11 10:07:22 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 aagrahfinejewelsstudio.shop· checked Sep 9, 2026
83
Needs Work
Performance
FCP
3.19s
First Contentful Paint
LCP
3.64s
Largest Contentful Paint
CLS
0.005
Cumulative Layout Shift
TBT
86ms
Total Blocking Time
SI
3.19s
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.
Domain Status Transition2026-10-09 01:44:59 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-09-24 22:07:18 UTC
Domain state transitioned from alive to dead.
VirusTotal Detections Update2026-09-09 17:37:26 UTC
VirusTotal scanner detections updated from 7 to 8. Added scanner alerts: Gridinsoft.
VirusTotal Detections Update2026-09-09 07:43:58 UTC
VirusTotal scanner detections updated from 6 to 7. Added scanner alerts: alphaMountain.ai.
VirusTotal Detections Update2026-09-09 04:04:47 UTC
VirusTotal scanner detections updated from 3 to 6. Added scanner alerts: ESET, LevelBlue, SOCRadar.
Threat First Observed2026-09-09 02:58:36 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 23.252.79.159.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
17 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.
