VirusTotal
5 / 89
ReportInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“Fortnite Rank & Locker Value Checker – Free Tool | Skinscheck”
Assessment based on the stored source evidence below. Review sources →
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
5 / 89
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
1 threat-system alert
ReportAlerts refer to the preserved scan. They do not describe the current state of the site.
4 community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
provider verdict: clean
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
stored report
View stored capture ↗ ReportA preserved page image documents what the collector received; a capture is not a safety verdict.
Analysis completed
ReportThis is the recorded automated analysis. Completion alone is not a safety verdict.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
0 external matches
DetailsA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | skinscheck.com |
malicious | Sinkholed |
Stored narrative · generated . Provider checks below retain their own observation dates.
skinscheck.com returned HTTP status 502 on 2026-10-01, a dated server-error response recorded during an HTTP check. The domain was first observed on 2026-09-14, and its registration date is recorded as 2026-09-05.
PhishDestroy's internal catalogue listed this domain, and OTX recorded four pulses on 2026-09-16. VirusTotal reported 5 detections across 89 scanners on 2026-09-18. The SSL certificate, issued by Let's Encrypt / YE2, was scanned on 2026-09-14, and PageSpeed recorded a performance score of 72 that same day.
The named sources span different observation dates, so their records describe separate points in time rather than one synchronized snapshot. OTX and VirusTotal were checked days apart, while the HTTP check on 2026-10-01 postdates the SSL and PageSpeed scans from 2026-09-14. Comparing these dated records shows how the available observations differ in timing, which matters when reading them together.
Retain the dated records for skinscheck.com, including the HTTP, OTX, VirusTotal, SSL, and PageSpeed observations, so later checks can be compared against them. When new observations are gathered, note their dates and compare them with the existing entries rather than treating any single record as current. During review, avoid submitting sensitive or personal information to skinscheck.com.
What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.
These checks have no retained result. This does not mean they passed or that a scan is running.
a.dnspod.comb.dnspod.comc.dnspod.comLocation describes the IP network.
a0c42a3c5da91c640ee034aa77bdd770f2e965647ac6d20bb194ea3f9485201dSaved 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 skinscheck.com · checked Sep 14, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='skinscheck.com', port=80): Max retries exceeded with url: / (Caused by NewConnectionError(
46.29.26.38.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
dns_inactive→Unknown
probe_inconclusive
Unknown→dns_inactive
dns_nxdomain
dns_inactive→Unknown
probe_inconclusive
Unknown→dns_inactive
dns_nxdomain
dns_inactive→Unknown
probe_inconclusive
Unknown→dns_inactive
dns_nxdomain
dns_inactive→Unknown
probe_inconclusive
Unknown→dns_inactive
dns_nxdomain
dns_inactive→Unknown
origin_unreachable · http_5xx
Unknown→dns_inactive
dns_nxdomain
dns_inactive→Unknown
origin_unreachable · http_5xx
Unknown→dns_inactive
dns_nxdomain
dns_inactive→Unknown
origin_unreachable · http_5xx
dns_inactive
dns_nxdomain
Reachable→Unavailable
Reachable
12 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.
PD-20260914-A24AEA Recipient: abuse@forticore.digital Registrar: Gname.com Pte. Ltd. (Singapore) Policy Violations: Illegal Activities section forbids phishing, fraud, fake sites, malware distribution; registrar investigates and may suspend or delete domain Applicable Laws: Computer Misuse Act 1993 §§3+, Penal Code §§415–420 (cheating), Online Criminal Harms Act (OCHA)
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