context safety score
A score of 38/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
social engineering
Site explicitly offers a 'Call Bomber' service enabling mass automated harassment calls (up to 1000/hour) to arbitrary Indian phone numbers. It frames this as 'pranking friends' and 'educational purposes' to normalize abusive behavior and lower user inhibitions, while the actual capability is coordinated telephone denial-of-service and harassment. (location: page.html:96-188, page.html:404)
social engineering
SMS Bomber tool advertised alongside the call bomber, soliciting users to send unlimited unsolicited SMS messages to any phone number. Combined with Number Lookup ('Find detailed information about any phone number'), this constitutes a stalking/harassment toolkit. (location: page.html:295-313)
social engineering
Footer and FAQ actively recruit users into a Telegram channel (https://telegram.dog/callbomb) for 'enhanced capabilities' and 'higher limits', funneling victims into an unmonitored platform where further criminal coordination can occur. (location: page.html:464, page.html:390)
hidden content
All JavaScript resources (main.js, bootstrap bundle, AOS library, Google AdSense, Google Analytics) are loaded with a non-standard MIME type 'b1cd6dcfd84f8960de1d8ba1-text/javascript' rather than 'text/javascript'. This is a Cloudflare Rocket Loader obfuscation token, but it also means scripts execute only after the Rocket Loader rewrites their type — delaying and obscuring actual script execution from static analysis tools. (location: page.html:18, page.html:506-509)
obfuscated code
An inline Cloudflare challenge script at the bottom of the page dynamically creates a hidden 1x1 invisible iframe, injects a script into it that sets encoded parameters (r and base64-encoded t value 'MTc3MjYyNjg0MA=='), then loads '/cdn-cgi/challenge-platform/scripts/jsd/main.js'. This pattern is used for bot detection but also obscures page-level behavior from automated scanners and AI agents inspecting the page. (location: page.html:516)
social engineering
The 'Voice SMS Service Provider' section uses authoritative enterprise language ('OTP verification', 'appointment reminders', 'emergency alerts', 'analytics') to reframe an anonymous harassment bombing service as a legitimate business communications platform, lending false legitimacy and potentially deceiving both users and automated content classifiers. (location: page.html:357-370)
social engineering
Disclaimer framing — 'for educational purposes only' and 'pranking friends' — is a superficial legal shield designed to mislead users about the illegality of using the service for harassment, and to prevent platform-level takedowns. The site simultaneously advertises 'speed and anonymity' directly contradicting the stated benign intent. (location: page.html:113, page.html:187, page.html:418)
curl https://api.brin.sh/domain/callbomberz.inCommon questions teams ask before deciding whether to use this domain in agent workflows.
callbomberz.in 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.