Skip to security report

fortsk.best

Availability last checked First listed Oct 6, 2026 VirusTotal analysed Oct 11, 2026 UTC

PhishDestroy verdict Critical 93/100 evidence score

Based on 2 recorded source signals. The score is a heuristic over stored detections, not a probability or confidence level.

View evidence
Availability · last observation Unverified

Current reachability is unverified

· Source: HTTP probe

Reachability is not a safety rating.

Key evidence

  • VirusTotal detections: 7/92
  • Spamhaus DBL: DBL_SPAM
Registrar
DYNADOT
Registered
Sep 15, 2026
IP
46.29.26.38
Abuse reports
1 sent
Stored capture 1 of 3 · Oct 6, 2026 UTC · Primary capture OpenAll capturesWayback
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; 7 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.

Elapsed since first report
7 days
Reports sent
1
Latest case ID
PD-20261006-550FB8
Current status
Observed active at latest stored check

Evidence

Source checks and detection results recorded for this domain, with the time each was observed.

Source evidence

8 sources

VirusTotal

7 / 92

Report

Spamhaus DBL

DBL_SPAM

URLQuery

Report stored; detailed verdict not recorded

Report

OTX

3 community references

Report

CF Radar

provider verdict: suspicious

Report

URLScan capture

stored report

Stored URLScan capture preview
Report

URLScan verdict

Analysis completed

Report

Google Safe Browsing

Checked; no threat flag recorded

Report
Detailed resultsVirusTotal vendor list · written summary · threat-intel cross-reference · cloaking analysis

Evidence summary

Stored written summary, generated Oct 7, 2026. It is not updated when source results change.

Assessment

The domain fortsk.best was recorded returning an HTTP 200 response on 2026-10-07, demonstrating that a server responded successfully to a request on that date. A PageSpeed performance score of 75 was also measured, indicating moderate technical optimization at the time.

Read full summary

Recorded Evidence

On 2026-10-07, OTX recorded three pulses for fortsk.best. VirusTotal reported 3 detections out of 92 scanners on 2026-10-06. The domain was listed in the PhishDestroy internal catalogue. The page title was observed as "Loading" on 2026-10-06, and a urlscan report was available on the same date. Registration was completed through DYNADOT LLC on 2026-09-15, and the SSL certificate was issued by Let's Encrypt / YE1 as of 2026-10-07.

Interpretation

These source observations provide a technical and security-related profile of fortsk.best within a brief period. The presence of OTX pulses and VirusTotal detections shows that the domain has been subject to external review, while the PageSpeed score and HTTP status reflect its server's configuration. The PhishDestroy internal listing and urlscan report availability further contribute to the documented record of this domain.

Recommended Actions

To further assess fortsk.best, review the urlscan report and compare its findings with the OTX and VirusTotal records. Preserve the available source records for future reference and ongoing comparison. Consider the PhishDestroy internal listing when determining next steps regarding this domain.

VirusTotal Analysis

7 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 3 detections
alphaMountain.ai
Bfore.Ai PreCrime
CRDF
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
SOCRadar
Detection-evasion analysis

Cloaking and traffic-distribution check

Not yet scanned No crawler-versus-browser difference has been recorded yet

Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.

Stored cloaking flag
Not yet scanned
Last cloaking scan

Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='fortsk.best', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SO

Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Waiting

Domain & infrastructure

Registrar DYNADOT · registered Sep 15, 2026 · IP 46.29.26.38 · TLS Let's Encrypt / YE1

Domain details

Domain
URLScan Verdict Analysis completed score 0 report ↗
IP Reputation abuse score 9/100 2 reports PhishingOpen ProxyPort Scan checked Oct 7, 2026
OTX Tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar DYNADOT US(US)
RegistrationCreated Sep 15, 2026 (29d · Very New!) — Expires Sep 15, 2027
Technical detailsProvenance & timestamps
First DetectedOct 6, 2026
DOM Analysisanalyzed Oct 9, 2026score 93/100
Submitted URLhttps://fortsk.best/
Favicon Hash
Case ID
ICANN OVERSIGHT

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

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.

Accountability draft Nothing is sent automatically.

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
Server header
ESF

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-15 12:08:49
Valid until
2026-12-14 12:08:48
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-10-14 16:02:42 UTC
Collection source
PhishDestroy collector
Certificate fingerprint38cc11d44d73f333d4526318fc3354bd0b725db8bbe63edf50d36ae2369894c4

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of fortsk.best · checked Oct 6, 2026

75
Needs Work
Performance
FCP
4.22s
First Contentful Paint
LCP
4.29s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
108ms
Total Blocking Time
SI
4.22s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor

Captures

3 stored captures

Stored Capture · 3 captures

TLS Certificate
Hostname coverage not recorded · Issued by Let's Encrypt / YE1 · stored validity ends in 60 days

Reports & history

1 abuse report sent · first listed Oct 6, 2026 · detection timeline

Latest Classified Outcome 2026-10-14 20:21:26 UTC

Primary outcome DNS inactive reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Unknown Probe Inconclusive 20% 2026-10-14 10:05:57 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-08 22:00:34 UTC last content: 2026-10-08 22:00:34 UTC current episode first observed: 2026-10-09 20:20:42 UTC observed RIP window: 2026-10-08 22:00:34 UTC → 2026-10-09 20:20:42 UTC · 22.34h midpoint estimate ≈ 2026-10-09 09:10:38 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.

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
  1. VirusTotal Detections Update 2026-10-07 03:20:56 UTC
    VirusTotal scanner detections updated from 2 to 3. Added scanner alerts: CRDF.
  2. Threat First Observed 2026-10-06 21:11:49 UTC
    Domain ingestion complete. Initial state is marked as alive pointing to IP 46.29.26.38.

Threat Response Pipeline

Discovery
Analysis
Notifications
Monitoring

11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Sent Report Recorded
Stored outgoing record associated with registrar DYNADOT LLC, 2 abuse contacts
abuse@forticore.digitalabuse@dynadot.com
Oct 6, 2026
How we investigate & report

Public scans, evidence and abuse channels

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.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

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.

Get help

Official reporting channels, a complaint draft, and listing review

Were You Affected by This Site?

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.

Europol
Find the official reporting channel for your EU country
National police directory
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 →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself

Tools & export

External lookups, JSON / PDF export, API and embed code
Analyze on destroy.tools Run a fresh external analysis of fortsk.best (opens in a new tab)

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261006-550FB8 Recipient: abuse@forticore.digital
PDF notice generated Notice text archived (291 chars)
Abuse notice text as sent to the provider
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
Deep Analysis
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/fortsk.best"
  title="PhishDestroy threat report for fortsk.best"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing