탐지를 보고하는 보안 엔진: 9. 극도의 주의를 기울이십시오 — 자격 증명이나 개인 정보를 입력하지 마십시오.
ABUSE NOTICE · 72H+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@forticore.digital.
The latest stored availability evidence still shows the domain reachable; 4 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations.
This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
aml20.com was recorded by VirusTotal with 1 detection out of 92 scanners on 2026-09-21, providing a security-related observation for the domain. The domain was also listed in the internal PhishDestroy catalogue on 2026-10-06, reflecting additional monitoring attention.
Recorded Evidence
VirusTotal reported 1 detection from 92 scanners for aml20.com on 2026-09-21. OTX had 2 pulses referencing the domain as of 2026-10-06. The internal PhishDestroy listing was recorded on 2026-10-06. A PageSpeed performance score of 72 was measured on 2026-10-06. The domain was registered through Squarespace Domains LLC on 2026-08-22.
Interpretation
The evidence for aml20.com spans security, monitoring, and web performance sources, each providing its own dated record. VirusTotal and OTX offer insight into external and community-driven observations, while the PhishDestroy listing highlights internal tracking. The PageSpeed score gives a snapshot of web performance but does not address security posture.
Recommended Actions
For aml20.com, retain the VirusTotal, OTX, and PhishDestroy source records for future reference and comparison. Continue to monitor the domain using these sources to identify any changes in detections or listings. Review the PageSpeed performance data alongside security records to inform any technical or risk assessment.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
저장된 은신 플래그
아직 스캔되지 않았습니다
마지막 은폐 스캔
스캐너 메모:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='aml20.com', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SOCK
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.
Primary outcomeDNS 비활성reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation알 수 없음Probe Inconclusive20%2026-10-11 10:08:01 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-07 10:17:08 UTClast content: 2026-10-07 10:17:08 UTCcurrent episode first observed: 2026-10-08 20:20:32 UTCobserved RIP window: 2026-10-07 10:17:08 UTC → 2026-10-08 20:20:32 UTC · 34.06hmidpoint estimate ≈ 2026-10-08 03:18:50 UTC · precision medium · basis bounded
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.
Last analyzed First positive detection Previous stored snapshot: 1 detection
alphaMountain.ai
Bfore.Ai PreCrime
CRDF
Emsisoft
Forcepoint ThreatSeeker
Fortinet
넷크래프트
SOCRadar
Webroot
사이트 성능 분석
Google PageSpeed Insights — mobile performance audit of aml20.com· checked Oct 6, 2026
72
Needs Work
Performance
FCP
4.35s
First Contentful Paint
LCP
4.43s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
102ms
Total Blocking Time
SI
5.24s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
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-06 21:01:48 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 46.29.26.38.
위협 대응 Pipeline
발견
Analysis
Notifications
Monitoring
9 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)
