The domain aiostory.com returned an HTTP status 200 on 2026-10-11, documenting a successful response on that date. Additionally, the domain was observed in the PhishDestroy internal listing, which is a publisher-owned catalogue.
Recorded Evidence
On 2026-10-11, the HTTP status source recorded a 200 code for aiostory.com. The PhishDestroy internal listing included the domain as of 2026-10-10. OTX referenced aiostory.com in 31 pulses on 2026-10-11. The domain was registered with Cloudflare, Inc. on 2025-12-30, and its SSL certificate was issued by Google Trust Services / WE1, as scanned on 2026-10-11.
Interpretation
The PhishDestroy internal listing contains a record of aiostory.com, documenting its inclusion in a publisher-managed catalogue. The HTTP status source measures the domain’s response code, which is a technical indicator of server communication on the recorded date. OTX provides a count of pulses referencing the domain, which reflects external intelligence entries but does not specify their nature. These sources together offer a snapshot of technical and intelligence-related observations.
Recommended Actions
For aiostory.com, retain the HTTP status 200 record and the PhishDestroy internal listing entry for future comparison. Preserve the OTX pulse count as a reference point for external intelligence mentions. Use these dated records to monitor any changes in technical responses or catalogue listings over time.
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: StaleRegistration: Unknown
Latest HTTP observationコンテンツ公開中Ordinary HTTP content served90%2026-10-10 23:02:16 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-10 23:02:16 UTClast content: 2026-10-10 23:02:16 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 21:51:10 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 172.67.173.91.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
7 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)
