Is merkl-allocation.xyz a scam? TrustSniffer's critical-risk assessment: 5/100

merkl-allocation.xyz

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

merkl-allocation.xyz 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.

Evidence captured 2026-11-13, re-scored 2026-11-15 by automated analysis. Evidence confidence 47%.

How the site describes itselfCloudflare bot-verification interstitial for merkl-allocation.xyz. No site content is visible, so the service 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.

  • The evidence was captured on 2026-11-13 and re-scored on 2026-11-15. The certificate, the registration age and the page content describe the site as it was on 2026-11-13.
  • Two sources reported 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-24), and 1 VirusTotal engine that marked it as malicious. A single VirusTotal engine is below TrustSniffer's bar for a confirming source, so no second source confirms the listing. The alert is from the evidence captured on 2026-11-13; 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.
  • 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 (47%) 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-24), and that listing caps the score. The business-model ceiling (at most 50) and the unconfirmed alert ceiling (at most 49) also apply, but the score is below them.Risk
Malware engines1 marked it malicious, 2 suspiciousVirusTotal; a single engine, not a confirmed listingWatch
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 age6 months oldRegistered 2026-05-11Watch
Web archiveNever archivedNo public history of this siteWatch
CertificateEncrypted connectionIssued by YE2Noted

The page as captured

https://merkl-allocation.xyz/
Screenshot of the merkl-allocation.xyz homepage captured during the TrustSniffer assessment
What merkl-allocation.xyz served when TrustSniffer captured it on 2026-11-13. The page may look different now.

Key findings

  • Automated classification: Sensitive Interaction Risk.
  • Domain age: less than 1 year at capture (registered 2026-05-11).
  • At least one reputation service TrustSniffer consulted had flagged this domain when the evidence was captured.
  • The operator behind the site could not be independently connected to a real-world brand or person.

Full analysis

Overview

This website at merkl-allocation.xyz presented a Cloudflare bot-verification screen when it was analysed, so no products, offers or services were visible. The domain name suggests a token-rewards allocation service, but that is unconfirmed. The captured page carried no service description, and the site's purpose and business model could not be determined from it.

Scam/Impersonation Risk

This site carries critical risk. A threat-intelligence feed lists it as the actor in a phishing activity, which is the most serious finding in this assessment. The feed last saw the listing on 24 October 2026, three weeks before the page was captured on 13 November 2026. It is a single-source listing, and the score is held down by the threat-listing ceiling. Separate reputation checks agree in part: one scanning engine rated the domain malicious and two rated it suspicious, though no leading vendor was among them. Google Safe Browsing did not list it. These engine ratings are soft reputational signals and not a confirmed listing. The page's behaviour in the sandbox adds to the concern. Almost all files loaded came from other domains, and the page made a large number of outbound requests, a small share of them to destinations TrustSniffer does not recognise. These behaviours are scored findings, so the page cannot be described as behaving ordinarily. The page reads "Verification successful" while still showing "Waiting for merkl-allocation.xyz to respond", and it asks the visitor to enable JavaScript and cookies. Those two statements can both be true, so this is an observation and not a contradiction. No forms or sign-in fields were present on the captured page. Image-based or content-based impersonation could not be assessed because no site content was visible.

Evidence
  • Threat-intelligence feed: a single source names the site as the actor in phishing activity, last seen 2026-10-24.
  • VirusTotal: 1 engine malicious and 2 suspicious, with no top-tier vendor among them; Google Safe Browsing did not list the site.
  • Sandbox behaviour: 96.9% of files came from other domains, 36 requests sent data to other hosts, and 3 of these went to destinations TrustSniffer does not recognise.
  • Homepage: the captured text consists only of the challenge wording, including "Performing security verification" and "Enable JavaScript and cookies to continue".

Regulatory Verification Notes

On the only page read, the homepage, no contact channels and no terms or privacy information appeared. That page was a bot-challenge screen, so these are gaps on the pages we read and not a conclusion about the whole site. No licence or regulatory status was claimed or found, and no independent source connects the domain to a real-world operator. The only name-like text on the page, "Just a moment", is the challenge screen's title and not an organisation. Operator identity therefore remains unverified. The domain was recently registered, and its registration record is complete.

Evidence
  • Registration record: domain registered 2026-05-11 (186 days at capture) through PDR Ltd. d/b/a PublicDomainRegistry.com, expiring 2027-05-11.
  • Hosting network: served from AS13335 (Cloudflare, Inc., US).
  • Homepage: no contact details and no terms or privacy statement on the page read.
  • Homepage: no licence or registration claim was made.

What to Verify Next

Any approach to this site should be treated as unconfirmed until an independent route establishes who operates it. If the domain reached a reader through a message, advertisement or social post, the sender's claims should be checked through the official channels of the organisation said to be behind it, using an offline or separately sourced route. Official support and contact channels should be confirmed the same way. Nothing on the site itself should be used to vouch for the site.

Evidence
  • Homepage: the capture returned a bot challenge (HTTP 403), so no service content could be assessed.
  • Domain name: it pairs the word "merkl" with "allocation". The page does not identify itself as any brand, and nothing captured connects the site to a brand of that name.
  • Page analysis: no brand impersonation was detected on the captured screen, but the screen contained no content to compare.

Summary Verdict

The overall posture is critical risk. The score is held down by the threat-listing ceiling, and the thin, unassessable page and the unverified operator identity give nothing to offset it. At capture on 13 November 2026, the page showed no forms or sign-in fields and its certificate was valid until 3 February 2027, but these observations do not change the critical risk.

Infrastructure Integrity

All four observed addresses belong to Cloudflare edge servers, and no origin address was observed. This is neutral and says nothing in the site's favour or against it. The site presented a valid DV TLS certificate from issuer YE2, valid until 2027-02-03. A valid certificate and a recognised network show only that the connection is encrypted and routed through a known provider. They say nothing about the intentions of the operator.

Closing Assessment

Prospective users should not engage with this domain and should not follow links or instructions that point to it. Anyone who has already visited should treat that visit as an unverified contact and rely only on independently sourced official channels for any related request.

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

What the analysis found

9 findings contributed to this verdict, raised by governance, 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 50, 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-24), and that listing caps the score.Governance rule:gov_active_threat_listing

02 Page content

  • The page content shows at least one warning sign that deceptive sites commonly use.Page content rule:PAGE_RED_FLAGS_SOME
  • 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

03 Behaviour in a sandbox

  • 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
  • Many of the responses the page received looked generated rather than served normally.Behaviour in a sandbox rule:BEHAV_SYNTHETIC_RESPONSES_HIGH
  • An automated reading of the page's network activity judged some requests unusual for this kind of page.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

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

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 merkl-allocation.xyz.

  • The request stayed on merkl-allocation.xyz. 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-05-11. Noted
  • 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:3035::6815:4b94 (a CDN edge address; the server behind it was not observed)
Name serverssid.ns.cloudflare.com, elma.ns.cloudflare.com
CDN / edge networkDetected (cloudflare)
Resolved IP addresses4
Edge IP addresses4
Likely origin IP addresses0
SSL issuerYE2
SSL expiry2027-02-03
Domain age186 days (registered 2026-05-11)
Domain expiry2027-05-11
Archive first seenNot available
Archive snapshots0
ReputationVirusTotal: 1 malicious, 2 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 merkl-allocation.xyz 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 merkl-allocation.xyz

Is merkl-allocation.xyz a scam?

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

Is merkl-allocation.xyz 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 merkl-allocation.xyz?

merkl-allocation.xyz scored 5 out of 100 on 2026-11-15, 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-15 · how we assess · report a mistake