Is sobeautifulstneots.co.uk safe?

suspiciouslow confidence
37/100

context safety score

A score of 37/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.

identity
100
behavior
60
content
0
graph
30

13 threat patterns detected

medium

encoded payload

suspicious base64-like blobs detected in page content

high

phishing

1 deceptive links where visible host does not match destination host

high

js obfuscation

JavaScript uses Function constructor for runtime code generation

critical

malicious redirect

The scanned domain sobeautifulstneots.co.uk serves content that is entirely from a different site (englishmastiffs.co.za), a Vietnamese adult content site branded 'HeoVL'. The canonical URL, all internal links, og:url, og:image, and all asset references point to englishmastiffs.co.za rather than sobeautifulstneots.co.uk. This is a classic domain hijack/cloaking redirect where an unrelated legitimate-looking domain silently proxies or redirects to a third-party site. (location: page.html:<link rel=canonical>, og:url, all href/src attributes)

high

hidden content

All JavaScript resources are loaded with a non-standard type attribute value '75ebdb4ec7ff9ccc6bb09799-text/javascript' instead of the standard 'text/javascript'. This is a Cloudflare Rocket Loader obfuscation technique that defers script execution, but it also masks the true script types from basic scanners and makes it difficult to determine which scripts execute at load time versus deferred. Multiple scripts including Google Analytics, jQuery, and inline business logic use this non-standard type. (location: page.html:lines 8,63,64,280,348,435,3161,3179,3180,3181,3184)

high

obfuscated code

A script at page load intercepts and monkey-patches HTMLScriptElement.prototype's 'src' setter to strip query parameters from all dynamically injected script URLs (val.split('?')[0]). This tampers with the browser's native script loading mechanism and could be used to prevent tracking parameters on malicious scripts or to bypass CSP/SRI checks that rely on exact URL matching. (location: page.html:lines 8-30)

high

malicious redirect

An ad banner in the catfish-bottom section links directly to a raw IP address: https://154.82.109.161/1825738.html. Linking to bare IP addresses in banner ads bypasses domain reputation systems and is a common technique for routing users to malicious or unlisted ad servers. (location: page.html:line 3100 - catfish-bottom banner href)

high

obfuscated code

A third-party script is loaded from https://synurl.vip/synurl-script in the footer. The domain 'synurl.vip' is an unrecognized external script host with no transparent purpose declared on the page. Combined with a countdown element (#brv-synurl-countdown), this pattern is consistent with traffic monetization scripts that perform background redirects, ad injection, or user tracking without disclosure. (location: page.html:line 3161 - <script src='https://synurl.vip/synurl-script'>)

high

brand impersonation

The page is served from sobeautifulstneots.co.uk (a UK domain suggesting a beauty salon business in St Neots) but the actual content is an adult entertainment site (HeoVL/englishmastiffs.co.za). The legitimate-sounding UK domain is being used to impersonate or mask the true nature of the content, likely to evade blocklists, pass link-building checks, or mislead users and crawlers about the site's identity. (location: metadata.json:domain=sobeautifulstneots.co.uk vs page.html title/canonical pointing to HeoVL adult site)

medium

malicious redirect

Multiple ad links use URL shortener/tracker domains including ln.run/bet88ads, ln.run/pg88ads, uepjdd.cc/JYGtNp, uepjdd.cc/7L2W8p, and vtd.codes/. These opaque redirect chains obscure the final destination and are commonly used to funnel users through affiliate tracking systems or to sites that change targets over time. The uepjdd.cc links also contain a literal unfilled template placeholder '{banner}' suggesting automated/programmatic ad injection. (location: page.html:lines 431,444,3100,3110 - catfish-top and catfish-bottom ad banners)

medium

hidden content

The HTML lang attribute is set to 'vi' (Vietnamese) and all meta geo tags indicate Ho Chi Minh City, Vietnam, while the page is served from a .co.uk domain suggesting a UK-based business. The footer also credits '© 2025 ENGLISHMASTIFFS.CO.ZA' while the scanned URL is sobeautifulstneots.co.uk. This multi-layer identity mismatch is used to confuse automated classification systems and search engine crawlers about the site's true origin and content. (location: page.html:line 2 (lang=vi), lines 49-51 (geo meta tags), line 3158 (footer copyright))

medium

social engineering

The footer 'LIÊN KẾT' (links) section contains links to multiple unrelated .co.uk domains (benedictionfilm.co.uk, tocapitall.co.uk, simplyheatingltd.co.uk) labeled as 'VLXX' and 'Sex Việt', suggesting a network of hijacked or compromised legitimate UK business domains being used as a link farm to boost SEO for adult and gambling sites. This cross-domain link network is designed to manipulate search rankings and launder traffic. (location: page.html:lines 3148-3152 - footer LIÊN KẾT section)

low

prompt injection

The Yoast SEO schema.org JSON-LD block embeds a rich organizational description with Vietnamese text, alternate names, and structured data pointing to englishmastiffs.co.za while the scanned URL is sobeautifulstneots.co.uk. AI crawlers and LLM-based search agents ingesting this structured data would be fed false organizational identity information, potentially causing them to misclassify or misrepresent the site's content and affiliation. (location: page.html:line 48 - application/ld+json Yoast schema graph)

API

curl https://api.brin.sh/domain/sobeautifulstneots.co.uk

FAQ: how to interpret this assessment

Common questions teams ask before deciding whether to use this domain in agent workflows.

Is sobeautifulstneots.co.uk safe for AI agents to use?

sobeautifulstneots.co.uk currently scores 37/100 with a suspicious verdict and low confidence. The goal is to protect agents from high-risk context before they act on it. Treat this as a decision signal: higher scores suggest lower observed risk, while lower scores mean you should add review or block this domain.

How should I interpret the score and verdict?

Use the score as a policy threshold: 80–100 is safe, 50–79 is caution, 20–49 is suspicious, and 0–19 is dangerous. Teams often auto-allow safe, require human review for caution/suspicious, and block dangerous.

How does brin compute this domain score?

brin evaluates four dimensions: identity (source trust), behavior (runtime patterns), content (malicious instructions), and graph (relationship risk). Analysis runs in tiers: static signals, deterministic pattern checks, then AI semantic analysis when needed.

What do identity, behavior, content, and graph mean for this domain?

Identity checks source trust, behavior checks unusual runtime patterns, content checks for malicious instructions, and graph checks risky relationships to other entities. Looking at sub-scores helps you understand why an entity passed or failed.

Why does brin scan packages, repos, skills, MCP servers, pages, and commits?

brin performs risk assessments on external context before it reaches an AI agent. It scores that context for threats like prompt injection, hijacking, credential harvesting, and supply chain attacks, so teams can decide whether to block, review, or proceed safely.

Can I rely on a safe verdict as a full security guarantee?

No. A safe verdict means no significant risk signals were detected in this scan. It is not a formal guarantee; assessments are automated and point-in-time, so combine scores with your own controls and periodic re-checks.

When should I re-check before using an entity?

Re-check before high-impact actions such as installs, upgrades, connecting MCP servers, executing remote code, or granting secrets. Use the API in CI or runtime gates so decisions are based on the latest scan.

Learn more in threat detection docs, how scoring works, and the API overview.

Last Scanned

March 4, 2026

Verdict Scale

safe80–100
caution50–79
suspicious20–49
dangerous0–19

Disclaimer

Assessments are automated and may contain errors. Findings are risk indicators, not confirmed threats. This is a point-in-time assessment; security posture can change.

start scoring agent dependencies.

integrate brin in minutes — one GET request is all it takes. query the api, browse the registry, or download the full dataset.