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; 8 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.
apclabel.shop was recorded in the PhishDestroy internal listing on 2026-10-02, the same date as its first observation. The domain resolves to an IP address in Georgia, and its SSL certificate was issued by Let's Encrypt / YE2.
Recorded Evidence
PhishDestroy's internal listing for apclabel.shop was recorded on 2026-10-02. VirusTotal reported 6 detections out of 91 scanners on 2026-09-11. OTX recorded 2 pulses on 2026-10-02. PageSpeed recorded a performance score of 59 on 2026-10-02. The SSL certificate was scanned on 2026-10-02, issued by Let's Encrypt / YE2.
Interpretation
The PhishDestroy listing, OTX pulses, and VirusTotal detections are separate source observations with different scopes and dates. The VirusTotal scan predates the other records by several weeks, so its detection count and the later listings should not be treated as a single measurement. The PageSpeed score describes a performance measurement, not a security judgment. These records allow comparison of what each source reported, but they do not establish a verdict about the domain.
Recommended Actions
Preserve the PhishDestroy listing record for apclabel.shop and the OTX pulse record as separate source artifacts. Compare the VirusTotal detection record against the PhishDestroy and OTX records to see whether the sources align. Re-check the domain against the same sources at a later date to observe any changes in their reported observations.
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:08:57 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:08:57 UTClast content: 2026-10-11 10:08:57 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 apclabel.shop· checked Oct 2, 2026
59
Needs Work
Performance
FCP
2.9s
First Contentful Paint
LCP
14.94s
Largest Contentful Paint
CLS
0.031
Cumulative Layout Shift
TBT
237ms
Total Blocking Time
SI
7.68s
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-02 18:14:16 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 46.245.239.66.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
12 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.
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.
