Analysis of the domain bfmonrl.online indicates it is associated with phishing activity targeting Bank Of Montreal customers. The domain was registered on July 9, 2026, through a registrar based in Lithuania, with hosting infrastructure located in the Netherlands under KnownSRV Ltd. The site resolves to the IP address 185.66.140.182 and currently returns an HTTP 200 status, suggesting it is operational. The page title explicitly displays 'Bank Of Montreal,' which aligns with the observed phishing classification. Infrastructure details reveal the domain uses Let's Encrypt SSL certificates, a common choice for both legitimate and malicious sites. MX records point to the domain itself, which may facilitate email-based phishing attempts. The domain appears on at least one security blocklist, though no detections are currently recorded by major scanning engines. This absence does not confirm safety, as newly registered domains often evade initial detection. Defenders should treat this domain as active phishing infrastructure. The combination of recent registration, hosting in a high-risk provider region, and explicit branding in the page title supports this assessment. Further monitoring is recommended to track any shifts in detection status or additional blocklist inclusions. Organizations should consider preemptive blocking of this domain and its associated IP address to mitigate potential credential theft or financial fraud targeting Bank Of Montreal customers.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='bfmonrl.online', 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.
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-13 01:12:43 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-07-12 16:00:10 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-07-12 16:00:10 UTC → 2026-09-30 16:14:55 UTC · 1,920.25hmidpoint estimate ≈ 2026-08-21 16:07:32 UTC · precision very low · 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.
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-08-05 23:04:44 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.
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.
CF Radar: Malicious
Cloudflare Radar classified this domain as dga domains
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
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.
(LT)
