Is shots-vote.fun a scam? 5/100

shots-vote.fun

Is it safe to use? An external threat listing named this site as malicious when the evidence was captured. Do not pay or share personal details with this site.

Download PDF Check another site How we score
Ask your AI about this report

Pick your AI assistant. It opens in a new tab with a question about this report already written, and you can ask it anything from there.

Only this public report is shared. Your AI app's own privacy terms apply, and its answers are its own: the report is TrustSniffer's assessment. Connect TrustSniffer to your AI to check sites from the chat.

Verdict

An external threat listing named this site as malicious when the evidence was captured. Do not pay or share personal details with this site.

5 OUT OF 100
Critical Risk

shots-vote.fun shows critical-risk indicators.

Sensitive Interaction Risk
  • Sensitive Interaction Risk: This label is given when the overall risk is high. The captured page did not ask for a password, card number or other sensitive details; if it ever does, entering them here could be unsafe.

Assessed 2026-11-14 by automated analysis. Evidence confidence 64%.

How the site describes itselfCloudflare bot-verification interstitial for shots-vote.fun. No site content was captured, so the site's purpose and legitimacy cannot be assessed.

Evidence status and limitations

Evidence completeness: CompleteThis says whether every check on the site was recorded as finished. All of them were.

  • One external source flagged this site when the evidence was captured (a threat-intelligence listing from a feed TrustSniffer monitors (phishing, the site itself as the source, last seen 2026-10-26)). No second source confirms it. The alert is from the evidence captured on 2026-11-14 and is treated as unconfirmed. On its own the alert would limit the score to at most 49; the threat-listing ceiling holds it at 5, because the listing names the site itself as the source.
  • The site showed automated visitors only a bot-protection challenge, so its own pages could not be read. The behaviour findings below measured that challenge page, not the site behind it.
  • The real-world operator identity was not independently verified.

How to read these numbers

The trust score runs from 0 to 100, higher is safer. 5/100 rates the evidence found, not the probability that the site is a scam.

Evidence confidence (64%) measures how much of TrustSniffer's evidence set this site produced: the page reading, the browser sandbox, the web archive, the registration record and the reputation services. It falls when a check returns nothing, as listed above, and it does not change the score.

At a glance

The checks that decide most of this verdict.

What limits the scoreThreat-listing ceilingA threat-intelligence feed TrustSniffer monitors listed this site itself as the source of a threat when the evidence was captured (last seen 2026-10-26), and that listing caps the score. The business-model ceiling (at most 70) and the unconfirmed alert ceiling (at most 49) also apply, but the score is below them.Risk
Malware enginesNone malicious; 1 marked it suspiciousVirusTotalWatch
Google Safe BrowsingNot listedGoogleClear
Abuse reports on the CDN edge address0% confidenceAbuseIPDB, 0 reports; this is the record of the CDN edge address, not of the server behind it, which was not observedNoted
Domain age9 months oldRegistered 2026-02-28Watch
Web archiveArchived since 20261 snapshot; the archive has almost no record of this site, which counted against itWatch
CertificateEncrypted connectionIssued by YE2Noted

The page as captured

https://shots-vote.fun/
Screenshot of the shots-vote.fun homepage captured during the TrustSniffer assessment
What shots-vote.fun served when TrustSniffer captured it on 2026-11-14. The page may look different now.

Key findings

  • Automated classification: Sensitive Interaction Risk.
  • Domain age: less than 1 year at capture (registered 2026-02-28).
  • Public web-archive history exists since 2026.
  • No security engine marked this domain as malicious; some marked it suspicious, which TrustSniffer does not count as a listing.

Full analysis

Overview

The address shots-vote.fun returned only a security-verification interstitial when it was captured on 14 November 2026. No products, pricing, forms, legal pages or other content were visible, so the page does not show what the site offers or who operates it. Its apparent purpose is unknown. Its name suggests a voting or polling service, but nothing on the captured page supports or explains that.

Scam/Impersonation Risk

A threat-intelligence listing classed this site as phishing, with the site itself in the role of actor, and last saw that listing on 26 October 2026. A single listing source supports this. It is not described as corroborated, and it did not exist as a finding about page content, because the captured page held none. The score is held down by the threat-listing ceiling, and the site is therefore assessed at critical risk. Only one external engine returned a suspicious result and none returned a malicious one. Google Safe Browsing did not list the domain. Neither of those results offsets the listing. No brand impersonation and no conflicting legal identities were detected, and no operator could be connected to a real-world person or organisation. The page's behaviour also produced scored findings. It sent a high volume of requests to other hosts, and some of those went to destinations TrustSniffer does not recognise. These findings sit alongside the listing and are not ordinary background activity. The page also displays "Verification successful" and "Performing security verification" together, a state the page reader flagged as inconsistent.

