Is 7423.sbs a scam? 0/100

7423.sbs

Is it safe to use? External threat listings 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

External threat listings named this site as malicious when the evidence was captured. Do not pay or share personal details with this site.

0 OUT OF 100
Critical Risk

7423.sbs shows critical-risk indicators.

Sensitive Interaction Risk Governance 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.
  • Governance Risk: An ownership check raised a concern: the domain's registration record withholds the owner's details. On its own this does not say who runs the site or that anything is wrong with it.

Evidence captured 2026-11-12, re-scored 2026-11-15 by automated analysis. Evidence confidence 55%.

What the captured page showedCloudflare error page (HTTP 522, connection timed out between Cloudflare and the origin server) for 7423.sbs. No site content, services, contact details, or policies were available to analyse.

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-11-12 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-12.
  • External threat sources confirmed a listing for this site when the evidence was captured (VirusTotal, a threat-intelligence listing from a feed TrustSniffer monitors (phishing, the site itself as the source, last seen 2026-10-25)). It was not re-queried for this version. On its own it would limit the score to at most 24; the score is lower because of the other findings below.
  • When captured, this address served a placeholder (a suspension notice, a server's default page or a coming-soon page) instead of the site; the page and sandbox findings below were measured on that placeholder.
  • The real-world operator identity was not independently verified.
  • These checks returned no result: web archive lookup.

How to read these numbers

A trust score of 0 means the risk evidence outweighed every trust signal by more than the 0 to 100 scale can show. It 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 scoreThe findings belowThe independent sources ceiling (at most 24) and the threat-listing ceiling (at most 5) also apply, but the findings brought the score lower.Watch
Malware engines4 marked it malicious, 1 suspiciousVirusTotalRisk
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 age7 months oldRegistered 2026-04-15Watch
CertificateEncrypted connectionIssued by YE1Noted
Hosted byCLOUDFLARENETNetwork registered in USNoted

The page as captured

https://7423.sbs/
Screenshot of the 7423.sbs homepage captured during the TrustSniffer assessment
What 7423.sbs served when TrustSniffer captured it on 2026-11-12. The page may look different now.

Key findings

  • Automated classification: Sensitive Interaction Risk, Governance Risk.
  • Domain age: less than 1 year at capture (registered 2026-04-15).
  • 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

The address 7423.sbs, when captured on 12 November 2026, served only a Cloudflare "522: Connection timed out" error page. That page is a placeholder, not a working website, and it carried no products, pricing, payment flow, company description or contact details. The site's apparent purpose therefore cannot be established from its own content. Its recorded history is a threat-intelligence listing that names it as a distributor of phishing content.

Scam/Impersonation Risk

This is a critical-risk site, and the risk comes from outside reputation, not from anything the page says. A threat-intelligence listing names the address as an actor distributing phishing content, last seen on 25 October 2026. Separately, the VirusTotal reputation service reported four engines as malicious and one as suspicious. Because these two sources align, the findings meet the bar for a confirmed listing, and the address is treated as blacklisted. Google Safe Browsing did not list it, and none of the malicious engines belongs to the leading-vendor group. No brand impersonation and no conflicting legal identities were observed. The listing is the only contradiction, and it is a serious one. The captured page offered no login or data-entry form, so the phishing activity was not visible on the page itself. It rests on the listing. The address presents itself under the label "7423 Sbs", which is taken from the page title, and that label does not link it to any real-world organisation or person. The placeholder also made 113 requests to other hosts, all to destinations TrustSniffer recognises, and about 95% of the files it loaded came from other domains. These are scored findings that count against the site, though they describe the placeholder's behaviour and not a working site.

Evidence
  • VirusTotal: four engines rated the address malicious and one suspicious on the capture date, and a separate threat-intelligence listing classes it as phishing (role: actor, last seen 25 October 2026).
  • Registration record: the domain was registered on 2026-04-15, about 211 days (0.6 years) before capture.
  • Homepage capture: the Cloudflare timeout placeholder showed no forms and no brand material, so no impersonation of a named brand was seen.
  • Homepage capture: 113 outbound requests were made, none to unrecognised destinations.

Regulatory Verification Notes

The only page read was the homepage, and it was a placeholder. On that page, no contact channels, no terms or privacy policy, no company name, no licence claim and no registration number were present. For the same reason, no business type or regulated activity could be assessed. These are gaps on the pages read, not findings of wrongdoing. The registration record uses privacy protection, which counts as a scored finding. The registrar is NameSilo, LLC. The site's operator identity is unverified, and no third-party regulatory or broker-reputation record was found for the site.

Evidence
  • Homepage capture: no contact, terms or privacy content on the single page read.
  • Registration record: registrar NameSilo, LLC; registration expires 2027-04-15; owner details privacy-protected.
  • Site hosting: served from AS13335 (CLOUDFLARENET, Cloudflare, Inc., US).
  • Transport encryption: TLS certificate issued by YE1 (domain-validated), and the certificate seen at capture was valid until 2027-01-07.

What to Verify Next

Any message, advertisement or payment request that points to this address should be treated as suspected phishing and reported to the party that supplied it. Because the address showed no working site and no operator details, the only reliable route to any business that claims to use it is a channel the recipient already trusts, such as a known official website or a registered company record found independently. The listing was last seen on 25 October 2026, so any later change in the address's reputation should be checked against fresh reputation sources before it is relied on. Official support or contact channels should be confirmed by an independent, offline route.

Evidence
  • Threat-intelligence listing: phishing classification, last seen 25 October 2026.
  • Homepage capture: no organisation, contact or policy information to check against.
  • VirusTotal: reputation results reflect the capture date of 12 November 2026.

Summary Verdict

The overall posture is critical risk. Independent, aligned reputation sources classify the address as a phishing distributor, and the page offers nothing that identifies or vouches for an operator. The site's identity is unverified, and the technical hygiene around it does not alter that conclusion.

Infrastructure Integrity

The address resolves to four Cloudflare edge addresses, and no origin server was observable. A CDN is neutral for this assessment. It neither raises nor lowers the risk, and it does not show who operates the site. The host's address was checked for abuse and had no reports. The 522 error means Cloudflare could not complete a connection to the origin server, so no site content was served at capture.

Closing Assessment

The address should not be visited, linked to, or engaged with for any purpose. It should be blocked on organisational networks and excluded from any business or payment relationship. Any message that directs people to it should be reported and not acted on.

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

What the analysis found

8 findings contributed to this verdict, raised by external reputation, page content, registration and ownership and behaviour in a sandbox.

When captured, this address served a placeholder (a suspension notice, a server's default page or a coming-soon page) instead of the site; the page and sandbox findings below were measured on that placeholder.

01 External reputation

  • 4 VirusTotal engines marked this domain as malicious when the evidence was captured.External reputation rule:EXT_BLACKLIST_HIGH

02 Page content

  • The site served a placeholder or error page instead of its content.Page content rule:PAGE_UNREACHABLE_PLACEHOLDER
  • The page could not be read normally when it was captured.Page content rule:PAGE_UNREACHABLE_REASON
  • The page has no description for search engines, which established sites usually provide.Page content rule:PAGE_SEO_MISSING_META
  • The page carries none of the structured previews for search and social sharing that established sites usually provide.Page content rule:PAGE_SEO_NO_STRUCTURED

03 Registration and ownership

  • The registration record withholds contact details for the operator.Registration and ownership rule:KF_WHOIS_HIDDEN

04 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
  • Many of the responses the page received looked generated rather than served normally.Behaviour in a sandbox rule:BEHAV_SYNTHETIC_RESPONSES_HIGH

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.

  • Certificate and search-engine setup: 2 findings share one limit, because none of them is a sign of fraud on its own. Together they stayed under the limit.

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:7423 Sbs
  • on_site_identity

What TrustSniffer observed

First-party facts recorded during the assessment of 7423.sbs.

  • The request stayed on 7423.sbs. It was not redirected to another domain. Clear
  • Registered through NameSilo, LLC. Noted
  • DNS for this domain is served by cloudflare.com, across 2 name servers. Noted
  • The domain is registered until 2027-04-15. Noted
  • It is hosted on CLOUDFLARENET, a network registered in US. Noted

Domain intelligence

RegistrarNameSilo, LLC
HostingCLOUDFLARENET - Cloudflare, Inc.
Network registered inUS
Server IP2606:4700:3035::6815:3ba (a CDN edge address; the server behind it was not observed)
Name serversrazvan.ns.cloudflare.com, isla.ns.cloudflare.com
CDN / edge networkDetected (cloudflare)
Resolved IP addresses4
Edge IP addresses4
Likely origin IP addresses0
SSL issuerYE1
SSL expiry2027-01-07
Domain age211 days (registered 2026-04-15)
Domain expiry2027-04-15
Archive first seenNot available
Archive snapshotsNot counted (archive lookup incomplete)
ReputationVirusTotal: 4 malicious, 1 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 7423.sbs 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 7423.sbs

Is 7423.sbs a scam?

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

Is 7423.sbs safe to use?

External threat listings 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 7423.sbs?

7423.sbs scored 0 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