Is golden-salmiakki-37d2cb.netlify.app a scam? 5/100

golden-salmiakki-37d2cb.netlify.app

Is it safe to use? An external threat listing named this site as malicious when the evidence was captured. Do not pay, sign in, 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, sign in, or share personal details with this site.

5 OUT OF 100
Critical Risk

golden-salmiakki-37d2cb.netlify.app shows critical-risk indicators.

Sensitive Interaction Risk Governance Risk
  • Sensitive Interaction Risk: The overall risk is high enough that entering private details here (a password, card number or wallet recovery phrase) could be unsafe.
  • Governance Risk: The governance checks raised a concern: a threat-intelligence listing limits the score; as a site on netlify.app, this address has no registration record of its own (the platform's domain is registered, not the site). The findings below give the detail.

Evidence captured 2026-10-18, re-scored 2026-11-16 by automated analysis. Evidence confidence 55%.

What the captured page showedNetlify default 'Site not found' 404 page. No forms, no payment or credential requests, minimal content advising the site owner to check Netlify support docs.

Evidence status and limitations

Evidence completeness: PartialThis says whether every check on the site was recorded as finished. At least one check failed or returned no result.

  • The evidence was captured on 2026-10-18 and re-scored on 2026-11-16. The certificate, the registration age and the page content describe the site as it was on 2026-10-18.
  • 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-18)). No second source confirms it. The alert is from the evidence captured on 2026-10-18; it was not re-queried for this version 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.
  • When captured, this address served the hosting platform's own 'site not found' page; the page and sandbox findings below were measured on that page.
  • The real-world operator identity was not independently verified.
  • These checks returned no result: web archive lookup.

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 (55%) 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-18), and that listing caps the score. The unconfirmed alert ceiling (at most 49) also applies, but the score is below it.Risk
Malware enginesNone malicious; 1 marked it suspiciousVirusTotalWatch
Google Safe BrowsingNot listedGoogleClear
Abuse reports on the CDN edge address1% confidenceAbuseIPDB, 4 reports; shared hosting inflates reports; this is the record of the CDN edge address, not of the server behind it, which was not observedNoted
Domain ageNot availableNo registration record was returnedNoted
CertificateEncrypted connectionIssued by DigiCert Global G2 TLS RSA SHA256 2020 CA1Noted
Hosted byAMAZON-02Network registered in USNoted

The page as captured

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

Key findings

  • Automated classification: Sensitive Interaction Risk, Governance Risk.
  • No security engine marked this domain as malicious and Google Safe Browsing does not list it; some engines marked it suspicious, which TrustSniffer does not count as a listing. Its hosting IP carries AbuseIPDB reports below the confidence level TrustSniffer treats as a flag.
  • The operator behind the site could not be independently connected to a real-world brand or person.

Full analysis

Overview

This web address is a subdomain on Netlify's public hosting service. When it was captured on 18 October 2026, it served Netlify's own "Site not found" page (translated as a 404 notice about a broken link or non-existent address) rather than any content of its own. The page showed no products, services, company description or business model. It only pointed the visitor to Netlify's troubleshooting guide and invited them to start building their own site. Its apparent purpose could not be determined from what the address served.

Scam/Impersonation Risk

The principal finding is that a threat-intelligence feed listed this address as the actor in a phishing case, last seen on 18 October 2026, the same day as the capture. This is the one contradictory signal present. It rests on a single listing source. One VirusTotal engine rated the address suspicious and none rated it malicious. Google Safe Browsing did not list it. The address itself has no identifiable brand or operator; it is a tenant name on a shared hosting platform, and the Netlify name in the address does not mean the site is Netlify. The page captured on that date was the platform's own not-found template, so its structure and behaviour belong to that template. The measurements taken from it say nothing about what the tenant's content did. Nothing observed on the page itself shows credential harvesting or brand impersonation. The score is held down by the threat-listing ceiling, and the analysis treats the site as a critical risk because of that listing. Because the address served no content of its own, the listing is the only evidence about the tenant's intent. No conflicting legal identities appeared, because no identity content was served.

Evidence
  • Threat-intelligence listing: the address was recorded as a phishing actor, last seen 18 October 2026.
  • VirusTotal: 0 engines malicious and 1 suspicious; Google Safe Browsing did not list the address.
  • Homepage capture: the Netlify "Site not found" template was served (HTTP 404), with no forms collecting data and no brand claims.
  • Hosting address record: 4 abuse reports were logged against a shared provider address used by the CDN. These relate to shared infrastructure and are not attributed to this site specifically.

Regulatory Verification Notes

The only page read was the homepage, and it was the platform's placeholder. On the pages read, no contact channels and no terms or privacy statement were found. The address makes no licensing, registration or regulatory claims, so there is nothing to test against any registry. The real-world operator is unverified. The TLS certificate seen at capture was an organisation-validated certificate issued to Netlify, Inc., valid until 19 March 2027. It identifies the hosting platform, not the tenant behind this address. This address was first seen on a shared platform domain and has no registration of its own. The behavioural measurements are scored findings. The page loaded 99.6% of its files from other domains. It made 36 requests sending data to other hosts, none to destinations TrustSniffer does not recognise. These measurements belong to the platform template, so they are not evidence of tenant behaviour. No third-party broker or regulator record matched this address.

Evidence
  • Homepage: the pages read showed no contact channels and no terms or privacy statement.
  • TLS: certificate issued by DigiCert Global G2 TLS RSA SHA256 2020 CA1 (OV), subject Netlify, Inc., valid to 2027-03-19.
  • Hosting: served from AS16509 (AMAZON-02, Amazon.com, Inc., US).
  • Page behaviour: 99.6% of files loaded from other domains, and 36 requests sent data to other hosts, all to recognised services.

