amlrescan.top returned HTTP status 502 on 2026-10-01, according to the recorded HTTP check. The same source data shows the domain was first observed on 2026-09-04, roughly four weeks earlier.
Recorded Evidence
The VirusTotal check on 2026-09-13 recorded 6 detections across 89 scanners. OTX recorded 2 pulses on 2026-09-13. PhishDestroy's internal listing marked amlrescan.top as present, and the registration date was 2026-08-02 with Global Domain Group LLC as registrar. The HTTP check on 2026-10-01 returned status 502.
Interpretation
The VirusTotal detections and OTX pulses are separate source metrics gathered on the same calendar date, so they should be read individually rather than combined into a single verdict. The HTTP 502 describes only the response recorded on that date and does not establish what the domain serves at other times. The gap between the 2026-08-02 registration date and the 2026-09-04 first observation is a matter of record only.
Recommended Actions
Preserve the VirusTotal record for amlrescan.top and the OTX record for amlrescan.top as separate source documents. Compare the HTTP status record against the PhishDestroy internal listing in separate reviews. Retain the registration record and the first-observation record for amlrescan.top so future checks can be compared against them.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='amlrescan.top', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-11 01:00:14 UTC
RDAP registration未知
Observed timelinecurrent episode first observed: 2026-09-30 16:14:55 UTCfirst terminal observation: 2026-09-30 16:14:55 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.
Last analyzed First positive detection Previous stored snapshot: 1 detection
alphaMountain.ai
Bfore.Ai PreCrime
CRDF
Forcepoint ThreatSeeker
Fortinet
SOCRadar
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.
VirusTotal Detections Update2026-09-13 04:57:26 UTC
VirusTotal scanner detections updated from 1 to 6. Added scanner alerts: CRDF, Forcepoint ThreatSeeker, Fortinet, SOCRadar, alphaMountain.ai.
Domain Status Transition2026-09-12 23:04:50 UTC
Domain state transitioned from alive to dead.
威胁响应 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.
已捕获威胁
amlrescan.top 已检测到并排入队，待进行全面分析
2026年9月4日
Spamhaus DBL
Spamhaus DBL recorded DBL_PHISH
2026年9月13日
Cloudflare Radar Report
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)
