food-stories.ru was observed in a source record dated 2026-10-11, with an OTX check documenting 34 pulses on that date. The domain was also listed internally by PhishDestroy, which is a publisher-owned catalogue.
Recorded Evidence
OTX checked food-stories.ru on 2026-10-11 and recorded 34 pulses. PhishDestroy included the domain in its internal listing, which was also documented. The domain's registration date is recorded as 2026-01-14 with REGRU-RU as the registrar, and its IP address was observed as 185.22.155.64 in Russia by AS51659 LLC Baxet.
Interpretation
The OTX source contains pulse counts, which are a type of detection metric based on external intelligence sharing. PhishDestroy's internal listing is a publisher catalogue entry, documenting the domain as part of its records. These measurements provide a snapshot of domain-related activity and catalogue inclusion, offering context for review without combining their values into a single assessment.
Recommended Actions
For food-stories.ru, preserve the OTX pulse count record and the PhishDestroy internal listing for future comparison. Reference these source records in any subsequent review or analysis to maintain continuity and context.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
Все о моде стильных тенденциях и ярких образах для тех кто хочет быть в тренде
TLS 인증서
Certificate hostname mismatch·
발급자 Let's Encrypt / YE1· stored validity ends in 75 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
185.22.155.64
Network ASN
AS51659
Organization
LLC Baxet
Observed location
Moscow, RU
Server header
LiteSpeed
네임서버 2
ns1.justhost.ru
ns2.justhost.ru
Mail routing 1 MX record
mail.food-stories.rupriority 10
Location describes the IP network.
TLS 인증서
Issuer
Let's Encrypt / YE1
Valid from
2026-09-26 17:16:10
Valid until
2026-12-25 17:16:09
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-11 01:02:06 UTC
Collection source
PhishDestroy collector
Certificate fingerprint90e106d9ed2de97416cc4aacc238eb388dc88c51416730020ae64cafee27f4caCertificate names · 5 SANs
ftp.food-stories.ru
mail.food-stories.ru
pop.food-stories.ru
smtp.food-stories.ru
www.food-stories.ru
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:03:25 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-11 10:03:25 UTClast content: 2026-10-11 10:03:25 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 22:03:06 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 185.22.155.64.
위협 대응 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.
도메인은 계속 연결 가능하거나 액세스가 제한되어 있습니다. 향후 점검을 통해 이 관찰 내용이 업데이트될 수 있습니다.
How we investigate & report
Public scans, evidence and abuse channels
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.
(RU)
