Is votingchoicemonitor.netlify.app safe? TrustSniffer's low-trust assessment: 46/100

votingchoicemonitor.netlify.app
Download PDF Check another site How we score

Verdict

Several risk patterns were present. Do not send money or personal details until you have verified this business another way.

46 OUT OF 100
Low Trust

votingchoicemonitor.netlify.app is low-trust and potentially risky.

Sensitive Interaction Risk Governance Risk

Assessed 2026-10-22 by automated analysis. Classification confidence 75%.

Evidence status and limitations

Evidence completeness: Not recorded

  • The real-world operator identity was not independently verified.
  • Module-level completeness metadata is unavailable for this legacy report.

At a glance

The checks that decide most of this verdict.

Malware engines2 flagged itVirusTotalRisk
Google Safe BrowsingNot listedGoogleClear
Abuse reports on the host0% confidenceAbuseIPDB, 2 reports; shared hosting inflates reportsClear
Domain age1 months oldMost scam domains are under a year oldRisk
Web archive435 snapshots435 snapshotsClear
CertificateEncrypted connectionIssued by DigiCert Global G2 TLS RSA SHA256 2020 CA1Noted

The page as captured

https://votingchoicemonitor.netlify.app/
Screenshot of the votingchoicemonitor.netlify.app homepage captured during the TrustSniffer assessment
What votingchoicemonitor.netlify.app served when TrustSniffer captured it on 2026-10-22. The page may look different now.

Key findings

  • Automated classification: Sensitive Interaction Risk.
  • Domain age: less than 1 year (registration continuity).
  • At least one reputation service TrustSniffer consulted had flagged this domain at assessment time.

Full analysis

Overview

This website is a subdomain published on a public application-hosting platform. Its name suggests a voting-related monitoring or tracking service. The analysis could not extract substantive product, pricing or operator content from the homepage, so its purpose and business model cannot be characterised beyond the name and the hosting arrangement. The site is young and shares its parent platform's domain space.

Scam/Impersonation Risk

Contradictory signals are present, and they drive a cautionary posture. Several independent reputation engines currently classify the site as malicious or suspicious, and the site also carries an external blacklist listing. These are the decisive findings, and the site's protective hosting and valid certificate cannot offset them. No brand impersonation, phishing page or conflicting legal identities were confirmed from page content, and no suspicious contact address was observed. The detections nonetheless point to a site that may be used to host harmful or deceptive content. A freshly created domain on a free hosting namespace is a pattern commonly seen in short-lived, disposable campaigns. Two abuse reports exist against an edge address in the hosting provider's shared network. These apply to shared provider infrastructure rather than to this site specifically, so they are discounted and not treated as evidence against it. In the behavioural sandbox, the homepage made no outbound data transfers, showed no hidden forms, wallet prompts or clipboard manipulation, and showed no cloaking. That is a mitigating observation about the captured page, but it does not outweigh the external detections. Evidence:

  • Two reputation engines rated the site malicious and one rated it suspicious across the homepage scan, alongside an additional external blacklist listing.
  • The domain is roughly 40 days old (about 0.11 years), registered in 2026, which is a very recent registration.
  • 435 archive snapshots were recorded within a single year (2026), all from the current year, so there is no long history to offset the detections.
  • The sandbox ran three homepage sessions, all returning stable HTTP 200 with zero external requests and zero console errors.

Regulatory Verification Notes

The captured homepage did not yield identifiable legal-entity, licensing or registration disclosures, and the real-world operator could not be independently connected to any known organisation or individual. This is a verification limitation and does not by itself indicate fraud. Here it sits alongside the external threat detections, which is why it cannot be treated as benign. No third-party broker or regulatory-database entry matched the site, so there is no external reputational or licensing context in either direction. The site's TLS certificate is organisation-validated, but the named subject is the hosting platform and not the site's operator. The certificate therefore confirms secure transport and does not identify who runs the site. Evidence:

  • The homepage shows no company name, licence or registration number in the content captured.
  • The site is served from AS16509 (AMAZON-02, Amazon.com, Inc., US).
  • The TLS certificate was issued by DigiCert Global G2 TLS RSA SHA256 2020 CA1 at OV level, with subject organisation Netlify, Inc and validity to 2027-03-19.
  • No matching broker-reputation record was found.

What to Verify Next

