Security engines reporting a detection: 7. Exercise extreme caution — do not enter credentials or personal information.
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.
fortwears.com is a suspicious domain on the PhishDestroy blocklist. Its only visible label is a generic "Loading" page title, with no brand or product named. PhishDestroy first saw it on 2026-10-06, and it was still online with live content on 2026-10-19.
How the scam works
A page titled only "Loading" gives a visitor nothing to judge it by. Its real content may appear only after a script runs or the visitor is sent elsewhere. That pattern is common among pages that later ask for logins, card details or a wallet connection, and the security flags on this domain point to that kind of risk. What a victim stands to lose depends on what the page eventually requests: credentials, payment data or access to funds. Until the domain is classified, treat any prompt it shows as untrusted.
Evidence
Seven of 92 engines on VirusTotal flagged the domain as of 2026-10-12: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft, LevelBlue and SOCRadar. That is a minority of engines, but these vendors run independent threat feeds that reached the same verdict. Spamhaus lists the domain in its DBL as a spam source. Three AlienVault OTX pulses also reference it, so other analysts have tied it to tracked activity.
Infrastructure
The domain was registered on 2026-09-23 through TuringSign Inc. d/b/a Cosmotown, just 13 days before PhishDestroy caught it. That short gap fits a site built for a brief campaign rather than an established business. It resolves to 46.29.26.38, on a network registered to M/S Robi Traders of Bangladesh but geolocated in Finland. Its free, automated Let's Encrypt certificate means the padlock in the browser says nothing about who runs the site.
What to do
If you typed a password into this site, change it everywhere you reuse it and turn on two-factor authentication. If you entered card details, contact your bank to block the card and dispute any charges. If you connected a crypto wallet or signed anything, treat that wallet as exposed and move your assets to a new one. Defenders should block fortwears.com and 46.29.26.38 at DNS and proxy level, and search logs for any traffic to them since 2026-09-23.
Issued by 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
Nameservers 3
a.dnspod.com
b.dnspod.com
c.dnspod.com
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt / YE1
Valid from
2026-09-23 07:30:12
Valid until
2026-12-22 07:30:11
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-10-11 07:02:57 UTC
Collection source
PhishDestroy collector
Certificate fingerprint224fc3ba50a2b958edadcda8dc6bba16e168d906dd214164038220b839d7a6a5Certificate names · 1 SANs
fortwears.com
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observationLive contentOrdinary HTTP content served90%2026-10-21 10:29:14 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-21 10:29:14 UTClast content: 2026-10-21 10:29:14 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.
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Infrastructure map · fortwears.com
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches4
Same favicon hash or the same page title as this host.
6 evidence signal groups linked1 stored notification recordsLast known active
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident
Recommendations & Advice for Victims
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Change all passwords — email, exchange accounts, anything that shares the same password
Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
Freeze cards if you entered banking details on the phishing site
What information should I collect for my report?
FBI guidelines
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.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including fortwears.com)
Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
FBI IC3 — Internet Crime Complaint Center (US federal reporting)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Local police — creates an official record, even if they can't act immediately
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?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Bookmark official sites — never click links from emails, DMs, or ads
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
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)
