37146.com is an impersonation phishing page. It poses as a legitimate service so visitors will trust it with their details. PhishDestroy first saw it on 2026-09-13. When checked on 2026-10-19 the domain was still alive and redirecting visitors onward, so the threat remains active.
How the scam works
Impersonation pages copy the look and wording of a service people already use. Victims then enter credentials, personal data or payment details without suspicion, and whatever they type goes straight to the operators. The page greets visitors with a plain "Welcome" title rather than a brand name, which differs from the impersonation we classified. Because the domain now redirects, the actual lure may sit on whatever destination visitors are forwarded to.
Evidence
On 2026-09-22, VirusTotal showed 13 of 89 engines flagging the domain. Detections came from established vendors including BitDefender, ESET, Kaspersky, Fortinet, G-Data, Forcepoint ThreatSeeker, alphaMountain.ai and the Vietnamese anti-scam group Chong Lua Dao. Agreement across that many unrelated engines makes a false positive unlikely. The domain also appears in three AlienVault OTX threat pulses and on the PhishDestroy blocklist.
Infrastructure
The domain is not new. It was registered on 2004-11-25, nearly 22 years before it surfaced as phishing, so age-based reputation filters may trust it more than a fresh registration. That fits an aged numeric domain that has been repurposed or resold. It is registered through Gname.com Pte. Ltd. and hosted in the US on the PEG TECH INC network. A free Let's Encrypt certificate gives it the padlock icon, which proves nothing about who runs the site.
What to do
If you entered a username and password on this site, change that password right away on the real service and anywhere else you reused it. Then turn on app-based two-factor authentication. If you submitted card or banking details, contact your bank to block the card and watch for unfamiliar charges. If you shared identity documents, stay alert for follow-up phishing that uses those details. Defenders should block 37146.com and its redirect chain at DNS and proxy level and search logs for past visits. Any users who reached the site should get credential resets.
颁发者 Let's Encrypt / YR1· stored validity ends in 9 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
38.173.42.5
Network ASN
AS398478
Organization
PEG Tech Inc
Observed location
San Jose, US
Server header
nginx
域名服务器 1
b2.share-dns.net
Location describes the IP network.
TLS 证书
Issuer
Let's Encrypt / YR1
Valid from
2026-08-01 15:08:42
Valid until
2026-10-30 15:08:41
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-20 19:02:05 UTC
Collection source
PhishDestroy collector
Certificate fingerprint84d9873a7fd1c852513e2eae9e19a827a41d515e87f7145efb3e6dcdd688914bCertificate names · 1 SANs
259tv.com
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-19 22:14:24 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-19 22:14:24 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.
trace the Received: chain: work from the bottom upward until we hit the first believable public server. In this one, your provider says it received the message from 178.91.17.110, while another preceding hop claims kiftlge via 37146.com
16pQ54sHsqQrUR2nYQsf2r7g93nwc37k2j
Hi! U
1 report filed for 37146.com (1 written by a person) · category: Sextortion · source checked
“trace the Received: chain: work from the bottom upward until we hit the first believable public server. In this one, your provider says it received the message from 178.91.17.110, while another preceding hop claims kiftlge via 37146.com
16pQ54sHsqQrUR2nYQsf2r7g93nwc37k2j
Hi! Unfortunately there is some bad news for you. Some time ago, your device was infected with my private Trojan, R.A.T. (Remote Administration Tool). If you want to find out more about it, simply use Google. My Trojan all”
— reported by Anonymous on Sep 13, 2026 · Source: ChainAbuse (TRM Labs) — full report and evidence there.
Template-based draft · optional AI wording assistance requires separate consent
AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交
After a phishing incident
针对受害者的建议与指导
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.
更改所有密码 — 电子邮件、Exchange 账户，以及任何使用同一密码的账户
启用双因素认证 使用身份验证器应用（而非短信）。禁用基于短信的恢复功能
冻结卡片 如果您在钓鱼网站上输入了银行信息
我应该为报告收集哪些信息？
联邦调查局（FBI）指南
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
当地警方 — 即使无法立即采取行动，也能留下正式记录
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
About this reportSources, observation dates and corrections
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.
(SG)
