Is memecoin-claiming.netlify.app a scam? 5/100

memecoin-claiming.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

memecoin-claiming.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-20, re-scored 2026-11-16 by automated analysis. Evidence confidence 75%.

What the captured page showedA Netlify-hosted 404 page reporting that the requested site or path does not exist. It contains no service offering, forms, trackers, or claims, so no fraud or deception signals are present, but no meaningful content is available to evaluate.

Evidence status and limitations

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

  • The evidence was captured on 2026-10-20 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-20.
  • 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-20; 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.

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 (75%) 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 flagged itVirusTotalClear
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
First seen1 month before captureWeb archive; a site on netlify.app has no registration of its ownRisk
Web archive398 snapshots398 snapshotsClear
CertificateEncrypted connectionIssued by DigiCert Global G2 TLS RSA SHA256 2020 CA1Noted

The page as captured

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

Key findings

  • Automated classification: Sensitive Interaction Risk, Governance Risk.
  • First seen: less than 1 year before capture (web archive; a site on netlify.app has no registration of its own).
  • VirusTotal and Google Safe Browsing had no flags for this domain; 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 address, a subdomain on Netlify's shared hosting platform whose name presents it as a place to claim memecoins, served no content of its own when it was captured. It returned the hosting platform's generic "Site not found" error page, which says the requested site or path does not exist on Netlify and points to the platform's troubleshooting guide. The page carries no product, offer, form or claim and has no visible business model. Any purpose therefore comes only from the name, which suggests a token-claiming or giveaway lure, not from anything the site said.

Scam/Impersonation Risk

A threat-intelligence feed flagged this address as a phishing site in the role of actor. The alert was last seen on 18 October 2026, and the evidence was captured two days later. This is a single alert from one source. Google Safe Browsing did not list the address, and no VirusTotal engine reported it as malicious or suspicious. The alert is therefore not treated as a confirmed listing. The score is held down by the threat-listing ceiling, so the assessment is critical risk. No conflicting legal identities and no brand impersonation were observed. The domain name does contain the platform name Netlify, but the site is only a tenant of that platform and is not Netlify. The address sits on a free platform subdomain and carries a lure-style name pairing "memecoin" with "claiming". The page captured was the platform's own not-found template, so its requests, hidden form elements, page-structure changes and missing metadata belong to that template. They are not evidence of what the operator does, and no inference about credential harvesting is drawn from them. Those measurements are nonetheless counted as scored findings, so the page's behaviour cannot be called clean.

Evidence
  • Threat-intelligence feed: the address was flagged for phishing as an actor, last seen 2026-10-18, from one source. VirusTotal reported 0 malicious and 0 suspicious engines, and Safe Browsing did not list it.
  • Homepage capture: it returned an HTTP 404 "Site not found" page with 368 characters of text, no forms analysed, and no claims or offers.
  • Registration record: the domain is a netlify.app tenant with no registration of its own. It was first seen in the web archive 45 days before capture, and 398 archive snapshots were counted, all in 2026.
  • Behavioural capture: across 3 runs, 36 requests went to other hosts, none to destinations TrustSniffer does not recognise. Hidden forms and a password field appeared in all 3 runs, and the template's page structure changed by up to 4,130 mutations after interaction.

Regulatory Verification Notes

The only page read was the homepage, which was the platform error page. On the pages read, no contact channels and no terms or privacy statement were found, and no operator, company name, licence or registration claim was found. No regulator or licensing claim was made, so none can be checked. The identity of whoever controls this subdomain is unverified. The site makes no claims about itself, and no third-party broker or reputational record matched it. Without a domain registration of its own, the address offers nothing that independently ties it to a real-world person or business. The certificate belongs to the hosting platform, not to the operator. It shows that the platform's transport encryption was working, not who runs the site.

Evidence
  • Homepage: on the page read, no contact channels, no terms or privacy statement, and no company or licence references appeared.
  • Hosting infrastructure: the address was served from AS16509 (AMAZON-02 - Amazon.com, Inc., US).
  • Transport encryption: an OV certificate issued by DigiCert Global G2 TLS RSA SHA256 2020 CA1 to Netlify, Inc was seen at capture and was valid until 2027-03-19.
  • Third-party broker data: no match was found, so no reputational context is available from that source.

What to Verify Next

The practical question is where the address came from. Any message, post or advertisement that sent traffic here should be traced to its source. Any memecoin or token-claim programme it claims to represent should be confirmed through the project's official channels, located independently and not through links on this address or in the message that promoted it. Because the site published no operator identity and no contact route on the pages read, there is nothing on the site itself to cross-check. Any later content at this address should be treated as unvetted and assessed again from scratch. If the sender of the link cannot be authenticated through a separate route, the link should not be followed.

Evidence
  • Homepage: it offered no outbound links, social profiles or contact routes to verify, so any verification must start outside the site.
  • Threat-intelligence feed: the phishing alert dated 2026-10-18 concerns this exact address.
  • Registration record: the address is a platform tenant, and its operator cannot be established from registration data.

Summary Verdict

The address is assessed at critical risk. It shows no operator identity and no content of its own, and it is attached to a phishing alert. The score is held down by the threat-listing ceiling. The reassuring technical signals that were present do not offset these facts.

Infrastructure Integrity

Four addresses were observed, all edge addresses on Amazon's network, and no origin address was seen, so the hosting arrangement cannot be traced beyond that edge. The CDN presence is treated as neutral. Abuse reports exist against one of the shared Amazon provider addresses, and they attach to that shared infrastructure, not specifically to this site.

Closing Assessment

This address should be treated as critical risk. It should not be used for any claim, sign-in or transaction. Any request that arrived through it should be verified through the genuine project's own channels.

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

What the analysis found

13 findings contributed to this verdict, raised by governance, behaviour in a sandbox, hosting and network, page content, 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
  • 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 replaced a large part of its own content during the sandbox session.Behaviour in a sandbox rule:BEHAV_DOM_CHANGE_HIGH
  • 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
  • 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 Hosting and network

  • The domain was registered, or a site on a hosting platform was first seen, less than three months before capture.Hosting and network rule:DNS_NEW_DOMAIN_90D

04 Page content

  • The page runs on a free hosting-platform address instead of a domain of its own, a setup common to short-lived phishing and claim pages.Page content rule:PAGE_FREE_PLATFORM_ADDRESS
  • The page has no description for search engines, which established sites usually provide.Page content rule:PAGE_SEO_MISSING_META

05 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.

  • 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: 2 findings share one limit, because they all measure one fact: the page loads files from other hosts. Together they stayed under the limit.

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 memecoin-claiming.netlify.app.

  • The request stayed on memecoin-claiming.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)44 days before capture; a site on netlify.app has no registration of its own
Domain expiryNot available
Archive first seenNot available
Archive snapshots398
ReputationVirusTotal: 0 malicious | 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 memecoin-claiming.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 memecoin-claiming.netlify.app

Is memecoin-claiming.netlify.app a scam?

TrustSniffer's assessment of memecoin-claiming.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 memecoin-claiming.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 memecoin-claiming.netlify.app?

memecoin-claiming.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