VirusTotal
3 / 90
ReportInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“Scanana - AI Crypto Portfolio Tracker”
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.
3 / 90
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.
2 external matches
DetailsA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
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.
80/100
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | plural-upright.defex.cc |
malicious | Sinkholed |
Stored narrative · generated . Provider checks below retain their own observation dates.
Stored evidence for scanana.fun: VirusTotal recorded 3 detections among 90 scanners on 2026-09-06. That ratio reproduces the stored check in its original units and is not converted into another measure. MetaMask and SEAL appear as named external blocklist observations for scanana.fun. Each item in this report remains at the scope supplied by its dated source record.
VirusTotal records 3 detections among 90 scanners in the stored snapshot dated 2026-09-06. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-09-06 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.
MetaMask and SEAL are recorded as named external blocklist observations for scanana.fun in the snapshot dated 2026-09-06. The stored MetaMask and SEAL blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains scanana.fun as a publisher record. That PhishDestroy record is counted separately from the MetaMask and SEAL external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.
The record first observed scanana.fun on 2026-09-05. The MetaMask and SEAL blocklist snapshot is dated 2026-09-06 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-09-03. A URLScan reference was stored on 2026-09-05 as a dated artifact for review. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.
The source stores 170.75.160.175 as the observed address in this record. The registration date for scanana.fun is recorded as 2026-09-03. The SSL issuer is recorded as Let's Encrypt / YR2 in the snapshot dated 2026-09-05. The stored ASN observation records 174 and Cogent Communications, LLC in this record. The observed server header is recorded as nginx in this record. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.
The scanana.fun record states that VirusTotal recorded 3 detections among 90 scanners on 2026-09-06. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-09-06. PhishDestroy remains a separate publisher catalogue entry in the stored record. The observed address field in this record contains 170.75.160.175. The supported conclusion is bounded to the exact stored observations for scanana.fun. Any statement beyond those source values would require additional dated material.
Avoid submitting sensitive information to scanana.fun during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain scanana.fun as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and MetaMask and SEAL blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to scanana.fun. The stored record does not justify extending that rule to 170.75.160.175 or to other infrastructure records.
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.
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
dns1.regway.comdns2.regway.comdns3.regway.comdns4.regway.comLocation describes the IP network.
ff0c0e0ea2046414a55d19dffa37c02b43cd57353004eb0b8e274aef8d54b1f9www.scanana.funSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.scanana.funDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of scanana.fun · checked Sep 5, 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='scanana.fun', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SO
170.75.160.175.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
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
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
14 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-20260904-FC6880 Recipient: abuse-contact@publicdomainregistry.com Policy Violations: Illegal Activities: Active phishing operation targeting victims Fraud & Deception: Impersonation of legitimate services Identity Theft: Collection of credentials under false pretenses Applicable Laws (RU): Russian Criminal Code Article 159.6 (Computer Fraud) Russian Criminal Code Article 272 Federal Law on Information Russian law criminalizes computer fraud and unauthorized access to information systems. Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
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