ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@forticore.digital.
The latest stored availability evidence still shows the domain reachable; 13 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.
fortcheck.cam is on the PhishDestroy blocklist as a suspicious domain. It does not show any recognizable brand. Its only visible label is the page title "Loading", a placeholder that reveals nothing about what the site offers. PhishDestroy first flagged it on 2026-10-06. On 2026-10-19 the server was still answering requests, but the domain's DNS no longer pointed to active content.
How the scam works
No specific scheme or impersonated brand has been confirmed for fortcheck.cam. A blank "Loading" page means the content is either served later or only to some visitors, so the risk sits in whatever appears next. Treat any prompt it shows as untrusted, whether that is a login form, a wallet connection request, a download or a "verification" step. The vendor categories and the spam listing point to a domain used in unsolicited campaigns, where victims typically arrive through a link in a message rather than by searching.
Evidence
On 2026-10-11, VirusTotal showed 6 of 92 engines flagging the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft and SOCRadar. That is a minority of engines, but they are independent vendors reaching the same conclusion. Spamhaus lists the domain on its DBL as a spam domain, which ties it to bulk messaging. It also appears in three AlienVault OTX threat pulses, so other researchers have linked it to tracked malicious activity.
Infrastructure
The domain was registered on 2026-08-15 through Gname.com Pte. Ltd., about seven weeks before PhishDestroy flagged it. That short gap is typical of throwaway domains bought for a single campaign. It resolves to 46.29.26.38, an address announced by a network registered to M/S Robi Traders in Bangladesh, while the server itself is geolocated in Finland. Its certificate is a free, automatically issued Let's Encrypt certificate, so the padlock in the browser says nothing about whether the site can be trusted.
What to do
Do not open fortcheck.cam or follow messages that link to it. If you entered a password there, change it on the real service and on any account that shares it, then turn on two-factor authentication. If the site made you download a file, delete it and run a full malware scan. If you shared personal or payment details, watch your accounts for unfamiliar activity. Defenders should block the domain and 46.29.26.38 at DNS, proxy and mail gateways, and search logs for earlier contact with either.
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-20 10:06:47 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-09 10:07:12 UTClast content: 2026-10-09 10:07:12 UTCcurrent episode first observed: 2026-10-09 20:20:42 UTCobserved RIP window: 2026-10-09 10:07:12 UTC → 2026-10-09 20:20:42 UTC · 10.23hmidpoint estimate ≈ 2026-10-09 15:13:57 UTC · precision medium · 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.
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.
(UA)
