Is es.danskporno.info safe?

suspiciousmedium confidence
49/100

context safety score

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

identity
90
behavior
80
content
17
graph
77

6 threat patterns detected

high

phishing

10 deceptive links where visible host does not match destination host

high

malicious redirect

Multiple video thumbnail links (approx. 10 instances) point to 'https://es.danskporno.info/link.php' rather than a real video page. These are opaque redirect endpoints with no disclosed destination, consistent with traffic-monetization or malicious redirect chains used by adult spam networks. (location: page.html lines 100, 106, 113, 120, 142, 146, 150, 153, 156 — href='https://es.danskporno.info/link.php')

medium

social engineering

The site uses deceptive SEO keyword stuffing throughout its footer and tag cloud — including terms like 'brazzers en español latino', 'pornhub latino', and dozens of misspelled variants (pormo, ponolatino, pirno) — to lure users searching for recognizable brand-name adult platforms into visiting this third-party site and clicking its opaque redirect links. (location: page.html lines 263–264, page-text.txt lines 182–183)

medium

brand impersonation

The page explicitly uses the brand names 'Brazzers' and 'PornHub' (as 'brazzers en español latino', 'porn hub latino', 'pornhub latino') as keyword anchors and tag links to attract users who believe they are accessing official brand content, while the site is an unaffiliated third party. (location: page.html line 263 — tag anchors for 'brazzers en español latino' and 'porn hub latino'; page-text.txt line 182)

low

hidden content

The footer contains a block of multilingual links (Japanese, Italian, Persian, Hungarian, Vietnamese) rendered in white text on a white/near-white background area (div styled color:white) pointing to xxxfatpornvideos.com subdomains. These are visually camouflaged cross-site link-farm entries not meaningfully visible to users. (location: page.html lines 264–270 — footer div with color:white containing off-domain links to xxxfatpornvideos.com and its language subdomains)

medium

malicious redirect

The footer contains an extensive off-domain link farm pointing to over 40 distinct external adult domains (e.g. es.porncomixvideos.com, es.xxxpornmoviesxxx.com, es.sexyhomemadeporn.com, kartuliporno.net, etc.) disguised as SEO text links. This pattern is consistent with link-exchange rings used by malvertising and PPI (pay-per-install) networks. (location: page.html lines 245–261 — footer SEO link block with >40 external adult domains)

API

curl https://api.brin.sh/domain/es.danskporno.info

FAQ: how to interpret this assessment

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

Is es.danskporno.info safe for AI agents to use?

es.danskporno.info currently scores 49/100 with a suspicious verdict and medium 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 26, 2026

Verdict Scale

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

Trust Graph

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.