context safety score
A score of 43/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
cloaking
Page loads content in transparent or zero-size iframe overlay
brand impersonation
The site uses the XVideos favicon (xvideos-favicon.png) and branding assets as its own favicon and logo, impersonating the well-known XVideos adult platform. The schema.org alternateName is explicitly set to 'Novinha Bucetuda - Xvideos Legendado de Incesto', reinforcing the impersonation to attract traffic associated with the legitimate XVideos brand. (location: page.html:27, page.html:42-44, page.html:83-86 — favicon and og:image use xvideos-favicon.png assets; schema.org alternateName at line 46)
hidden content
A text block containing SEO keyword-stuffed descriptions (Videos de Sexo com Legenda, Contos Eróticos Brasileiros, Xvideos as Panteras, Xvideos de Novinhas) is rendered with 'display: none' via the div#texto_home element, hiding it from casual visitors but exposing it to search engine crawlers. This is a cloaking/hidden SEO spam technique. (location: page.html:403 — div#texto_home with inline style 'display: none;'; page-hidden.txt lines 1-11)
hidden content
A zero-dimension tracking pixel (width=0, height=0) from whos.amung.us is embedded inside a span with 'display:none', silently tracking visitor counts without any visible disclosure to users. (location: page.html:1043-1044 — <span style="display:none;"><img src="https://whos.amung.us/swidget/47nnqwm80q.gif" width="0" height="0">)
malicious redirect
Two popunder/pop ad scripts from xtraffix.com are loaded unconditionally at page load. These scripts (pop.php and popunder.php) are well-known for triggering unsolicited popunder windows that redirect users to third-party sites, including potentially malicious or scam pages, without user consent. (location: page.html:1051 — <script src="https://xtraffix.com/ads/pop.php?c=276&v=030403"> and <script src="https://xtraffix.com/ads/popunder.php?c=276&v=030403">)
social engineering
The footer copy actively solicits users to submit their own videos for cataloguing ('mande seus videos para catalogar aqui') and encourages bookmarking the site, using manipulative language designed to increase user engagement and return visits to an ad-monetized adult content farm. (location: page.html:1007-1013 — footer copy text)
hidden content
CSS rule '.m18lochide,.m18locsh{display:none;}' hides elements with classes m18lochide and m18locsh. These classes are applied to native ad list items (li.m18native), which contain inline ad units (data-revive-zoneid). The elements are hidden from certain visitors (likely based on age/geo via user-location.js) but the ad content is still served, suggesting conditional content cloaking tied to the user-location.js geolocation script. (location: page.html:83 — inline style block; page.html:454, 520 — li.m18native elements; page.html:1045 — user-location.js script)
brand impersonation
Post titles and category URLs embed third-party brand names (e.g., 'Sexo4k', 'TubePorn', 'IncestoBR', 'SuperPorno') to piggyback on the search visibility of those brands and divert their audience traffic to this site. (location: page.html:590, 608, 626, 824 — article titles containing third-party brand names in URLs and headings)
curl https://api.brin.sh/domain/novinhabucetuda.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
novinhabucetuda.com currently scores 43/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.
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.
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.
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.
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.
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.
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.
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.
integrate brin in minutes — one GET request is all it takes. query the api, browse the registry, or download the full dataset.