VirusTotal
14 / 91 engine detections
Mở báo cáoLừa đảo: weatherbot.finance — Hoạt động được biết đến lần cuối (HTTP 301). Tóm tắt bằng chứng: VirusTotal 14/91 (ChainPatrol, alphaMountain.ai, Bfore.Ai…
Phân tích chi tiết của PhishDestroy AI bên dưới được giữ bằng tiếng Anh để bảo toàn hồ sơ pháp chứng gốc.
14 / 91 engine detections
Mở báo cáoSuspicious
Mở báo cáoDBL_SPAM
Độc hại
Mở báo cáo6 community references
Mở báo cáoNo threat flag
Mở báo cáoResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
The domain weatherbot.finance is currently active and is classified as a generic phishing site. The site returns an HTTP 301 redirect and displays the page title “Just a moment…”. Its TLS certificate is issued by Let’s Encrypt (identifier YE1), indicating the use of a free certificate authority. Registration was performed through Tucows Domains Inc., and the authoritative nameservers are 1-you.njalla.no, 2-can.njalla.in, and 3-get.njalla.fo, which are associated with the Njalla privacy‑focused hosting service. DNS resolution points to IP address 95.215.19.22, which is hosted in Sweden and attributed to Materialism s.r.l. The domain appears on three public blocklists and is flagged by PhishDestroy, MetaMask, and SEAL. AlienVault OTX lists the domain in two threat‑intel pulses, confirming prior observation by the security community. VirusTotal has processed the domain with 91 antivirus engines, yet no detections have been logged; this absence does not confirm safety. No further content analysis is available beyond the observed title, so the exact phishing payload or targeted brand remains unknown. Defenders should add weatherbot.finance to URL filtering and DNS sinkhole rules, monitor for any future payload changes, and consider sharing these indicators with upstream blocklist operators. Continuous observation is advised to detect possible evolution of the phishing campaign.
Last checked
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.
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.
Danh tiếng của Edge-IP không được quy cho tên miền này.
3-get.njalla.fomx1.hostinger.compriority 5mx2.hostinger.compriority 10Location describes the IP network.
c8b75f62e8395e404a8777a673714d7b1f4aac2364ddc1ce4e694185d3a66aacSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of weatherbot.finance · checked Jul 20, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Không rõ→redirected
http_redirect
Không rõ→redirected
http_redirect
Không rõ→redirected
http_redirect
Không rõ→redirected
http_redirect
Không rõ→redirected
http_redirect
Không rõ→redirected
http_redirect
Không rõ→redirected
http_redirect
Không rõ→redirected
http_redirect
Không rõ→redirected
http_redirect
Không rõ→redirected
http_redirect
Không rõ→redirected
http_redirect
Không rõ→redirected
http_redirect
Không rõ→redirected
http_redirect
Không rõ→redirected
http_redirect
Không rõ→redirected
http_redirect
Không rõ→redirected
http_redirect
Không rõ→redirected
http_redirect
14/91 engine detections
View source6 community references
View sourceNo threat flag
View sourceweatherbot.finance
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
weatherbot.finance
Listed domains receive at least one abuse report; this entry has no retained notification history.
Nếu bạn đã nhập thông tin xác thực tài khoản, thông tin cá nhân hoặc thông tin thanh toán hoặc đã tải xuống tệp từ miền này, hãy hành động ngay lập tức. Dưới đây là các nguồn lực giúp bạn báo cáo vụ việc và bảo vệ chính mình.
Chọn quốc gia của bạn để nhận liên hệ tội phạm mạng chính thức hoặc soạn thảo đơn khiếu nại →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
weatherbot.finance)Dù bạn chưa nắm rõ tất cả các chi tiết — vẫn nên nộp báo cáo. Ngay cả những thông tin không đầy đủ cũng vẫn có ích cho công tác điều tra.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Phân tích mối đe dọa bằng cách sử dụng danh sách chặn được lưu trữ, WHOIS, DNS và bằng chứng quét công khai
Quét ngayHãy gửi các tên miền đáng ngờ đến cơ sở dữ liệu mối đe dọa của chúng tôi — để bảo vệ cộng đồng
Báo cáoCác báo cáo lừa đảo gần đây và những thay đổi về tính khả dụng được quan sát thấy
Theo dõiTheo dõi các mối đe dọa đang diễn ra hoặc phản đối danh sách này nếu bạn cho rằng đây là kết quả báo động sai
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.