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; 14 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.
fnsum.com is a young domain on the PhishDestroy blocklist. It shows nothing but a page titled "Loading", with no visible brand or product. PhishDestroy first saw it on 2026-10-06, and it has no assigned scheme type yet. On 2026-10-19 the site was still reported alive, but its DNS was inactive, so it may not load consistently.
How the scam works
A bare "Loading" title tells a visitor nothing about who runs the site or what it will ask for. That is the risk, because users cannot judge such a page before it reacts to them. In crypto fraud, unbranded landing domains like this often redirect visitors elsewhere or later serve a request to log in, enter a seed phrase or connect a wallet. No specific scheme has been confirmed for fnsum.com. Treat any prompt it shows for credentials, recovery words or wallet signatures as hostile.
Evidence
On 2026-10-19, VirusTotal showed 5 of 92 engines flagging the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, SOCRadar and VIPRE. That count is modest, but five unrelated vendors agreeing on a near-empty page is meaningful. Spamhaus lists the domain in its DBL as a spam domain, which points to use in unsolicited campaigns. It also appears in two AlienVault OTX threat pulses, and PhishDestroy is the blocklist carrying it.
Infrastructure
The domain was registered on 2026-09-22 through TuringSign Inc. d/b/a Cosmotown. It reached our blocklist just 14 days later, a short lifespan typical of disposable fraud domains. It is hosted in Finland on AS132359, a network registered to M/S ROBI TRADERS. It uses a free Let's Encrypt certificate, so the padlock in the browser says nothing about who operates it.
What to do
If you reached fnsum.com from a message, ad or link, close it and do not return to it. If you entered a password there, change it wherever you reuse it and turn on app-based 2FA. If you typed a seed phrase, assume the wallet is compromised and move funds to a new wallet. If you connected a wallet or signed anything, revoke the approvals through a token-approval checker. Defenders should block the domain at DNS and proxy level, search mail logs for links to it, and watch for sibling domains registered through the same registrar and network.
登録情報作成日 2026年9月22日 (28d · Very New!)—Expires 2027年9月22日
技術詳細Provenance & timestamps
初確認2026年10月6日
DOM Analysisanalyzed 2026年10月9日score 88/100
Submitted URLhttps://fnsum.com/
Favicon Hash
ケース ID
TLS証明書
発行者 Let's Encrypt / YE1· stored validity ends in 61 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
46.29.26.38
Network ASN
AS132359
Organization
M/S ROBI TRADERS
Observed location
Helsinki, FI
ネームサーバー 3
a.dnspod.com
b.dnspod.com
c.dnspod.com
Location describes the IP network.
TLS証明書
Issuer
Let's Encrypt / YE1
Valid from
2026-09-22 17:07:54
Valid until
2026-12-21 17:07:53
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-10-21 10:02:24 UTC
Collection source
PhishDestroy collector
Certificate fingerprinte1dd876ef68ae39c7b14124d1718c5d944f0c03238634d44ad137706e8b5cb0cCertificate names · 1 SANs
fnsum.com
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-21 10:07:25 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-09 10:11:33 UTClast content: 2026-10-09 10:11:33 UTCcurrent episode first observed: 2026-10-09 20:20:42 UTCobserved RIP window: 2026-10-09 10:11:33 UTC → 2026-10-09 20:20:42 UTC · 10.15hmidpoint estimate ≈ 2026-10-09 15:16:07 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.
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.
詐欺による金銭の返還を装った詐欺 — 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.
(US)
