ABUSE NOTICE · 24H+ 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; 26 hours 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.
bakkerdirect.shop was observed in a PhishDestroy internal listing on 2026-10-10, documenting its inclusion in a publisher-owned catalogue. The domain was registered with Dynadot Inc. on 2026-05-11, which provides context for its timeline and infrastructure.
Recorded Evidence
PhishDestroy internal listing recorded bakkerdirect.shop on 2026-10-10. The domain's registration date with Dynadot Inc. is 2026-05-11. SSL certificate issuance by Let's Encrypt / YE1 was scanned on 2026-10-10, showing encryption was enabled at that time.
Interpretation
PhishDestroy contains a listing for bakkerdirect.shop, which is a catalogue measurement documenting its presence on a specific date. The evidence includes registration, SSL, and catalogue records, offering a snapshot of the domain's technical and listing context without combining metrics or assigning a verdict. The timeline allows comparison of registration and catalogue inclusion.
Recommended Actions
For bakkerdirect.shop, retain the PhishDestroy listing and SSL scan records for ongoing review. Compare future catalogue entries and SSL scans to these source records to track changes or updates. Preserve registration details for reference in any subsequent assessments or technical reviews.
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:24 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-11 10:00:24 UTClast content: 2026-10-11 10:00:24 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-10 16:52:03 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 23.252.79.189.
威胁响应 Pipeline
发现
Analysis
Notifications
Monitoring
10 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)
