context safety score
A score of 40/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 checks user-agent for bot/crawler strings to serve different content
cloaking
Page conditionally redirects based on referrer or user-agent
malicious redirect
When user clicks 'Yes, I'm Interested' on the modal popup, JavaScript redirects the browser to https://smss-lnk.com/aff — an affiliate/redirect URL on a separate domain (smss-lnk.com) that is different from the host site. This is an unsolicited redirect triggered by user interaction with a social-engineering modal. (location: page.html:402, btnYes.onclick handler)
social engineering
A modal popup prompts users with 'Would you like to rent a temporary phone number?' with 'Yes, I'm Interested' and 'No, Thanks' buttons. Both button clicks fire covert tracking beacon requests to /ou.php and /rs.php before any action, recording user decisions. The 'Yes' path redirects to an affiliate link. This modal uses urgency/interest framing to drive conversions to a third-party affiliate destination. (location: page.html:98-405, #myModal)
hidden content
All script tags on the page use a non-standard type attribute ('d0c35e6b9a38e153d5863b17-text/javascript') instead of 'text/javascript'. This causes browsers to not execute the scripts natively — they are instead activated by Cloudflare Rocket Loader (rocket-loader.min.js at the bottom of the page). This obfuscates the true script execution from basic static analysis and security scanners that look for standard script types, effectively hiding the JavaScript behavior from naive inspection. (location: page.html:107, 122, 140, 142, 217, 259, 355, 1175, 1176, 1178, 1183)
prompt injection
The page explicitly lists known AI/bot crawlers in a large botPattern regex (including 'Lighthouse', 'lighthouse', 'AISearchBot', 'Applebot', and many others) and uses isBott() to detect them. While bot detection itself is common, the pattern specifically targets AI indexing agents. Combined with the affiliate modal redirect behavior, this suggests content/behavior may be conditionally altered when an AI agent is detected versus a human user, a classic cloaking/prompt-injection setup to deceive agent-based scanners. (location: page.html:107-120, 259-267 — botPattern regex with isBott() function)
credential harvesting
The site's core function is to provide publicly accessible temporary phone numbers that receive SMS messages from any sender. SMS-based 2FA codes, OTPs, and verification codes sent to these numbers are visible to all visitors. Any attacker can use these numbers to intercept authentication codes for accounts on Gmail, Facebook, WhatsApp, Tinder, and other services listed on the site. The site explicitly advertises this capability for Google, Yahoo, Fiverr, Twitter, Instagram, Facebook, and more. (location: page-text.txt:754, page.html:1124 — 'registering and verifying numerous websites such as Google, Yahoo, Fiverr, Twitter, Instagram, Facebook')
curl https://api.brin.sh/domain/receive-smss.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
receive-smss.com currently scores 40/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.