context safety score
A score of 43/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
cloaking
Page loads content in transparent or zero-size iframe overlay
malicious redirect
Two external script tags load JavaScript from unrelated domains 'extreme-ip-lookup-com.com' and 'ww2-extreme-ip-lookup-com.eu' — both are typosquat/lookalike domains of the legitimate site 'extreme-ip-lookup.com'. These scripts execute with full page privileges and could perform credential theft, session hijacking, or arbitrary code execution. The domains differ from the canonical domain in non-obvious ways (hyphenated TLD, EU subdomain format). (location: page.html:2038-2039)
hidden content
Multiple content blocks are rendered with 'display:none' and revealed only via JavaScript after page load, including the main content div (#mainContentDiv), header (#header), homepage IP input (#homepageIPInput), and footer (#footerDiv). This deferred-reveal pattern conceals the true page structure from static scanners and can hide content from security tools while showing it to users. (location: page.html:339,998,1000,1437,1782)
hidden content
A span element containing promotional content ('We block IPs and websites going over the limits, get the Pro Package if your requests are important!') is explicitly set to display:none in the HTML, keeping it invisible to users but present in the DOM. (location: page.html:1541,1673)
credential harvesting
A live Stripe public key ('pk_live_mCSYlggRFOBmQDp8selrHAjf') is embedded directly in the page JavaScript. While public keys are less sensitive than secret keys, their exposure allows attackers to identify the payment processor, craft targeted Stripe-based phishing flows, or enumerate account details. Combined with the suspicious external scripts (lines 2038-2039), this key could be exfiltrated and abused. (location: page.html:28)
hidden content
A live API key ('Qn97RtiI2gwjStzJJjuG') for the extreme-ip-lookup.com JSON API is hardcoded and exposed in client-side JavaScript, used for dynamic IP lookups via JSONP script injection. Any visitor can extract and abuse this key to make unlimited authenticated API calls. (location: page.html:1405,1768)
social engineering
The page explicitly promotes and documents adding hidden input fields with company details (company name, website, email) to newsletter signup, MailChimp, download, and lead generation forms without visitor awareness. This describes a covert data collection technique targeting website visitors of customers who use the API. (location: page-text.txt:1181-1182)
curl https://api.brin.sh/domain/extreme-ip-lookup.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
extreme-ip-lookup.com currently scores 43/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.