Evidence
  • Threat-intelligence listing (phishing class, site as actor), last seen 2026-10-26.
  • Homepage behaviour across three runs: 36 requests sent to other hosts, 3 of them to destinations TrustSniffer does not recognise.
  • Homepage text: the captured page shows both "Verification successful. Waiting for shots-vote.fun to respond" and "Performing security verification".
  • Registration record: domain registered 2026-02-28 (259 days at capture); web archive holds 1 snapshot, first and last 2026-02-28 (span 0 days).

Regulatory Verification Notes

On the homepage, the only page read, no licence, registration number, company name, terms, privacy notice or contact channel was present. These are gaps on the page read. The business type could not be established, so no sector-specific licensing expectation applies. No third-party broker or regulatory record matched this domain. The domain was registered through PDR Ltd. d/b/a PublicDomainRegistry.com, and its registration record is complete. The site's transport encryption is a domain-validated certificate. That shows an encrypted connection and says nothing about who operates the site or whether it is legitimate.

Evidence
  • Homepage: no contact channel and no terms or privacy disclosure on the page read.
  • Registration record: registrar PDR Ltd. d/b/a PublicDomainRegistry.com; created 2026-02-28, expires 2027-02-28.
  • TLS certificate issued by YE2 (DV), valid until 2027-01-20.A TLS certificate is what puts the padlock and https:// in your browser and encrypts the connection. "YE2" is the name of the authority that issued it. DV (domain validated) means the issuer only confirmed who controls the domain name, not which person or company runs the site.
  • Hosting: served from AS13335 (Cloudflare, Inc., US).

What to Verify Next

The first step is to establish how the address was reached. If it arrived by message, advertisement or social post, the sender's identity should be checked through an independent route. The operator of the sender's account should not be taken from the message itself. Any claim about who runs the site should be treated as unconfirmed until it is checked against an independent source, because the captured page names no operator. Official contact channels for any organisation the site is said to represent should be confirmed through an offline route. A fresh capture that gets past the bot check would show whether the site serves any content of its own. Until then, nothing on the site can be relied upon.

Evidence
  • Homepage: the captured text is only a bot-check message, with no operator, product or contact detail to cross-check.
  • Threat-intelligence listing: last seen 2026-10-26, which is why provenance is treated as failed.
  • Registration record: domain only 259 days old at capture, with no archive history before 2026-02-28.

Summary Verdict

The site is assessed at critical risk. A phishing-class threat listing in which the site is the actor holds the score down, and the evidence contains nothing that offsets it. No operator identity could be established, and the captured page showed no content from which legitimacy could be judged. The site should not be regarded as safe or established.

Infrastructure Integrity

The site resolves to four Cloudflare edge addresses, and the origin server was not observed. Cloudflare's bot-verification service sits in front of the site. This is neutral. It neither raises nor lowers risk, and it says nothing about who operates the site or what it serves. The host address has no abuse reports on record, and the TLS certificate was valid at capture. Neither point offsets the threat listing.

Closing Assessment

The site should not be visited or interacted with. If the address arrived in an unsolicited message or advertisement, that message should be treated as suspect and not acted on. The domain should not be entered in any workflow until independent evidence of the operator's identity exists.

Written analysis generated 2026-11-14 by the TrustSniffer Analysis Engine from the evidence in this report.

What the analysis found

7 findings contributed to this verdict, raised by governance, history in the web archive, page content and behaviour in a sandbox.

01 Governance

  • TrustSniffer limits the score of a site whose operator it could not verify, according to the kind of site it appears to be; here that limit is at most 70, and the score is below it, so it does not set the score.Governance rule:gov_business_model_cap
  • A threat-intelligence feed TrustSniffer monitors listed this site itself as the source of a threat when the evidence was captured (last seen 2026-10-26), and that listing caps the score.Governance rule:gov_active_threat_listing

02 History in the web archive

  • The web archive has almost no record of this domain, which fits a site that is new.History in the web archive rule:ARCH_PEN_YOUNG_AND_SPARSE

03 Page content

  • The browser raised a warning while loading the page.Page content rule:PAGE_BROWSER_FLAGS_SUSPICIOUS
  • The page has no description for search engines, which established sites usually provide.Page content rule:PAGE_SEO_MISSING_META

04 Behaviour in a sandbox

  • The page made many background requests to other domains while it was open.Behaviour in a sandbox rule:BEHAV_EXTERNAL_XHR_HEAVY
  • The page sent data to other domains many times while it was open.Behaviour in a sandbox rule:BEHAV_EXTERNAL_POSTS_HEAVY
  • Many of the responses the page received looked generated rather than served normally.Behaviour in a sandbox rule:BEHAV_SYNTHETIC_RESPONSES_HIGH