Before any engagement, the operator's identity should be established through channels independent of the site, and sensitive use should be deferred until the external detections are cleared. The exact entity behind the service, and any claimed licence or registration, should be confirmed with the relevant registry. Anyone who received a link to this address by message, email or social media should confirm the sender's authenticity through an offline route. Official support or contact channels should be obtained from a trusted external source and not from the site. The security team should also check whether the detections are being re-evaluated or have been resolved by the hosting platform. Evidence:

  • The homepage presents no verifiable operator identity to check against a registry.
  • The subdomain-based address provides no independent brand anchor to confirm authenticity.
  • The detections come from multiple independent sources, so remediation or removal can be tracked externally.

Summary Verdict

The site carries an elevated risk posture. External threat detections are the decisive factor, and they outweigh the clean behavioural sandbox results and the valid encryption. Legitimacy cannot be inferred from the available evidence, and the operator's identity remains unestablished. The site should be treated as unsafe for any sensitive interaction.

Infrastructure Integrity

The site is delivered through Amazon Web Services edge infrastructure, with every observed address belonging to CDN edge servers. The origin server was not observable. This provides stable, well-maintained delivery and transport encryption, and it is a mitigating factor only. Edge-only visibility also prevents independent verification of where the content originates and can mask rapid content changes. Protective infrastructure is not evidence of legitimacy.

Closing Assessment

Treat the site as high-risk. Do not enter credentials, sign in, connect a wallet or make any payment or financial submission on it. Open the site only for read-only observation, and only from an isolated, non-sensitive environment. If it reached the reader through an unsolicited message, report that message and discard it.

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

What the analysis found

3 findings contributed to this verdict, raised by external reputation, hosting and network, registration and ownership.

01 External reputation

  • Several malware engines flagged this domain.External reputation rule:EXT_BLACKLIST_HIGH

02 Hosting and network

  • The domain was registered less than three months ago.Hosting and network rule:DNS_NEW_DOMAIN_90D

03 Registration and ownership

  • The public registration record for this domain is incomplete.Registration and ownership rule:KF_WHOIS_INCOMPLETE

Signals weighed against the site

  • AbuseIPDB: 2 reports on hosting IP 2a05:d014:58f:6200::259 (Amazon Data Services Ireland Ltd, Content Delivery Network), 0% confidence. The reports are attributed to shared infrastructure, not specifically to this website.

Identity verification

StatusUNKNOWN
Identity score50/100
Identity verification confidence30%
  • AI page analysis unavailable (page captured; identity not AI-verified)

Identity verification measures whether the site can be independently connected to a real-world brand or person. It is separate from the classification confidence.

What TrustSniffer observed

First-party facts recorded during the assessment of votingchoicemonitor.netlify.app.

  • The request stayed on votingchoicemonitor.netlify.app. It was not redirected to another domain. Clear
  • It is hosted on AMAZON-02, from a server in US. Noted

Domain intelligence

RegistrarNot available
HostingAMAZON-02 - Amazon.com, Inc., US
CountryUS
Server IP2a05:d014:58f:6200::259
Name serversNot available
CDN / edge networkDetected (aws)
Resolved IP addresses4
Edge IP addresses4
Likely origin IP addresses0
SSL issuerDigiCert Global G2 TLS RSA SHA256 2020 CA1
SSL expiry2027-03-19
Domain age0.11 years (continuous registration)
Domain expiryNot available
Archive first seenNot available
Archive snapshots435
ReputationVirusTotal: 2 flagged | AbuseIPDB: 0% confidence, 2 reports | Google Safe Browsing: 0 matches

About this assessment

A trust score summarises the evidence TrustSniffer could collect about votingchoicemonitor.netlify.app at assessment time. It is a starting point for your own judgement, not a guarantee: a high score means the signals were consistent with a legitimately operated site, a low or critical score means several risk patterns were present.

TrustSniffer assesses a website from the evidence it can collect at a point in time: domain registration and age, hosting and certificate, the content the site served, and third-party reputation feeds. A score is a summary of that evidence, 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 votingchoicemonitor.netlify.app

Is votingchoicemonitor.netlify.app a scam?

TrustSniffer found several risk patterns on votingchoicemonitor.netlify.app. It scored 46 out of 100 on 2026-10-22, a low-trust result. That is not proof of fraud: it means the evidence did not support treating the site as safe.

Is votingchoicemonitor.netlify.app safe to use?

Several risk patterns were present. Do not send money or personal details until you have verified this business another way.

What is the trust score of votingchoicemonitor.netlify.app?

votingchoicemonitor.netlify.app scored 46 out of 100 on 2026-10-22, which places it in the low-trust 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.
By AminRez, Founder & Lead Security Researcher, TrustSniffer
Produced by the TrustSniffer Analysis Engine · assessed 2026-10-22 · how we assess · report a mistake