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; 16 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.
akjaerbedefashion.shop returned HTTP status 301 on 2026-10-01, according to the recorded HTTP check. The same domain was first observed on 2026-09-25, and a PhishDestroy internal listing is recorded for it.
Recorded Evidence
The HTTP check dated 2026-10-01 recorded a 301 response for akjaerbedefashion.shop. The first observation of this domain is dated 2026-09-25, and a PageSpeed check on 2026-09-25 returned a performance score of 84. VirusTotal, checked on 2026-09-29, reported 9 detections across 91 scanners. OTX, checked on 2026-09-29, recorded 4 pulses, while the SSL scan on 2026-09-25 named Let's Encrypt / YE1 as the issuer.
Interpretation
The HTTP, PageSpeed and SSL observations for akjaerbedefashion.shop were collected on 2026-09-25 and 2026-10-01, while the OTX and VirusTotal checks are dated 2026-09-29. Because these named sources were consulted on different dates, their records describe separate points in time rather than one synchronized snapshot. The PhishDestroy internal listing and the OTX pulses are catalogue entries, and the VirusTotal result is a scanner count; none of these records by itself explains why the domain appears in those sources.
Recommended Actions
Retain the dated records for akjaerbedefashion.shop so that later observations can be compared against the 2026-09-25 and 2026-10-01 entries. When reviewing the domain, compare new HTTP, SSL and catalogue observations with the existing dates before drawing conclusions. Avoid submitting passwords, payment details or other sensitive information to akjaerbedefashion.shop while that review is in progress.
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:32:03 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-11 10:32:03 UTClast content: 2026-10-11 10:32:03 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 akjaerbedefashion.shop· checked Sep 25, 2026
84
Needs Work
Performance
FCP
3.02s
First Contentful Paint
LCP
3.02s
Largest Contentful Paint
CLS
0.022
Cumulative Layout Shift
TBT
204ms
Total Blocking Time
SI
4.09s
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-29 07:00:47 UTC
VirusTotal scanner detections updated from 10 to 9. Resolved alerts: alphaMountain.ai.
VirusTotal Detections Update2026-09-27 15:56:13 UTC
VirusTotal scanner detections updated from 7 to 10. Added scanner alerts: Forcepoint ThreatSeeker, Gridinsoft, SOCRadar.
VirusTotal Detections Update2026-09-27 13:43:36 UTC
VirusTotal scanner detections updated from 6 to 7. Added scanner alerts: alphaMountain.ai.
VirusTotal Detections Update2026-09-27 07:53:08 UTC
VirusTotal scanner detections updated from 7 to 6. Resolved alerts: alphaMountain.ai.
VirusTotal Detections Update2026-09-26 21:53:31 UTC
VirusTotal Detections Update2026-09-26 19:15:16 UTC
VirusTotal scanner detections updated from 1 to 2. Added scanner alerts: CyRadar.
VirusTotal Detections Update2026-09-25 19:17:36 UTC
VirusTotal scanner detections updated from 0 to 1. Added scanner alerts: SOCRadar.
Threat First Observed2026-09-25 10:28:40 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 23.252.79.169.
威胁响应 Pipeline
发现
Analysis
Notifications
Monitoring
20 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.
