baurmodehaus.shop was observed with an HTTP status 200 response on 2026-10-11, which documents a successful connection at that time. The domain also appeared in the PhishDestroy internal listing, providing another recorded observation relevant to its profile.
Recorded Evidence
OTX recorded four pulses for baurmodehaus.shop on 2026-10-11. The domain was listed in the PhishDestroy internal catalogue on the same date. URLScan had a report available for the domain, also dated 2026-10-11. The registration was completed through Dynadot Inc. on 2026-04-18, and the SSL certificate was issued by Let's Encrypt / YE1.
Interpretation
The PhishDestroy internal listing contains a catalogue entry for baurmodehaus.shop, which is a type of publisher-owned record documenting its inclusion. OTX provides a measurement of pulses, which are external intelligence entries related to the domain. The HTTP status observation records a successful connection, offering technical evidence of the domain's response on the specified date. These sources together provide a snapshot of the domain's recorded context and technical infrastructure.
Recommended Actions
For baurmodehaus.shop, preserve the PhishDestroy internal listing and OTX pulse records for future comparison and review. Retain the URLScan report as an additional reference for technical evidence. Use the HTTP status record as a baseline for monitoring changes in response or accessibility over time.
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:34 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:00:34 UTClast content: 2026-10-11 10:00:34 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 00:39:45 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 162.222.90.56.
脅威対応 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)
