PhishDestroy first observed slon911.cc on Oct 13, 2026. The captured page title is “KRAKEN”. Current evidence score: 53/100 (high).
One source contains a positive finding: URLQuery. URLQuery recorded 2 detections; no observation timestamp was retained. Additional recorded evidence: On Oct 13, 2026 at 13:14 UTC, VirusTotal recorded 0 detections among 92 engines; AlienVault OTX listed 4 community pulse references (not vendor detections). URLScan captured the page on Oct 13, 2026 at 12:09 UTC.
The collector marked the hostname reachable on Oct 13, 2026 at 12:09 UTC, but did not retain the HTTP response code. Latest classified outcome: unknown; cause probe inconclusive on Oct 13, 2026 at 10:09 UTC. Registration records for the domain list DYNADOT LLC as the registrar and Sep 8, 2026 as the creation date. At collection time, the hostname resolved to 104.194.149.158. The evidence archive retains 2 visual captures from PhishDestroy and URLScan. TLS metadata lists Let's Encrypt / YE2 as the certificate issuer with validity through Jan 9, 2027; checked Oct 13, 2026 at 13:02 UTC.
Stored content provides classification context alongside the positive source finding.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
저장된 은신 플래그
아직 스캔되지 않았습니다
캡처 라우팅
Local보관됨 2026-10-13 14:10:17 UTC
TDS 지문 인식 실시간 확인
이 패널이 열려 있을 때 PhishDestroy 스캐너에서 실행되는 7개의 케이타로 지문과 크롤러 대 브라우저 비교 결과.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observation알 수 없음Probe Inconclusive20%2026-10-13 12:09:30 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-13 12:09:30 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.
Values retained by the collector; long values may be shortened during collection.
Crawler & disclosure files
Site configuration evidence
3 recorded files
Files, paths and sitemap entries retained by the collector.
robots.txt
Reachable (legacy)/robots.txt
HTTP response
200
Observed at
2026-10-13 14:10:17 UTC
출처
legacy scan archive
A legacy scan recorded a successful response. The file contents were not retained.
Sitemap
Reachable (legacy)/sitemap.xml
HTTP response
200
Observed at
2026-10-13 14:10:17 UTC
출처
legacy scan archive
A legacy scan recorded a successful response. The file contents were not retained.
security.txt
Reachable (legacy)/.well-known/security.txt
HTTP response
200
Observed at
2026-10-13 14:10:17 UTC
출처
legacy scan archive
A legacy scan recorded a successful response. The file contents were not retained.
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
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-13 12:09:30 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 104.194.149.158.
위협 대응 Pipeline
발견
Analysis
Notifications
Monitoring
7 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
OTX Community References
4 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
2026년 10월 13일
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
2026년 10월 13일
Sent Report Recorded
Stored outgoing record associated with registrar DYNADOT LLC, 2 abuse contacts
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)
