Is spaceweather.com safe?

suspiciouslow confidence
40/100

context safety score

A score of 40/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.

identity
100
behavior
80
content
0
graph
30

8 threat patterns detected

high

phishing

1 deceptive links where visible host does not match destination host

high

hidden content

A link to a Hindustan Times sponsored post promoting counterfeit Rolex replica watches ('rolex-replica-watches-best-website-to-buy-1-1-rolex-super-clone-for-sale') is embedded inside the 'Spotless Days' statistics paragraph with an empty anchor tag, making it invisible to users while still serving SEO link juice to a counterfeit goods site. URL: https://www.hindustantimes.com/sponsored-post/rolex-replica-watches-best-website-to-buy-1-1-rolex-super-clone-for-sale-101729774089439.html (location: page.html:336 — inside <span class='dailySunCaptionText'> within Spotless Days section)

high

hidden content

A large block of off-topic sponsored links — multiple online casino sites (GamStop, NonGamStop, Norwegian casinos, Dutch casinos, New Zealand slots, German no-deposit bonuses), counterfeit watch sellers (superluxuryreps.com, superclonereps.com, prestigewatches.co), social media follower-selling services (smikky.com, instant-famous.com), real estate listings, a personal injury law firm, and a windshield replacement company — is embedded in the page body framed as 'supporters' and labeled in a hidden HTML comment block as 'YouKnowWhat Block'. These links are styled in small caption text and are contextually irrelevant to the site's space weather content, indicating covert link injection. (location: page.html:1676–1698 (YouKnowWhat Block); page-text.txt:1439–1610; page-hidden.txt:5–6)

medium

social engineering

Multiple counterfeit luxury watch vendors (superluxuryreps.com, superclonereps.com, prestigewatches.co) are promoted using trust-signaling language such as 'Most Trusted seller', 'Premium quality', 'true 1:1 detailing', and 'best super clone watches and rolex replica for sale'. These phrases are designed to legitimize counterfeit goods and deceive visitors into purchasing illegal replica products. (location: page.html:1681–1682, 1695; page-text.txt:1596–1610)

medium

hidden content

Casino and gambling links (languagecoursesuk.co.uk, eventgenius.co.uk, tombrake.co.uk, athenaeumclub.co.uk, bideford.com, onlinecasinoinformatie.com, nongamstop.pieria.co.uk, zamsino.com, kiwislots.nz, betterbonus.com, adlerslots.com, bonuszonderstorting.com, leeuwslots.com, nyecasino.com) are injected using legitimate-looking UK organizational and educational domain names (e.g. languagecoursesuk.co.uk, eventgenius.co.uk, tombrake.co.uk) as anchor targets for gambling content, obscuring the true destination of those links from users and automated safety checks. (location: page.html:1526–1529, 1679–1694)

medium

social engineering

Services for buying social media followers (smikky.com, instant-famous.com) are promoted inline on a trusted science news site, exploiting the site's authority and reader trust to legitimize fraudulent engagement-manipulation services. (location: page.html:1683, 1686; page-text.txt:1598, 1601)

low

hidden content

Unusual HTML comment 'Start of the YouKnowWhat Block' / 'End of the YouKnowWhat Block' intentionally labels the injected sponsored link section with an obfuscated placeholder name rather than a descriptive identifier, suggesting deliberate concealment of the nature of the block from casual code reviewers. (location: page.html:1676, 1698; page-hidden.txt:5–6)

low

hidden content

Facebook SDK script loaded via protocol-relative URL '//connect.facebook.net/en_US/sdk.js#xfbml=1&version=v2.5black' contains the string 'v2.5black' appended to the version parameter, which is not a valid Facebook SDK version string. This anomalous version tag could be used for tracking or fingerprinting, or may indicate a tampered/unofficial SDK load. (location: page.html:92; page-text.txt:7)

API

curl https://api.brin.sh/domain/spaceweather.com

FAQ: how to interpret this assessment

Common questions teams ask before deciding whether to use this domain in agent workflows.

Is spaceweather.com safe for AI agents to use?

spaceweather.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.

How should I interpret the score and verdict?

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.

How does brin compute this domain score?

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.

What do identity, behavior, content, and graph mean for this domain?

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.

Why does brin scan packages, repos, skills, MCP servers, pages, and commits?

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.

Can I rely on a safe verdict as a full security guarantee?

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.

When should I re-check before using an entity?

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.

Last Scanned

March 4, 2026

Verdict Scale

safe80–100
caution50–79
suspicious20–49
dangerous0–19

Disclaimer

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.

start scoring agent dependencies.

integrate brin in minutes — one GET request is all it takes. query the api, browse the registry, or download the full dataset.