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; 17 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.
purecrystalslay.info returned an HTTP status code of 200 during a check conducted on 2026-10-01. The domain was first observed on 2026-09-23, indicating recent activity within the recorded timeline.
Recorded Evidence
The domain purecrystalslay.info was first observed on 2026-09-23 and registered on 2025-08-27. An HTTP check on 2026-10-01 recorded status code 200, while a PageSpeed performance score of 91 was documented on 2026-09-23. VirusTotal, checked on 2026-09-25, reported 17 detections out of 91 scanners. OTX, also checked on 2026-09-25, showed 4 pulses. The PhishDestroy internal listing was marked as true, and the SSL certificate was issued by YE2, with a scan recorded on 2026-09-24.
Interpretation
The evidence from VirusTotal and OTX, both recorded on 2026-09-25, provides insight into the domain's security profile at that time, while the HTTP and PageSpeed checks occurred on earlier and later dates. The presence of a PhishDestroy internal listing, along with a recent SSL scan, adds further context but reflects different points in the domain's timeline. Comparing these sources highlights how observations from various dates contribute to a more complete understanding of purecrystalslay.info.
Recommended Actions
Retain all evidence for purecrystalslay.info with their exact dates and source names for future comparison. Compare subsequent observations with the 2026-09-23 to 2026-10-01 records to track any changes. Avoid submitting sensitive information to purecrystalslay.info during any ongoing review.
スキャナーに関する注記:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='purecrystalslay.info', port=80): Max retries exceeded with url: / (Caused by NewConnection
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-11 10:08:14 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-07 02:08:43 UTCcurrent episode first observed: 2026-10-08 20:20:32 UTCobserved RIP window: 2026-10-07 02:08:43 UTC → 2026-10-08 20:20:32 UTC · 42.20hmidpoint estimate ≈ 2026-10-07 23:14:37 UTC · precision medium · basis bounded
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
A
Apache HTTP Server
Web servers
Apache is a free and open-source cross-platform web server software.
Google PageSpeed Insights — mobile performance audit of purecrystalslay.info· checked Sep 23, 2026
91
Good
Performance
FCP
0.79s
First Contentful Paint
LCP
2.9s
Largest Contentful Paint
CLS
0.117
Cumulative Layout Shift
TBT
51ms
Total Blocking Time
SI
3.26s
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-07 02:08:43 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-09-23 23:04:26 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-23 19:40:55 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 103.224.212.142.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
13 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.
