Is outbidplacardshowman.com safe?

suspiciousmedium confidence
47/100

context safety score

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

identity
80
behavior
100
content
20
graph
30

6 threat patterns detected

medium

encoded payload

suspicious base64-like blobs detected in page content

high

brand impersonation

The domain outbidplacardshowman.com serves a page that fully impersonates Clickadu s.r.o.'s official privacy policy, using Clickadu's logo (embedded as a base64 SVG), branding, company address, and linking repeatedly to clickadu.com. The domain has no apparent affiliation with Clickadu, creating a deceptive mirror of the legitimate company's policy page. (location: page.html:4, page.html:5, page.html:154, page.html:159-160)

high

social engineering

The page poses as a legitimate privacy/unsubscribe portal operated by the Clickadu ad network. It presents an 'Unsubscribe' button that silently POSTs a JSON payload (including a timestamp) to /unsubscribe on the attacker-controlled domain. Users believing they are opting out of notifications are instead confirming their browser session to a hostile endpoint, potentially being tracked or profiled. (location: page.html:272-277, page.html:323-365)

medium

hidden content

The 'Subscription Management Guide' section is hidden by default via CSS class 'collapse:not(.show) { display: none }'. This collapsible section is not visible on page load and contains detailed instructions guiding users to manipulate browser notification settings, which could be used to prevent users from blocking the ad network's push notifications. (location: page.html:87-89, page.html:186-253)

medium

social engineering

The page includes a 'Subscription Management Guide' that instructs users step-by-step on managing push notification permissions in Chromium, including a direct chrome:// settings URL. This content is designed to help users 'unsubscribe' but may be used to confuse or misdirect users about which domains to block, potentially keeping the malicious ad network's notification permissions intact. (location: page.html:182-253, page-text.txt:31-103)

medium

malicious redirect

Multiple 'More...' links throughout the page point to clickadu.com/privacy and clickadu.com/contact. These links open in a new tab (target='_blank') and redirect users from the unaffiliated domain outbidplacardshowman.com to the legitimate Clickadu site, lending false credibility to the impersonation page and potentially facilitating referral tracking or additional redirect chains. (location: page.html:160, page.html:168, page.html:261, page.html:268, page.html:292, page.html:300)

API

curl https://api.brin.sh/domain/outbidplacardshowman.com

FAQ: how to interpret this assessment

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

Is outbidplacardshowman.com safe for AI agents to use?

outbidplacardshowman.com currently scores 47/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 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.