alogin.org was observed in external blocklists on 2026-10-12, with MetaMask and SEAL both listing the domain as of that date. The domain was first recorded on 2026-10-11, expanding the timeline for review.
Recorded Evidence
VirusTotal checked alogin.org on 2026-10-11, documenting 7 detections from 92 scanners. OTX referenced the domain in 4 pulses as of 2026-10-12. PhishDestroy internally listed alogin.org, and its registration with Cloudflare, Inc. was recorded on 2026-05-18. MetaMask and SEAL blocklists included the domain on 2026-10-12.
Interpretation
PhishDestroy contains an internal listing for alogin.org, which records its inclusion in a curated security dataset. VirusTotal provides a quantitative measurement of detections from multiple scanners, reflecting automated analysis. OTX documents the domain in several pulses, representing collections of security intelligence. The evidence spans several sources and dates, allowing for comparison across intelligence platforms.
Recommended Actions
Retain the VirusTotal detection record for alogin.org to compare with future scanner results. Preserve the PhishDestroy internal listing and OTX pulse references for ongoing review. Monitor entries from MetaMask and SEAL blocklists to track changes in external intelligence. Keep all dated source records to support future contextual analysis.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
저장된 은신 플래그
아직 스캔되지 않았습니다
TDS 지문 인식 실시간 확인
이 패널이 열려 있을 때 PhishDestroy 스캐너에서 실행되는 7개의 케이타로 지문과 크롤러 대 브라우저 비교 결과.
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.
기술 · 2 identified
Cloudflare
CDN
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
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-12 10:04:18 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 188.114.97.1.
위협 대응 Pipeline
발견
Analysis
Monitoring
10 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.
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)
