context safety score
A score of 36/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
encoded payload
suspicious base64-like blobs detected in page content
malicious redirect
script/meta redirect patterns detected in page source
cloaking
Page uses meta refresh redirect
prompt injection
Hidden HTML element contains AI-targeting instructions
brand impersonation
The domain whatsapp.net is not the official WhatsApp domain (whatsapp.com). The HTML contains id='facebook' on the <html> element and loads all resources from static.whatsapp.net, indicating this is a Meta/Facebook-served page rendered under the non-official whatsapp.net domain. The page fully replicates the WhatsApp marketing/login experience including 'Log in', 'Sign up', and 'Download' CTAs, which could deceive users into believing they are on the legitimate WhatsApp site. (location: https://whatsapp.net — page.html line 2, <html id='facebook'>)
credential harvesting
The page presents 'Log in' and 'Sign up' prompts to visitors. Because this is served from whatsapp.net (not whatsapp.com), any credentials entered could be intercepted or harvested. The HTML encodes a Facebook/Meta session infrastructure (DTSG tokens, XAsyncRequest, WebSession modules) behind a WhatsApp branding facade on an alternate domain, creating conditions for credential theft. (location: page-text.txt line 1 — 'Log in', 'Sign up' CTAs; page.html lines 7-10 — DTSG, WebSession module definitions)
phishing
whatsapp.net mimics the official WhatsApp website (whatsapp.com) in full, including branding, feature descriptions, download links, and login flows. The TLS certificate expires in only 7 days (days_until_expiry: 7), which is atypical for a legitimate long-running brand property and consistent with short-lived phishing infrastructure. The domain is not owned by Meta/WhatsApp LLC. (location: metadata.json — tls.days_until_expiry: 7; page-text.txt line 1 — full WhatsApp branding and CTAs)
social engineering
The page uses trust signals from the legitimate WhatsApp brand — privacy messaging ('private messaging', 'end-to-end encrypted', 'Layers of protection'), Meta AI promotion, and official-looking footer with '2026 © WhatsApp LLC' — to build false credibility on a non-official domain, lowering user suspicion before credential entry or app download. (location: page-text.txt line 1 — 'Simple, reliable, private messaging', 'Security', 'Privacy', '2026 © WhatsApp LLC')
curl https://api.brin.sh/domain/whatsapp.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
whatsapp.net currently scores 36/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.