Stored registration data identifies Trustname / Fewmoretaps OÜ (IANA 4318) as the registrar. PhishDestroy maintains a separate registrar investigation; that material is contextual and is not an independent detection for this domain.
amlhtx.com returned an HTTP status 403 during a check on 2026-10-01, indicating that access was denied at that time. The domain was first observed on 2026-09-05, and its registration is recorded with Fewmoretaps OU d/b/a Trustname.com as of 2026-06-22.
Recorded Evidence
On 2026-10-01, amlhtx.com produced a 403 HTTP status in a check. VirusTotal, as of 2026-09-18, reported 4 detections out of 89 scanners for this domain. OTX recorded 4 pulses on 2026-09-11. The domain is included in the PhishDestroy internal listing. Its SSL certificate, issued by Google Trust Services / WE1, was scanned on 2026-09-05.
Interpretation
These records show that amlhtx.com was monitored by several sources, each providing distinct observations on separate dates. The HTTP status only reflects the response at the time of the check, while VirusTotal and OTX offer independent security-related signals. The presence in the PhishDestroy internal listing and the SSL scan provide additional context for technical and security review.
Recommended Actions
Retain the HTTP 403 response record and the PhishDestroy listing for amlhtx.com as reference points. Compare future VirusTotal and OTX results to these observations to track any changes. The SSL certificate and registration details should be preserved for ongoing monitoring and verification.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
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:30:18 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-11 10:30:18 UTClast content: 2026-10-11 10:30:18 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.
기술 · 3 identified
Cloudflare Browser Insights
AnalyticsRUM
Cloudflare Browser Insights is a tool that measures the performance of websites from the perspective of users.
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-09-05 00:44:36 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 104.21.48.139.
위협 대응 Pipeline
발견
Analysis
Monitoring
11 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.
Web Archive
Preserved in 웨이백 머신 — historical evidence archived
도메인은 계속 연결 가능하거나 액세스가 제한되어 있습니다. 향후 점검을 통해 이 관찰 내용이 업데이트될 수 있습니다.
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.
(BY)
PhishDestroy Investigation
