context safety score
A score of 38/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
phishing
Domain funinmatch360.com is only 119 days old, a pattern strongly associated with phishing infrastructure. Newly registered domains are routinely used for short-lived phishing campaigns before being burned. (location: metadata.json: whois.domain_age_days=119)
phishing
TLS connection failed (connected=false, cert_valid=false). A site that cannot serve a valid HTTPS connection is either misconfigured or a staged/inactive phishing landing page. Legitimate services consistently maintain valid TLS. The SAN mismatch (san_match=false) further suggests the certificate, if any, does not belong to this domain. (location: metadata.json: tls.connected=false, tls.cert_valid=false, tls.san_match=false)
brand impersonation
The domain name 'funinmatch360.com' uses a numeric suffix ('360') and generic entertainment/social framing ('fun','match'), a common pattern in brand-impersonation and romance-scam domains that mimic legitimate dating or social platforms (e.g., Match.com, Match360 variants). (location: metadata.json: domain=funinmatch360.com)
social engineering
The domain construction ('funinmatch360') targets social/romantic engagement themes. Domains constructed around 'fun', 'match', and numeric identifiers are frequently used in romance scams and social-engineering lures designed to harvest personal information or payment credentials. (location: metadata.json: domain=funinmatch360.com)
hidden content
Page HTML, visible text, and hidden content files are all empty despite the domain resolving to a URL. This blank-page pattern is consistent with cloaking techniques where content is served only to real victims (e.g., based on geolocation, referrer, or user-agent), while scanners and bots receive an empty response. (location: page.html, page-text.txt, page-hidden.txt: all files empty)
phishing
Hosting reputation is unknown and no blocklist entry exists yet. Combined with the young domain age and failed TLS, this suggests a newly stood-up phishing site that has not yet been reported — a common state for targeted or low-volume phishing campaigns. (location: metadata.json: hosting.reputation=Unknown, blocklist.listed=false)
curl https://api.brin.sh/domain/funinmatch360.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
funinmatch360.com currently scores 38/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.