amlbot-net.website returned an HTTP 404 status when checked on 2026-10-01, so the recorded response contained no page content at that time. The domain was first observed on 2026-09-04, and it appears in the PhishDestroy internal listing.
Recorded Evidence
OTX recorded 2 pulses for amlbot-net.website on 2026-09-13. VirusTotal reported 7 detections across 89 scanners on 2026-09-16. The domain was registered with Global Domain Group LLC on 2026-07-10, and its certificate was issued by Google Trust Services / WE1, scanned on 2026-09-14.
Interpretation
The PhishDestroy listing, OTX pulses, and VirusTotal detections are separate source records, each capturing its own observation of amlbot-net.website. Because the HTTP check and the SSL scan fall on different dates, they describe distinct moments rather than one combined measurement. These records allow comparison of what each source noted, without establishing a verdict about the domain.
Recommended Actions
For amlbot-net.website, preserve the PhishDestroy listing and the OTX pulse record so later observations can be compared against them. Retain the VirusTotal detection record and the HTTP response record as separate items for future comparison. Avoid submitting sensitive information to the domain while its recorded evidence remains in place.
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.
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不明Origin unreachableHttp 5xx20%2026-10-11 01:33:15 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-09-15 22:17:48 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.
Last analyzed First positive detection Previous stored snapshot: 2 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
SOCRadar
VIPRE
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.
Domain Status Transition2026-09-13 22:17:54 UTC
Domain state transitioned from dead to alive.
VirusTotal Detections Update2026-09-13 04:55:39 UTC
VirusTotal scanner detections updated from 0 to 2. Added scanner alerts: CRDF, SOCRadar.
Domain Status Transition2026-09-12 18:56:53 UTC
Domain state transitioned from alive to dead.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
脅威の検知
amlbot-net.website 検出され、詳細な分析のためにキューに入れられた
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)
