Is hylrukrxwfwbooknmtyx.supabase.co a scam? 0/100

hylrukrxwfwbooknmtyx.supabase.co
Download PDF Check another site How we score

Verdict

This assessment found strong scam indicators. Do not pay, sign in, or share personal details with this site.

0 OUT OF 100
Critical Risk

hylrukrxwfwbooknmtyx.supabase.co shows high-risk / scam indicators.

Sensitive Interaction Risk

Assessed 2026-10-19 by automated analysis. Classification confidence 45%.

What this site appears to beThis page contains only a short JSON-style error message indicating an invalid requested path. No actionable content, forms, links, or business information are present.

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, 14 reports; shared hosting inflates reportsClear
Domain ageNot availableNo registration record was returnedNoted

The page as captured

https://hylrukrxwfwbooknmtyx.supabase.co/
Screenshot of the hylrukrxwfwbooknmtyx.supabase.co homepage captured during the TrustSniffer assessment
What hylrukrxwfwbooknmtyx.supabase.co served when TrustSniffer captured it on 2026-10-19. The page may look different now.

Key findings

  • Automated classification: Sensitive Interaction Risk.
  • At least one reputation service TrustSniffer consulted had flagged this domain at assessment time.
  • The operator behind the site could not be independently connected to a real-world brand or person.

Full analysis

Security Alert

Sophos flagged this site in external intelligence checks, indicating elevated compromise/scam exposure that requires immediate caution.

This website is an unbranded service endpoint hosted on a subdomain of a shared backend-platform domain. Its homepage returns only a short machine-style error message stating that the requested path is invalid. It presents no visible products, navigation, forms, company description or contact details. Its apparent role is a back-end resource rather than a customer-facing business, and no business model can be discerned from what it serves.

Scam/Impersonation Risk

Contradictory signals are present, and they are what drive the cautionary posture of this assessment. Independent threat-intelligence engines flag the host: two classify it as malicious and one as suspicious, including a major security vendor, and the host is listed as blacklisted by external sources. The detections do not specify the nature of the threat, so no particular attack type, such as phishing or malware delivery, can be attributed to the site. No brand impersonation and no conflicting legal identities were observed. The page contains no login form, no hidden form, no wallet-connection logic and no external data submission, and the behavioural runs showed no outbound network activity. These benign behaviours do not offset the external detections. Abuse reports exist against the shared edge address the site resolves to. They are attributed to that address's role as shared content-delivery infrastructure and are therefore discounted. They are not evidence about this site's operator. Because the page is blank, the detections cannot be tied to any visible content, so the threat listing is the decisive negative. Evidence:

  • Homepage: returns only a short JSON-style error stating the requested path is invalid, served with a "not found" status. It has no title, no meta description, no links and no forms.
  • External reputation: two engines rate the host malicious and one suspicious, while a larger group rates it harmless or undetected. A major security vendor is among the flagging engines.
  • Network behaviour: three sandbox runs completed, with zero external requests, zero external form posts and zero wallet or clipboard activity. Three browser console errors were recorded.
  • Shared address: 14 abuse reports against the edge address are classed as shared-infrastructure noise and discounted.

Regulatory Verification Notes

The site exposes no legal, identity, terms, privacy or about pages, so there is no corporate name, licence reference or registration number to assess. Because nothing is published, the real-world operator cannot be independently connected to any business or person. Any claim of legitimacy would therefore be unsupported. No financial, investment or regulated-service activity is advertised, so the absence of licensing disclosure is a verification matter and not a finding against the site. Third-party broker-reputation data returned no match for this host. Evidence:

  • Homepage: contains no company name, licence number, registration detail or jurisdiction.
  • Hosting: served via AS13335 (Cloudflare, Inc., US).
  • Transport encryption: the TLS certificate is issued by WE1 at domain-validated (DV) level and is valid to 2026-11-24. DV confirms only control of the domain name, not the identity of the operator.
  • Broker reputation: no matching record in the third-party broker dataset, which is context only and not a regulatory verdict.

What to Verify Next

