Skip to security report
Analytics Dashboard
Domain security and threat intelligence
fortgs.com favicon

fortgs.com

In short

fortgs.com is a phishing page detected by PhishDestroy on 2026-10-22. Risk: critical (85/100). Registrar: NiceNIC. Status: Last known active. Hosting: Fast Zone IT. VirusTotal: 4/92 engines flag it. Google Safe Browsing flags it. Do not enter credentials or connect a wallet.

Registrar
NiceNIC
Resolved IP
193.187.110.10
Registered
Oct 12, 2026
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation
Risk signals
VirusTotal detections: 4/92 Spamhaus DBL: DBL_SPAM Young domain: 9 days old Google Safe Browsing: threat flag recorded
Oct 22, 2026
API
This domain has been flagged as malicious
Security engines reporting a detection: 4. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
4 / 92
engine detections
Google Safe Browsing
Flagged
Page captures
4
open gallery
Domain age
9 days
Source evidenceVirusTotal 4 / 92 · Google Safe Browsing: flagged 6 sources

VirusTotal

4 / 92 engine detections

Open report

Google Safe Browsing

Threat flag recorded

Open report

Spamhaus DBL

DBL_SPAM

OTX

no community references

Open report

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Network Security Intelligence Registrar context
Registrar context NiceNIC
Stored registration data identifies NICENIC INTERNATIONAL GROUP CO., LIMITED (IANA 3765) as the registrar. PhishDestroy maintains separate NiceNIC abuse-report research; registrar association is contextual and is not an independent detection for this domain.
NiceNIC Verdict Full Investigation

Analysis

Critical
VirusTotal
4 / 92
Page captures
4
Page captures Source results Registration record

PhishDestroy threat report

Overview

PhishDestroy added fortgs.com to its internal blocklist as a suspicious domain. The site returned HTTP 200 with the recorded title “Loading”. The domain first appeared on PhishDestroy’s list on 2026-10-22 after Google Safe Browsing reported a social‑engineering threat.

How the scam works

The detections suggest the site may be used for generic social‑engineering attacks, such as tricking visitors into revealing credentials or personal data. No specific phishing page, wallet drainer, or malware delivery was observed on the captured snapshot.

Evidence

VirusTotal scanned the domain on 2026-10-16 and recorded four detections from 92 engines, including one malicious label (SOCRadar) and three suspicious labels (Fortinet, Gridinsoft, alphaMountain.ai). Google Safe Browsing flagged the domain as SOCIAL_ENGINEERING on 2026-10-22. urlscan.io captured the page on 2026-10-14; its overall verdict was clean, but its machine‑learning engine assigned a malicious score of 94. No external blocklists reported the domain and OTX listed zero pulses as of 2026-10-22.

Infrastructure

The domain was registered on 2026-10-12 with NICENIC INTERNATIONAL GROUP CO., LIMITED and uses the nameservers a.dnspod.com, b.dnspod.com, and c.dnspod.com. The recorded DNS A record pointed to 193.187.110.10, which was associated with Fast Zone IT in Turkey, and the TLS certificate observed was issued by Let’s Encrypt / YE2 and was valid until 2027-01-10. Open ports observed include 22, 80, and 443, and DNSSEC is not enabled.

What to do

Visitors should avoid entering any credentials or personal information on the site and, if they have already done so, change affected passwords and monitor accounts for unusual activity. Organizations can block the domain at the firewall or web proxy, and review logs for connections to 193.187.110.10. Continue to rely on up‑to‑date Google Safe Browsing and similar threat feeds for automated protection.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportStored capture screenshotCloudflare Radar screenshot (2026-10-22T13:20:38Z)URLScan screenshot (2026-10-22T13:19:35Z)URLScan capture reportVirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

URLScan · 2026-10-14T17:35:45Z

Observed: · Retrieved:

Uuid
01a13b7b-e7de-7629-877c-d5ee55158556
Final url
https://fortgs.com/
Status
200
Ip
193.187.110.10
Contacted IP addresses
[
    "193.187.110.10"
]
Asns
[
    "153947"
]
Countries
[
    "TR"
]
Document hash
6b7597a872f8aa225c3535869dee1f645f5630720958321a71c00b8d19f30223
Globals
[
    "_d87a",
    "_aa39",
    "_f747",
    "_s269",
    "_x801",
    "_xd1f",
    "_xbae",
    "_x3af",
    "_x5e2",
    "_x0bd",
    "_x197",
    "_x894",
    "_xf04",
    "_x00e",
    "_xb7e",
    "_x3d2",
    "_xfc7",
    "_xeb1",
    "_xa6f",
    "_x0b7",
    "_x246",
    "_x2b7",
    "_xb5b",
    "_x25a",
    "_x9d7",
    "_xf1b",
    "_xb4e",
    "_x896",
    "_x37f",
    "_x8fe",
    "_x78d",
    "_x72b",
    "_xf38",
    "_x88a",
    "_xf21",
    "_xa00",
    "_x6b3",
    "_x837",
    "_x117",
    "_x9f4"
]
Cookies
[
    "sil_ses",
    "__Host-sil_ses",
    "sil_gate",
    "__Host-sil_gate"
]
Tls
{
    "san": [
        "fortgs.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE2",
    "subject": "fortgs.com",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-10T15:28:10Z",
    "valid_from": "2026-10-12T15:28:11Z"
}
Domain age days
2
Apex age days
2
Tls age days
2
Tls valid days
89
Requests
4
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 94,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "content-type": "text/html; charset=utf-8"
}
Cloudflare Radar · 2026-10-22T13:20:38Z