How related findings were counted

Some findings above describe the same underlying fact, and some are weak on their own. TrustSniffer counts each such group under one shared limit, so one fact is not counted several times and weak signals stay bounded.

  • Third-party connections: 2 findings share one limit, because they all measure one fact: the page loads files from other hosts. Together they stayed under the limit.

Identity verification

StatusUNVERIFIED

The operator behind the site could not be connected to a real-world brand or person. What the page shows, if anything, is listed below; none of it was independently checked.

  • org:Just a moment
  • on_site_identity

What TrustSniffer observed

First-party facts recorded during the assessment of shots-vote.fun.

  • The request stayed on shots-vote.fun. It was not redirected to another domain. Clear
  • Registered through PDR Ltd. d/b/a PublicDomainRegistry.com. Noted
  • DNS for this domain is served by cloudflare.com, across 2 name servers. Noted
  • The domain is registered until 2027-02-28. Noted
  • The earliest public archive of this site is from 2026-02-28. Watch
  • It is hosted on CLOUDFLARENET, a network registered in US. Noted

Domain intelligence

RegistrarPDR Ltd. d/b/a PublicDomainRegistry.com
HostingCLOUDFLARENET - Cloudflare, Inc.
Network registered inUS
Server IP2606:4700:3033::ac43:bf1c (a CDN edge address; the server behind it was not observed)
Name serversgalilea.ns.cloudflare.com, lewis.ns.cloudflare.com
CDN / edge networkDetected (cloudflare)
Resolved IP addresses4
Edge IP addresses4
Likely origin IP addresses0
SSL issuerYE2
SSL expiry2027-01-20
Domain age259 days (registered 2026-02-28)
Domain expiry2027-02-28
Archive first seen2026-02-28 (259 days before capture)
Archive snapshots1
ReputationVirusTotal: 0 malicious, 1 suspicious | AbuseIPDB (CDN edge address, not the host): 0% confidence, 0 reports | Google Safe Browsing: 0 matches

About this assessment

A trust score summarises the evidence TrustSniffer could collect about shots-vote.fun at a point in time: domain registration and age, hosting and certificate, the content the site served, and third-party reputation feeds. A high score means the signals were consistent with a legitimately operated site; a low or critical score means several risk patterns were present. It is a starting point for your own judgement, not a guarantee and not a legal finding. There is no human rating and no user review in it. A site can change after it is assessed.

Already paid or signed in? Do this now

Act fast. The sooner your bank knows, the better the chance of stopping the payment.

  1. Call your bank or card company now. Use the number on the back of your card. Ask them to stop or reverse the payment.
  2. Paid with crypto? Contact the exchange or wallet app you sent it from today. Give them the address you paid.
  3. Signed in or shared a password? Change it now, on every site where you use it, and turn on two-step sign-in.
  4. Report it to the police. In the US you can also report at reportfraud.ftc.gov and ic3.gov. In other countries, use your national police or fraud reporting service.
  5. Keep the evidence. Save screenshots, receipts, emails and chat messages. Your bank and the police will ask for them.
  6. Ignore anyone who offers to get your money back for a fee. These "recovery" offers are often a second scam.

Looking for the real site? Type the company name into a search engine yourself, or use the web address printed on your card, bill or letter. Do not use links from messages or ads.

Common questions about shots-vote.fun

Is shots-vote.fun a scam?

TrustSniffer's assessment of shots-vote.fun found strong scam indicators. It scored 5 out of 100 on 2026-11-14, which is the critical-risk band. The specific signals are listed in the evidence above.

Is shots-vote.fun safe to use?

An external threat listing named this site as malicious when the evidence was captured. Do not pay or share personal details with this site.

What is the trust score of shots-vote.fun?

shots-vote.fun scored 5 out of 100 on 2026-11-14, which places it in the critical-risk band. The score is built from the domain's age and registration history, its hosting and certificate, the content of the site itself, and third-party reputation data. There is no human rating and no user review in it.

Download this report as PDF Free, no account needed. Create one to keep a history of the sites you check.
Questions about this report? Ask your AI

Pick your AI assistant. It opens in a new tab with a question about this report already written, and you can ask it anything from there.

Only this public report is shared. Your AI app's own privacy terms apply, and its answers are its own: the report is TrustSniffer's assessment. Connect TrustSniffer to your AI to check sites from the chat.

By AminRez, Founder & Lead Security Researcher, TrustSniffer
Produced by the TrustSniffer Analysis Engine · assessed 2026-11-14 · how we assess · report a mistake