VirusTotal
7 / 91
Interpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“Jindouyun AI”
Assessment based on the stored source evidence below. Review sources →
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@dynadot.com.
The latest stored availability evidence still shows the domain reachable; 15 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
signallx.com — Hoạt động được biết đến lần cuối (HTTP 200). Mạo danh thương hiệu: MetaMask; Loại lừa đảo: Impersonation. Tóm tắt bằng chứng: VirusTotal 7/91 (BitDefender, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft); URLQuery 3 det.; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 100/100. Nhà đăng ký: DYNADOT.
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.
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
7 / 91
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
3 det.
Alerts refer to the preserved scan. They do not describe the current state of the site.
4 community references
Báo cáoCommunity publication references, not a vendor verdict or evidence of a common operator.
provider verdict: suspicious
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
báo cáo được lưu trữ
Báo cáo A preserved page image documents what the collector received; a capture is not a safety verdict.
Phân tích hoàn tất
Báo cáoThis is the recorded automated analysis. Completion alone is not a safety verdict.
Checked; no threat flag recorded
Báo cáoA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Stored narrative · generated . Provider checks below retain their own observation dates.
Stored evidence for signallx.com: VirusTotal recorded 1 detections among 91 scanners on 2026-09-29. That ratio reproduces the stored check in its original units and is not converted into another measure. MetaMask and SEAL appear as named external blocklist observations for signallx.com. Each item in this report remains at the scope supplied by its dated source record.
VirusTotal records 1 detections among 91 scanners in the stored snapshot dated 2026-09-29. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-09-29 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.
MetaMask and SEAL are recorded as named external blocklist observations for signallx.com in the snapshot dated 2026-09-29. The stored MetaMask and SEAL blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains signallx.com as a publisher record. That PhishDestroy record is counted separately from the MetaMask and SEAL external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.
The record first observed signallx.com on 2026-09-29. The MetaMask and SEAL blocklist snapshot is dated 2026-09-29 and remains a separate event in the stored timeline. A stored HTTP status 200 was observed for signallx.com on 2026-09-29. The HTTP status 200 dated 2026-09-29 records a single response for later comparison. The registration date is separately recorded as 2026-09-26. A URLScan reference was stored on 2026-09-29 as a dated artifact for review. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.
For signallx.com, the registrar field records DYNADOT LLC; this is kept as an exact source value. The source stores 188.114.97.3 as the observed address in this record. The registration date for signallx.com is recorded as 2026-09-26. The SSL issuer is recorded as Let's Encrypt / YE1 in the snapshot dated 2026-09-29. The stored ASN observation records 13335 and Cloudflare, Inc. in this record. The observed server header is recorded as cloudflare in this record. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.
The signallx.com record states that VirusTotal recorded 1 detections among 91 scanners on 2026-09-29. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-09-29. PhishDestroy remains a separate publisher catalogue entry in the stored record. For signallx.com, the registrar field records DYNADOT LLC; this remains separate from the other source fields. The observed address field in this record contains 188.114.97.3. The supported conclusion is bounded to the exact stored observations for signallx.com. Any statement beyond those source values would require additional dated material.
Avoid submitting sensitive information to signallx.com during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain signallx.com as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and MetaMask and SEAL blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to signallx.com. The stored record does not justify extending that rule to 188.114.97.3 or to other infrastructure records.
Các dữ liệu quan sát đã lưu trữ về sự so sánh giữa trình thu thập dữ liệu và trình duyệt đối với máy chủ này, cùng với việc kiểm tra dấu vân tay thời gian thực dành cho các hệ thống phân phối lưu lượng theo phong cách Keitaro.
cloudflareGhi chú về máy quét: alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare
Danh tiếng của Edge-IP không được quy cho tên miền này.
amy.ns.cloudflare.combob.ns.cloudflare.comsmtp.secureserver.netpriority 0mailstore1.secureserver.netpriority 10Location describes the IP network.
0fe3032b1d9ac81f616ed5dbc237100908d7489b283fde47ab5141d59548d6e7Saved 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 signallx.com · checked Sep 29, 2026
188.114.97.3.13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
79 tên miền tương tự đã lưu
PD-20260929-6D77B4 Recipient: abuse@dynadot.com Registrar: Dynadot LLC / Dynadot Inc (United States) Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
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
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