VirusTotal
8 / 91
skins-fort.com was observed in a publisher-owned PhishDestroy listing as of 2026-10-05, indicating it was catalogued for internal monitoring on that date. The domain was first recorded on 2026-10-03, providing a recent timeline for its activity.
On 2026-10-05, skins-fort.com was included in the PhishDestroy internal listing. The domain was first observed on 2026-10-03. OTX recorded one pulse referencing this domain on 2026-10-05. The domain was registered through Gransy, s.r.o. on 2026-09-06.
The recorded evidence shows that skins-fort.com was noted by both OTX and the PhishDestroy internal catalogue within a short period after its registration. These observations indicate that the domain attracted attention from monitoring sources soon after becoming active. The presence in both sources reflects its inclusion in security-related records but does not provide details about its content or intent.
Review any interactions with skins-fort.com in light of its presence in the PhishDestroy internal listing and OTX pulse records. Preserve the PhishDestroy and OTX records for future reference and compare them with any new evidence as it becomes available.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: alive_content: raw=ok; http=200; via=https_proxy
Location describes the IP network.
0e0b9796db9b1d08e73ec6e1575da70f1547ac8d7840b984d27ee3b51af1c4d0Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
46.29.26.38. 9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
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
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