VirusTotal
7 / 92 engine detections
Open report
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.
7 / 92 engine detections
Open reportScan report
Open report4 community references
Open reportprovider verdict: clean
Open reportNo threat flag
Open reportNo malicious flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
fortnw.com is on the PhishDestroy blocklist as a suspicious domain. Its page shows nothing more than the title "Loading", and we have not tied it to a specific brand or scheme. PhishDestroy first saw it on 2026-10-06. On 2026-10-19 the site was still online and serving live content, so anyone who receives a link to it can still reach it.
A page that only says "Loading" gives a visitor no reason to trust it. The real content usually appears after a script runs or a redirect fires, and that content can be a credential form, a fake wallet prompt or a download. Because several security engines already flag this domain, the safest assumption is that whatever loads is built to take something from the visitor, such as passwords, personal details or wallet access. We have not confirmed which of these it targets.
On 2026-10-12, VirusTotal showed 7 of 92 engines flagging the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, Kaspersky, LevelBlue and SOCRadar. That is a minority of engines, but these are independent vendors, including Kaspersky and Forcepoint, reaching the same conclusion about a domain that is only weeks old. Four AlienVault OTX threat pulses also reference it, so other researchers are tracking it as well. PhishDestroy is currently the only blocklist in our set that lists it.
The domain was registered on 2026-09-22 through TuringSign Inc. d/b/a Cosmotown, two weeks before PhishDestroy detected it. A domain that goes from registration to multiple threat flags this fast fits the profile of short-lived abuse infrastructure. It resolves to 46.29.26.38, an address geolocated in Finland but announced by M/S ROBI TRADERS, a network registered in Bangladesh. The site has a free Let's Encrypt certificate, so the browser padlock says nothing about whether it is legitimate.
If you opened fortnw.com, close it and do not act on any prompt that appeared after the loading screen. If you typed a password there, change it on every service where you reuse it, and turn on app-based two-factor authentication. If you connected a crypto wallet or signed anything, revoke the permissions you granted with a token-approval checker and move your funds to a fresh wallet. If you downloaded a file, delete it and run a malware scan. Security teams should block the domain and its IP at the DNS and proxy level and review logs for visits since 2026-09-22.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a11308-cab2-75ff-8fe2-fb7495311ab4 |
|---|---|
| Final url | https://fortnw.com/ |
| Status | 200 |
| Ip | 46.29.26.38 |
| Contacted IP addresses | [
"46.29.26.38"
] |
| Asns | [
"132359"
] |
| Countries | [
"TR"
] |
| Document hash | 373e47755d7eae82d8d44dfa5292f66a1287634d0a3a9c47405476f5ca14f573 |
| Globals | [
"_d5d9",
"_ad9a",
"_fa39",
"_s3d4",
"_x9f1",
"_xc0c",
"_x6f9",
"_xdee",
"_xcda",
"_xf59",
"_x5e2",
"_xcde",
"_xe8e",
"_xace",
"_x26f",
"_x597",
"_xffb",
"_x559",
"_x77c",
"_x321",
"_xe05",
"_xfca",
"_x868",
"_x844",
"_x231",
"_x83e",
"_x9d8",
"_x33e",
"_xc56",
"_xa9f",
"_x9f9",
"_xe49",
"_x40b",
"_xeac",
"_x620",
"_x886",
"_x582",
"_x2fc",
"_x498",
"_xa3f"
] |
| Cookies | [
"sil_ses",
"__Host-sil_ses",
"sil_gate",
"__Host-sil_gate"
] |
| Tls | {
"san": [
"fortnw.com"
],
"cipher": "AES_128_GCM",
"issuer": "YE2",
"subject": "fortnw.com",
"protocol": "TLS 1.3",
"valid_to": "2026-12-21T05:34:54Z",
"valid_from": "2026-09-22T05:34:55Z"
} |
| Domain age days | 480 |
| Apex age days | 480 |
| Tls age days | 14 |
| Tls valid days | 89 |
| Requests | 4 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 81,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"content-type": "text/html; charset=utf-8"
} |
Observed: · Retrieved:
| Uuid | 19aec3d8-9de1-4922-ae92-c3c6865db610 |
|---|---|
| Final url | https://fortnw.com/ |
| Status | 200 |
| History | [
{
"url": "https://fortnw.com/",
"status": 200
}
] |
| DOM structure hash | bc948235e9efeda3c8d176de53504109efd904a0c8a0ba260d9c0d5db04d3bb4 |
| Document hash | b211db2a087a43d405eba31689e653e559454f855e66b78af43613baee5fb6d7 |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "fortnw.com",
"type": "A",
"value": "46.29.26.38"
}
] |
| Dnssec valid | false |
| Ip | 46.29.26.38 |
| Registration record | {
"registrar": "TuringSign Inc. d/b/a Cosmotown",
"created": "2026-09-22T05:55:19Z",
"updated": "2026-09-22T06:08:11Z",
"expires": "2027-09-22T05:55:19Z",
"nameservers": [
"a.dnspod.com",
"b.dnspod.com",
"c.dnspod.com"
]
} |
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 53,
"malicious": 4,
"suspicious": 1,
"undetected": 34
} |
|---|---|
| Vendor labels | {
"SOCRadar": "phishing",
"LevelBlue": "phishing",
"Gridinsoft": "suspicious",
"alphaMountain.ai": "phishing",
"Forcepoint ThreatSeeker": "phishing"
} |
| Reputation | 0 |
| Categories | {
"alphaMountain.ai": "Phishing, Newly Registered (alphaMountain.ai)"
} |
| Registrar | TuringSign Inc. d/b/a Cosmotown |
| Created | 2026-09-22T05:55:19Z |
| Expires | 2027-09-22T05:55:19Z |
| Updated | 2026-09-22T06:08:11Z |
| First seen | 2025-06-14T09:04:21Z |
| DNS records | [
{
"ttl": 21600,
"type": "NS",
"value": "b.dnspod.com"
},
{
"ttl": 180,
"type": "SOA",
"rname": "domainadmin.dnspod.com",
"value": "a.dnspod.com"
},
{
"ttl": 21600,
"type": "NS",
"value": "a.dnspod.com"
},
{
"ttl": 21600,
"type": "NS",
"value": "c.dnspod.com"
},
{
"ttl": 600,
"type": "A",
"value": "46.29.26.38"
}
] |
| Dns at | 2026-10-12T18:12:05Z |
| Jarm | 27d40d40d00040d00042d43d00041df04c41293ba84f6efe3a613b22f983e6 |
| Certificate | {
"san": [
"fortnw.com"
],
"issuer": "Let's Encrypt / YE2",
"serial": "5b348e839476478f3bb0c5b5165745fb961",
"sha256": "4ab702d9f1b0786b7fff7238f5914b2e73cdfc63b9800c699a4415c0d0f931ef",
"subject": "fortnw.com",
"valid_to": "2026-12-21T05:34:54Z",
"valid_from": "2026-09-22T05:34:55Z"
} |
| Registration record | {
"registrar": "TuringSign Inc. d/b/a Cosmotown",
"registrar_iana_id": "1509",
"registrar_url": "http://www.cosmotown.com",
"created": "2026-09-22T05:55:19Z",
"updated": "2026-09-22T06:08:11Z",
"expires": "2027-09-22T05:55:19Z",
"status": [
"ok"
],
"nameservers": [
"a.dnspod.com",
"b.dnspod.com",
"c.dnspod.com"
],
"dnssec": "unsigned"
} |
| Registry data | {
"status": [
"active"
],
"events": {
"last changed": "2026-09-22T05:55:19Z",
"registration": "2026-09-22T05:55:19Z",
"registrar expiration": "2027-09-22T05:55:19Z",
"last update of RDAP database": "2026-10-10T18:09:40Z"
}
} |
a.dnspod.comb.dnspod.comc.dnspod.comLocation describes the IP network.
4ab702d9f1b0786b7fff7238f5914b2e73cdfc63b9800c699a4415c0d0f931effortnw.comSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of fortnw.com · checked Oct 6, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
2→3
1→2
Unknown→live_content
content_served
Reachable
No threat flag
View source7/92 engine detections
View source4 community references
View sourcePD-20261006-6DE48F
Page captured
View sourcefortnw.com
View sourceReported by 1 community member, first seen Dec 24, 2025
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
fortnw.com
PD-20261006-6DE48F Recipient: abuse@forticore.digital If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
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.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
fortnw.com)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.