VirusTotal
7 / 92 engine detections
Raporu aç
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.
Oltalama: fortwears.com — Bilinen son aktif (HTTP 200). Kanıt özeti: VirusTotal 7/92 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft)…
Özgün adli kaydı korumak için aşağıdaki ayrıntılı PhishDestroy AI analizi İngilizce bırakılmıştır.
7 / 92 engine detections
Raporu açSuspicious
Raporu açDBL_SPAM
Scan report
Raporu aç3 community references
Raporu açNo threat flag
Raporu açNo malicious flag
Raporu açResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
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.
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.
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.
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.
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.
Stored page, network and scanner observations, grouped by source and observation time.
Gözlemlenen: · Retrieved:
| Uuid | 01a1136e-aa8e-72b2-bdaa-87db1823bb59 |
|---|---|
| Final url | https://fortwears.com/ |
| Durum | 200 |
| Ip | 46.29.26.38 |
| Contacted IP addresses | [
"46.29.26.38"
] |
| Asns | [
"132359"
] |
| Countries | [
"TR"
] |
| Document hash | e7183554186abbb51a0a44c16629c61ebbe46687f586ae1184354ae560eed85c |
| Globals | [
"_d0a0",
"_a309",
"_f563",
"_s9fc",
"_x393",
"_x30a",
"_xade",
"_xbd2",
"_x988",
"_x03c",
"_x546",
"_x3d2",
"_x53c",
"_xfc6",
"_x631",
"_x27d",
"_x617",
"_x9d3",
"_x5eb",
"_x528",
"_xbfc",
"_x942",
"_x4bb",
"_x275",
"_x34e",
"_x8ae",
"_xded",
"_xf47",
"_x477",
"_xca6",
"_x6e1",
"_x2ea",
"_xfb4",
"_x01f",
"_x06b",
"_xb21",
"_xc1d",
"_xcbc",
"_xe13",
"_x8fd"
] |
| Çerezler | [
"sil_ses",
"__Host-sil_ses",
"sil_gate",
"__Host-sil_gate"
] |
| Tls | {
"san": [
"fortwears.com"
],
"cipher": "AES_128_GCM",
"issuer": "YE1",
"subject": "fortwears.com",
"protocol": "TLS 1.3",
"valid_to": "2026-12-22T07:30:11Z",
"valid_from": "2026-09-23T07:30:12Z"
} |
| Domain age days | 2800 |
| Apex age days | 2800 |
| Tls age days | 13 |
| Tls valid days | 89 |
| Requests | 4 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 49,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"content-type": "text/html; charset=utf-8"
} |
Gözlemlenen: · Retrieved:
| Uuid | 504b7cef-fa77-4ce1-ba8e-e540f6ef3741 |
|---|---|
| Final url | https://fortwears.com/ |
| Durum | 200 |
| History | [
{
"url": "https://fortwears.com/",
"status": 200
}
] |
| DOM structure hash | bc948235e9efeda3c8d176de53504109efd904a0c8a0ba260d9c0d5db04d3bb4 |
| Document hash | 295f20e2230ccf76f7ce4160d73ed8aeace1780e9ea650cfbebfee3920a11b1e |
| Domain risks | [
"Newly Seen Domains",
"Security Risks",
"New Domains"
] |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "fortwears.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-23T08:09:28Z",
"updated": "2026-09-23T08:24:15Z",
"expires": "2027-09-23T08:09:28Z",
"nameservers": [
"a.dnspod.com",
"b.dnspod.com",
"c.dnspod.com"
]
} |
Gözlemlenen: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 49,
"malicious": 5,
"suspicious": 2,
"undetected": 36
} |
|---|---|
| Vendor labels | {
"CRDF": "malicious",
"Fortinet": "spam",
"SOCRadar": "phishing",
"LevelBlue": "phishing",
"Gridinsoft": "suspicious",
"alphaMountain.ai": "phishing",
"Forcepoint ThreatSeeker": "phishing"
} |
| Reputation | 0 |
| Categories | {
"alphaMountain.ai": "Phishing, Spam (alphaMountain.ai)"
} |
| Kayıt kuruluşu | TuringSign Inc. d/b/a Cosmotown |
| Oluşturuldu | 2026-09-23T08:09:28Z |
| Expires | 2027-09-23T08:09:28Z |
| Updated | 2026-09-23T08:24:15Z |
| First seen | 2026-09-23T11:13:11Z |
| DNS records | [
{
"ttl": 21600,
"type": "NS",
"value": "a.dnspod.com"
},
{
"ttl": 21600,
"type": "NS",
"value": "b.dnspod.com"
},
{
"ttl": 180,
"type": "SOA",
"rname": "domainadmin.dnspod.com",
"value": "a.dnspod.com"
},
{
"ttl": 600,
"type": "A",
"value": "46.29.26.38"
},
{
"ttl": 21600,
"type": "NS",
"value": "c.dnspod.com"
}
] |
| Dns at | 2026-10-12T02:00:36Z |
| Jarm | 27d40d40d00040d00042d43d00041df04c41293ba84f6efe3a613b22f983e6 |
| Certificate | {
"san": [
"fortwears.com"
],
"issuer": "Let's Encrypt / YE1",
"serial": "6e5e2199c683b1acca223e547b0cec4d6a4",
"sha256": "224fc3ba50a2b958edadcda8dc6bba16e168d906dd214164038220b839d7a6a5",
"subject": "fortwears.com",
"valid_to": "2026-12-22T07:30:11Z",
"valid_from": "2026-09-23T07:30:12Z"
} |
| Registration record | {
"registrar": "TuringSign Inc. d/b/a Cosmotown",
"registrar_iana_id": "1509",
"registrar_url": "http://www.cosmotown.com",
"created": "2026-09-23T08:09:28Z",
"updated": "2026-09-23T08:24:15Z",
"expires": "2027-09-23T08:09:28Z",
"status": [
"ok"
],
"nameservers": [
"a.dnspod.com",
"b.dnspod.com",
"c.dnspod.com"
],
"dnssec": "unsigned"
} |
| Registry data | {
"status": [
"active"
],
"events": {
"last changed": "2026-09-23T08:09:28Z",
"registration": "2026-09-23T08:09:28Z",
"registrar expiration": "2027-09-23T08:09:28Z",
"last update of RDAP database": "2026-10-12T02:00:25Z"
}
} |
a.dnspod.comb.dnspod.comc.dnspod.comLocation describes the IP network.
224fc3ba50a2b958edadcda8dc6bba16e168d906dd214164038220b839d7a6a5fortwears.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 fortwears.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.
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
4→5
Bilinmiyor→live_content
content_served
3→4
2→3
Bilinmiyor→live_content
content_served
No threat flag
View source7/92 engine detections
View source3 community references
View sourcePD-20261007-F33C0D
Page captured
View sourcefortwears.com
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
fortwears.com
PD-20261007-F33C0D Recipient: abuse@forticore.digital Hesap kimlik bilgilerini, kişisel bilgileri veya ödeme bilgilerini girdiyseniz ya da bu alan adından bir dosya indirdiyseniz hemen harekete geçin. Aşağıda olayı bildirmenize ve kendinizi korumanıza yardımcı olacak kaynaklar bulunmaktadır.
resmi siber suç iletişim bilgileri veya şikayet taslağı oluştur → almak için ülkenizi seçin.
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 ↗
fortwears.com)Tüm ayrıntıları bilmeseniz bile — yine de şikayette bulun. Kısmi bilgiler de soruşturmalara yardımcı olmaktadır.
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
Saklanan engelleme listesi, WHOIS, DNS ve genel tarama kanıtlarını kullanarak tehdit analizi
Şimdi TaraŞüpheli alan adlarını tehdit veritabanımıza bildirin — topluluğu koruyun
BildirSon kimlik avı raporları ve gözlemlenen kullanılabilirlik değişiklikleri
İzleCanlı tehditleri izleyin veya bunun yanlış bir uyarı olduğunu düşünüyorsanız bu kayda itiraz edin
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.