Observed: · Retrieved:

Uuid
44137cdd-373b-41b7-9d51-0ae140bb7e69
Final url
https://fortgs.com/
Status
200
History
[
    {
        "url": "https://fortgs.com/",
        "status": 200
    }
]
DOM structure hash
bc948235e9efeda3c8d176de53504109efd904a0c8a0ba260d9c0d5db04d3bb4
Document hash
dde065034afcaba36633b0eee87a75e27a75570aa7d054a252224845ec2c263a
Domain risks
[
    "Newly Seen Domains",
    "Security Risks"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "fortgs.com",
        "type": "A",
        "value": "193.187.110.10"
    }
]
Dnssec valid
false
Ip
193.187.110.10
Registration record
{
    "registrar": "NICENIC INTERNATIONAL GROUP CO., LIMITED",
    "created": "2026-10-12T16:20:52Z",
    "updated": "2026-10-12T16:24:01Z",
    "expires": "2027-10-12T16:20:52Z",
    "nameservers": [
        "a.dnspod.com",
        "b.dnspod.com",
        "c.dnspod.com"
    ]
}
VirusTotal · 2026-10-16T19:54:31Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 52,
    "malicious": 1,
    "suspicious": 3,
    "undetected": 36
}
Vendor labels
{
    "Fortinet": "spam",
    "SOCRadar": "phishing",
    "Gridinsoft": "suspicious",
    "alphaMountain.ai": "spam"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Spam, Suspicious (alphaMountain.ai)"
}
Registrar
NICENIC INTERNATIONAL GROUP CO., LIMITED
Created
2026-10-12T16:20:52Z
Expires
2027-10-12T16:20:52Z
Updated
2026-10-12T16:24:01Z
First seen
2026-10-12T18:01:16Z
DNS records
[
    {
        "ttl": 600,
        "type": "A",
        "value": "193.187.110.10"
    },
    {
        "ttl": 180,
        "type": "SOA",
        "rname": "domainadmin.dnspod.com",
        "value": "a.dnspod.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "b.dnspod.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "c.dnspod.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "a.dnspod.com"
    }
]
Dns at
2026-10-16T19:56:03Z
Jarm
27d40d40d00040d00042d43d00041df04c41293ba84f6efe3a613b22f983e6
Certificate
{
    "san": [
        "fortgs.com"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "5c1e7419ea806e90d3f90b97e44d156ee4e",
    "sha256": "c39f0ca70bf0079794a6a194abe174f339757529c553f1a24572ec6927ddff1d",
    "subject": "fortgs.com",
    "valid_to": "2027-01-10T15:28:10Z",
    "valid_from": "2026-10-12T15:28:11Z"
}
Registration record
{
    "registrar": "NICENIC INTERNATIONAL GROUP CO., LIMITED",
    "registrar_iana_id": "3765",
    "registrar_url": "https://nicenic.com",
    "created": "2026-10-12T16:20:52Z",
    "updated": "2026-10-12T16:20:52Z",
    "expires": "2027-10-12T16:20:52Z",
    "status": [
        "clientDeleteProhibited",
        "clientTransferProhibited"
    ],
    "nameservers": [
        "a.dnspod.com",
        "b.dnspod.com",
        "c.dnspod.com"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "client delete prohibited",
        "client transfer prohibited"
    ],
    "events": {
        "expiration": "2027-10-12T16:20:52Z",
        "registration": "2026-10-12T16:20:52Z",
        "registrar expiration": "2027-10-12T16:20:52Z",
        "last update of RDAP database": "2026-10-12T16:20:52Z"
    }
}
Website checks · 2026-10-22T13:24:02Z
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "fortgs.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-10-22T13:18:03Z",
    "first": "2026-10-12T20:39:04Z",
    "changes": 2,
    "days_archived": 3,
    "scans_per_day": 0.21,
    "avg_page_bytes": 242701
}
Page title and metadata
{
    "title": "Loading",
    "robots": "noindex,nofollow"
}
Trackers
{
    "requests": 1
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 223,
        "tls": 55,
        "wait": 212,
        "connect": 36,
        "download": 294
    },
    "response_ms": 820
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        22,
        80,
        443
    ]
}
Carbon
{
    "bytes": 2301958,
    "co2_grams": 0.0842,
    "cleaner_than": 1
}
Dns server
{
    "ns": [
        {
            "ip": "43.130.172.75",
            "host": "a.dnspod.com"
        },
        {
            "ip": "43.161.3.75",
            "host": "b.dnspod.com"
        },
        {
            "ip": "43.134.249.75",
            "host": "c.dnspod.com"
        }
    ],
    "zone": "fortgs.com"
}
Location
{
    "ip": "193.187.110.10",
    "asn": "153947",
    "org": "Fast Zone IT",
    "city": "Istanbul",
    "country": "TR"
}
Ssl
{
    "issuer": "Let's Encrypt / YE2",
    "subject": "fortgs.com"
}
DNS records
{
    "A": [
        "193.187.110.10"
    ],
    "NS": [
        "a.dnspod.com",
        "c.dnspod.com",
        "b.dnspod.com"
    ],
    "SOA": "{\"nsname\": \"a.dnspod.com\", \"hostmaster\": \"domainadmin.dnspod.com\", \"serial\": 1791911964, \"refresh\": 3600, \"retry\": 180, \"expire\": 1209600, \"minttl\": 180}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "193.187.110.10",
    "family": 4
}
Registration record
{
    "registrar": "NICENIC INTERNATIONAL GROUP CO., LIMITED",
    "created": "2026-10-12T16:20:52Z",
    "updated": "2026-10-12T16:24:01Z",
    "expires": "2027-10-12T16:20:52Z",
    "status": [
        "clientDeleteProhibited https://icann.org/epp",
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "a.dnspod.com",
        "b.dnspod.com",
        "c.dnspod.com"
    ]
}
HTTP headers
{
    "headers": []
}

