escorter.info was referenced in a PhishDestroy internal listing on 2026-10-11, providing a dated catalogue entry for the domain. Additional intelligence sources recorded observations on the same date, contributing to a technical snapshot of escorter.info.
Recorded Evidence
OTX documented 34 pulses for escorter.info as of 2026-10-11. The PhishDestroy internal listing included the domain on 2026-10-11. URLScan made a report available for escorter.info on 2026-10-11. The domain was registered with NameCheap, Inc. on 2026-09-04, and its SSL certificate was issued by Google Trust Services / WE1.
Interpretation
PhishDestroy contains a catalogue listing for escorter.info, which is a record of its inclusion in an internal database. OTX provides a measurement of community-contributed intelligence entries, offering insight into how the domain has been referenced in external sources. The evidence from these sources documents the domain’s presence and technical context as of their respective dates, allowing for comparison across different types of records.
Recommended Actions
For escorter.info, it is advisable to preserve the OTX pulse records and the URLScan report for future reference and comparison. Retaining the PhishDestroy internal listing will support ongoing review against other catalogue entries. These records can be periodically compared with new intelligence sources to track changes in the domain’s recorded profile.
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:28 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:00:28 UTClast content: 2026-10-11 10:00:28 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 23:39:11 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 188.114.96.3.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
8 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)