Anyone who was directed to this address should first establish who sent the link and why. The sender should be asked, through an independent channel such as a known phone number or an in-person contact, to confirm that the endpoint is intentional and to supply the organisation's official website address. A prospective user should not rely on this address to identify a counterparty. The official channels of the claimed organisation should be reached through routes found independently, not through anything reached from here. If the address belongs to an application the user operates or integrates with, the owner or administrator should review the project's configuration and exposure. They should also confirm whether the external detections stem from content that was served from this host in the past. Evidence:

  • Homepage: shows no identifying content, so the claimed organisation cannot be established from the site itself.
  • Page status: the not-found response suggests the root path is not an intended public entry point.
  • External reputation: current detections by multiple engines mean the host's status should be re-checked after any remediation.

Summary Verdict

The site carries an elevated risk assessment and is not suitable for sensitive interaction. External threat-intelligence detections are decisive, and the site's own content provides neither identity nor purpose that could offset them. The behavioural runs were clean, but that is not enough to support trust, and the operator remains unidentified.

Infrastructure Integrity

The site is delivered through Cloudflare's CDN and WAF, and the observed addresses are edge servers; the origin server was not observed. This is a mitigating factor only. A valid certificate and mainstream edge protection show competent hosting. They do not establish legitimacy and cannot offset the reputational risk from the external detections.

Closing Assessment

At most, the address should be treated as read-only. Account login, credential entry and any financial or payment interaction should be avoided, and nothing should be downloaded from it, until the owner has been independently identified and the external detections are resolved.

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

What the analysis found

2 findings contributed to this verdict, raised by external reputation, page content.

01 External reputation

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

02 Page content

  • The page loaded on its own domain but had no readable content.Page content rule:PAGE_CONTENT_EMPTY
  • The page shows few of the signs expected from a trustworthy operator.Page content rule:PAGE_TRUST_QUALITY_LOW
  • The page has no title, which almost every website sets.Page content rule:PAGE_TITLE_MISSING
  • The browser raised a warning while loading the page.Page content rule:PAGE_BROWSER_FLAGS_SUSPICIOUS

Signals weighed against the site

  • AbuseIPDB: 14 reports on hosting IP 172.64.149.246 (Cloudflare, Inc., Content Delivery Network), 0% confidence. The reports are attributed to shared infrastructure, not specifically to this website.

Identity verification

StatusUNVERIFIED
Identity score30/100
Identity verification confidence50%
  • No on-site identity signals detected

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 hylrukrxwfwbooknmtyx.supabase.co.

  • The request stayed on hylrukrxwfwbooknmtyx.supabase.co. It was not redirected to another domain. Clear

Domain intelligence

RegistrarNot available
HostingNot available
CountryNot available
Server IP172.64.149.246
Name serversNot available
CDN / edge networkLookup incomplete
SSL issuerWE1
SSL expiry2026-11-24
Domain ageNot available (no registration date was returned)
Domain expiryNot available
Archive first seenNot available
Archive snapshotsNot available
ReputationVirusTotal: 2 flagged | AbuseIPDB: 0% confidence, 14 reports | Google Safe Browsing: 0 matches

About this assessment

A trust score summarises the evidence TrustSniffer could collect about hylrukrxwfwbooknmtyx.supabase.co 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 hylrukrxwfwbooknmtyx.supabase.co

Is hylrukrxwfwbooknmtyx.supabase.co a scam?

TrustSniffer's assessment of hylrukrxwfwbooknmtyx.supabase.co found strong scam indicators. It scored 0 out of 100 on 2026-10-19, which is the critical-risk band. The specific signals are listed in the evidence above.

Is hylrukrxwfwbooknmtyx.supabase.co safe to use?

This assessment found strong scam indicators. Do not pay, sign in, or share personal details with this site.

What is the trust score of hylrukrxwfwbooknmtyx.supabase.co?

hylrukrxwfwbooknmtyx.supabase.co scored 0 out of 100 on 2026-10-19, 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.
By AminRez, Founder & Lead Security Researcher, TrustSniffer
Produced by the TrustSniffer Analysis Engine · assessed 2026-10-19 · how we assess · report a mistake