Questions about fortgs.com

Is fortgs.com legit?

No. PhishDestroy classifies fortgs.com as a phishing page (risk: critical, 85/100); it was first detected on 2026-10-22. VirusTotal: 4/92 engines flag it. Google Safe Browsing flags it. Listed on Spamhaus DBL. Treat the site as unsafe.

Is fortgs.com safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on fortgs.com. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used fortgs.com?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 4 captures

Primary capture 1 / 4
SourcePrimary capture
Recorded2026-10-22 13:13 UTC
StateStored capture
HTTP status at archiveHTTP 200
Final URLhttps://fortgs.com/
Position1 / 4
Open capture Wayback Download

Domain details

Domain
Google Safe Browsing Flagged Social engineering checked Oct 22, 2026
IP Reputation abuse score 0/100 0 reports checked Oct 22, 2026
Registrar NiceNIC RU(RU) PhishDestroy Investigation
Abuse contact["abuse@nicenic.net", "6eb609d996e182a6s@"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for fortgs.com →
RegistrationCreated Oct 12, 2026 (9d · Very New!) — Expires Oct 12, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 22, 2026
DOM Analysisanalyzed Oct 22, 2026score 81/100
Submitted URLhttps://fortgs.com/
Favicon Hash
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 79 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
193.187.110.10
Network ASN
AS153947
Organization
Fast Zone IT
Observed location
Istanbul, TR

Nameservers 3

  • a.dnspod.com
  • b.dnspod.com
  • c.dnspod.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-10-12 15:28:11
Valid until
2027-01-10 15:28:10
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintc39f0ca70bf0079794a6a194abe174f339757529c553f1a24572ec6927ddff1d
Certificate names · 1 SAN
  • fortgs.com

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

viewdns.info · 193.187.110.10rapiddns.io
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

4 / 92 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
Fortinet
Gridinsoft
SOCRadar
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of fortgs.com · checked Oct 22, 2026

77
Needs Work
Performance
FCP
4.04s
First Contentful Paint
LCP
4.08s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
15ms
Total Blocking Time
SI
4.04s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: https://fortgs.com/
Loading
Response
HTTP 200
HTML body
2.14 MB
Compressed
583.5 KB
Links
3 internal · 0 external
Selected response headers
Content-Type: text/html; charset=utf-8
Cache-Control: no-store
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 8
alt-svc
clear
Cache-Control
no-store
Content-Encoding
gzip
Content-Length
668482
Content-Type
text/html; charset=utf-8
Date
Thu, 22 Oct 2026 13:19:40 GMT
Vary
Accept-Encoding
x-edge-action
captcha

Values retained by the collector; long values may be shortened during collection.

Archived
Stored observation history1

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

Recorded activity

3 entries
  1. Google Safe Browsing

    Threat flag recorded

    View source
  2. VirusTotal

    4/92 engine detections

    View source
  3. Added to PhishDestroy

    fortgs.com

    View source

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

fortgs.com

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 4 det. ChainPatrol URLQuery Google SB Flagged SSL Labs Stored certificate dates valid CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked 0 stored notification records Last known active

Listed domains receive at least one abuse report; this entry has no retained notification history.

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.

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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

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 fortgs.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)
  • Europol — European cybercrime reporting (EU)
  • 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

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

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
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.

Request a correction or appeal How PhishDestroy works
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/fortgs.com"
  title="PhishDestroy threat report for fortgs.com"
  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>