What to Verify Next

The first step is to establish who published or shared this link, using a channel that does not depend on the address itself, and why it was sent. If the link arrived in a message, email or advertisement claiming to represent a company, that company's own published channels should be used to confirm whether it operates this address. Whether the address now serves any content should be rechecked before any engagement, since the capture reflects only 18 October 2026. If the tenant presents itself as a business, it should provide a verifiable company name and, where relevant, a licence reference that can be checked with the competent registry.

Evidence
  • Homepage capture: no operator or company identity was presented.
  • Homepage capture: the page served only the platform's troubleshooting prompt.
  • Threat-intelligence listing: it was last seen on 18 October 2026, so the address's current content is unknown.

Summary Verdict

The address carries critical risk. It is anonymous, unidentified and tied to a phishing listing, and it offers no legitimate content or identity that would counterbalance that. The valid platform certificate and the absence of malicious content on the placeholder page are not sufficient to offset the listing.

Infrastructure Integrity

The address resolved to four edge IPs on Amazon Web Services infrastructure, with a CDN detected and no origin server observable. This is a neutral technical condition. It neither supports legitimacy nor adds exposure, and it does not offset the threat listing.

Closing Assessment

The address should be treated as unsafe for any login, credential entry or financial interaction. Links to it should not be followed or relied on, and at most it should be viewed passively. If it was received through an unsolicited message, that message should be treated as a possible phishing attempt and reported.

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

What the analysis found

12 findings contributed to this verdict, raised by governance, behaviour in a sandbox, and registration and ownership.

When captured, this address served the hosting platform's own 'site not found' page; the page and sandbox findings below were measured on that page.

01 Governance

  • 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-18), and that listing caps the score.Governance rule:gov_active_threat_listing

02 Behaviour in a sandbox

  • The page contained a form a visitor cannot see.Behaviour in a sandbox rule:BEHAV_HIDDEN_FORMS
  • Most of the files the page loaded (scripts, images, fonts) came from other domains. This is about where its content is hosted, not about data being sent elsewhere.Behaviour in a sandbox rule:BEHAV_EXTERNAL_RATIO_HIGH
  • The page replaced a large part of its own content during the sandbox session.Behaviour in a sandbox rule:BEHAV_DOM_CHANGE_HIGH
  • The page contained a form a visitor cannot see in more than one sandbox session.Behaviour in a sandbox rule:BEHAV_HIDDEN_FORMS_REPEAT
  • The page rewrote itself after it was interacted with, so what a visitor first sees is not what they end up on.Behaviour in a sandbox rule:BEHAV_DOM_DIFF_AFTER_INTERACTION
  • The structure of the page changed sharply during the sandbox session.Behaviour in a sandbox rule:BEHAV_DOM_DENSITY_SPIKE
  • The page showed a password field during the sandbox session, and it could not be matched to a recognised brand's sign-in page.Behaviour in a sandbox rule:BEHAV_PASSWORD_FORM_PRESENT
  • An automated reading of the page's network activity judged some requests unusual for this kind of page, although every destination was a service TrustSniffer recognises.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

03 Registration and ownership

  • As a site on netlify.app, this address has no registration record of its own (the platform's domain is registered, not the site).Registration and ownership rule:KF_WHOIS_INCOMPLETE

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.

  • Browser sandbox heuristics: 2 findings share one limit, because no other evidence confirms them. The limit applied, so together they counted for less than their sum.
  • Page structure: 3 findings share one limit, because they describe one page structure. The limit applied, so together they counted for less than their sum.
  • Third-party connections: 3 findings share one limit, because they all measure one fact: the page loads files from other hosts. The limit applied, so together they counted for less than their sum.

Noted, not counted

Recorded during the assessment, but not counted against the site.

  • AbuseIPDB: 4 reports on hosting IP 2a05:d014:58f:6200::258 (AMAZON-02), 1% confidence. The reports are attributed to shared infrastructure, not specifically to this website.

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.

  • No contact detail, company registration number or linked social profile was extracted from the page for checking.

What TrustSniffer observed

First-party facts recorded during the assessment of golden-salmiakki-37d2cb.netlify.app.

  • The request stayed on golden-salmiakki-37d2cb.netlify.app. It was not redirected to another domain. Clear
  • It is hosted on AMAZON-02, a network registered in US. Noted

Domain intelligence

RegistrarNot available
HostingAMAZON-02 - Amazon.com, Inc.
Network registered inUS
Server IP2a05:d014:58f:6200::258 (a CDN edge address; the server behind it was not observed)
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
First seen (web archive)Not available (the web archive has no record of this address; a site on netlify.app has no registration of its own)
Domain expiryNot available
Archive first seenNot available
Archive snapshotsNot counted (archive lookup incomplete)
ReputationVirusTotal: 0 malicious, 1 suspicious | AbuseIPDB (CDN edge address, not the host): 1% confidence, 4 reports | Google Safe Browsing: 0 matches

About this assessment

A trust score summarises the evidence TrustSniffer could collect about golden-salmiakki-37d2cb.netlify.app 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 golden-salmiakki-37d2cb.netlify.app

Is golden-salmiakki-37d2cb.netlify.app a scam?

TrustSniffer's assessment of golden-salmiakki-37d2cb.netlify.app found strong scam indicators. It scored 5 out of 100 on 2026-11-16, which is the critical-risk band. The specific signals are listed in the evidence above.

Is golden-salmiakki-37d2cb.netlify.app safe to use?

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

What is the trust score of golden-salmiakki-37d2cb.netlify.app?

golden-salmiakki-37d2cb.netlify.app scored 5 out of 100 on 2026-11-16, 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-16 · how we assess · report a mistake