The domain bayekcouturefashion.shop was observed on 2026-10-11, with a PhishDestroy internal listing recorded on the same date. This domain was registered with Dynadot Inc. and is associated with the network AS199242 Malakmadze Web LLC in the US.
Recorded Evidence
PhishDestroy included bayekcouturefashion.shop in its internal listing as of 2026-10-11. The domain registration was completed on 2026-05-16 through Dynadot Inc. The network infrastructure is provided by AS199242 Malakmadze Web LLC, with the IP address located in the United States.
Interpretation
PhishDestroy records contain a listing for bayekcouturefashion.shop, documenting its presence in a publisher-owned catalogue. This measurement provides a reference point for internal security intelligence and cataloguing. The evidence spans registration and network details, offering a snapshot of the domain's technical context on the observed date.
Recommended Actions
For bayekcouturefashion.shop, preserve the PhishDestroy internal listing and registration records for future comparison. Reference the network infrastructure details in subsequent reviews to monitor any changes. Use these documented sources to inform ongoing assessment and maintain a clear record of observed evidence for the domain.
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:00:43 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-11 10:00:43 UTClast content: 2026-10-11 10:00:43 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.
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-11 01:20:43 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 46.245.239.137.
威胁响应 Pipeline
发现
Analysis
Notifications
Monitoring
9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
(US)
