Is clouditalia.com 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

6 threat patterns detected

high

phishing

1 deceptive links where visible host does not match destination host

high

brand impersonation

The page is served from clouditalia.com but prominently displays the 'Retelit' brand identity (logo, title 'Retelit - Area Clienti', footer referencing 'Retelit Digital Services S.p.A.'). CloudItalia was acquired by Retelit/Irideos, but the domain mismatch between the serving domain (clouditalia.com) and the displayed brand (Retelit) creates a brand impersonation risk where users may believe they are on an official Retelit domain. (location: page.html:5, page.html:29-30, page.html:105)

high

credential harvesting

A login form collects 'Codice Utenza/User Id' and 'Password' credentials and POSTs them to a relative action endpoint 'wbc_logonopenservice' on the clouditalia.com domain. The form also contains a hidden field 'wc_retpath' pointing to areaclienti.clouditalia.com, and a hidden field 'wc_dbos' with value 'dbeutelia'. The combination of a legacy domain (clouditalia.com), Retelit branding, and credential collection is consistent with a credential harvesting setup or at minimum a deceptive login page. (location: page.html:75-88)

high

phishing

The URL is clouditalia.com but the page title, logo, and footer all display Retelit branding. Users receiving a link to this domain expecting to reach Retelit's customer portal may not recognize the domain mismatch and willingly submit credentials. The page instructs users that they need their 'Codice Utente e la password' communicated during contract activation, mimicking a legitimate ISP customer portal to elicit credential entry. (location: page.html:5, page.html:73-74, metadata.json:1)

medium

hidden content

A hidden form field 'wc_retpath' contains a hardcoded redirect URL (https://areaclienti.clouditalia.com/index.php?option=com_content&task=view&id=6&Itemid=63) submitted with credentials. Another hidden field 'wc_dbos' exposes an internal database/service name ('dbeutelia'). These hidden fields are not visible to the user and manipulate post-login behavior without disclosure. (location: page.html:84-86)

medium

malicious redirect

The hidden field 'wc_retpath' specifies a post-authentication redirect to areaclienti.clouditalia.com with a Joomla-style URL. This redirect is injected into the form as a hidden parameter and controls where the user is sent after credential submission, which could be manipulated to redirect to an attacker-controlled destination if the parameter is not validated server-side. (location: page.html:84)

API

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

FAQ: how to interpret this assessment

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

Is clouditalia.com safe for AI agents to use?

clouditalia.com 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 5, 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.