# Impact Capital connection and domain history second pass


## Later network-review update · 5 November 2026

The subsequent [two-network investigation](network-connection-investigation.md) recovered a specific infrastructure link: `globaltreasury.solutions` shares IPv4 **83.228.211.130** with `mail.zingalabs.org`, the current MX destination for Impact, GRiOT and Zinga. Historical provider address intervals overlap, without proving uninterrupted use or historical MX configuration. This updates any earlier broad statement below that no Global-to-Impact link was recovered. **The reported HTTP redirect remains unverified, and the link from company 15907803 or the named individuals to operation of the Global domain remains unestablished.** The original pass's observations and access failures are retained as research history.


Prepared 5 November 2026 for case SP-GTS-001. This report builds on the first domain and corporate-record reports. It reviews new public identifiers and alternative retrieval routes, rather than treating earlier failed searches as final evidence.

## Main result

The **Global Treasury domain’s registry record was retrieved successfully**. It records registration on **22 January 2026 at 13:12:55.802 UTC**, one day before the certificate event already found. This is new, primary registration evidence supporting a January infrastructure chronology. It still does not prove a website launch, trading, legal operator or ownership by UK company 15907803.

Impact’s domain record was also retrieved. It records registration on **24 September 2023**, a later transfer event in September2026 and current Cloudflare registrar service. The registrar publishes Switzerland/Vaud as registrant geography but redacts the name. This corroborates geography only; it does not identify Ivan, Elena, the Swiss company or a beneficial owner.

**No independently verified GTS-to-Impact bridge emerged.** Fresh root/www and HTTP/HTTPS alternatives all encounter the expired GTS certificate after any protocol upgrade. The current Impact-to-studio redirect remains captured separately. The live Impact careers and news routes are placeholders, and reviewed service pages name no case subjects or customers. A separate Swiss current-extract attempt reached an explicit internal-server-error page.

The requester has already confirmed CAPITALIXE LTD 11853977 as the original business. The old wording in the latest brief describing that business as unidentified is therefore not adopted here.

## Findings and source references

### IC2-01 Global Treasury domain registration

**Status:** Documented in retrieved registry record.

- **Source title and URL:** Identity Digital registry RDAP for `globaltreasury.solutions`, [direct registry response](https://rdap.identitydigital.services/rdap/domain/globaltreasury.solutions), reached through `https://rdap.org/domain/globaltreasury.solutions`.
- **Retrieved:** 2026-11-05 at 11:47:42.807398 UTC.
- **Event:** `registration` gives `2026-01-22T13:12:55.802Z`; the record separately gives `last changed` on 11 August 2026. Current registrar is GoDaddy, IANA 146; nameservers are `ns43.domaincontrol.com` and `ns44.domaincontrol.com`.
- **Location:** `events`, the registrar entry under `entities`, and `nameservers` in `sources/pass-2-impact/global-rdap.body`.
- **Entities:** `globaltreasury.solutions`; no named registrant was established.

This gives a separate registration event immediately preceding the previously observed certificate validity/SCT dates of23 January 2026. Do not replace the registration date with the certificate date, or either with a launch or first-trade date. The registry’s last-change field does not say what changed or establish an ownership transfer. The linked public GoDaddy registrar endpoint returned HTTP 429 and was not retried.

### IC2-02 Impact domain registration and redacted geography

**Status:** Documented in retrieved registry and registrar records.

- **Sources:** [Identity Digital registry](https://rdap.identitydigital.services/rdap/domain/impactcapital.ltd), retrieved 2026-11-05 at 11:48:37.914851 UTC; [Cloudflare registrar RDAP](https://rdap.cloudflare.com/rdap/v1/domain/impactcapital.ltd), retrieved at 11:51:24.875771 UTC.
- **Events:** registration24 September 2023 at19:42:54.432 UTC; transfer28 September 2026 at18:55:46.828 UTC; last changed3 October 2026. Registrar: Cloudflare, IANA 1910. Nameservers: `sid.ns.cloudflare.com` and `jule.ns.cloudflare.com`.
- **Location:** Registry `events`; registrar `entities` entry with role `registrant`, whose name is redacted and address exposes country CH and region Vaud.
- **Files:** `impact-rdap.body`, `impact-registrar-rdap.body`, with adjacent exact request metadata.

The registration predates GTS’s incorporation. That neither proves nor disproves a later business relationship. A registry transfer event is not proof that beneficial ownership changed. The geography is consistent with Impact’s Swiss website attribution but cannot independently identify that operator or a case subject. The registrar’s public contact relay was not used.

### IC2-03 Current redirect refresh and GTS blocker

**Status:** Documented HTTP/TLS observations.

The fresh Impact HEAD chain records **HTTP 301** from `https://impactcapital.ltd/` to `https://studio.impactcapital.ltd/`, followed by **HTTP 200**. Header server dates run from11:50:59 to11:51:09 UTC; the actual local write-completion capture time is in `header-capture-meta.json`. The separately preserved ordinary GET completed at 11:47:44.769689 UTC and followed the same final host.

The GTS HTTP first hop remains **HTTP 301** to its own HTTPS root. Four ordinary validated alternatives were tested: root HTTPS, root HTTP with redirects, www HTTPS and www HTTP with redirects. Every attempt stopped on certificate expiry. The individual `global-*-meta.json` files preserve actual attempt timestamps and error messages. No certificate exception was used, and no HTTPS page or further redirect was read after that failure.

This is a specific retrieval blocker. It is not evidence that the requester’s previous GTS-to-Impact observation was false or that the redirect never existed. The already documented archive rate limits and Common Crawl gateway errors also remain limitations, not zero-capture findings.

### IC2-04 Public trading and staffing footprint check

**Status:** Documented website representations and bounded negative search.

Newly reviewed public routes include [Jobs](https://studio.impactcapital.ltd/jobs), [News](https://studio.impactcapital.ltd/news), [Venture Studio](https://studio.impactcapital.ltd/venture-studio), [Industries](https://studio.impactcapital.ltd/industries) and [Finance and Trading](https://studio.impactcapital.ltd/industries/finance-trading). They were retrieved by ordinary HTTPS between11:49:26 and11:49:35 UTC; each has a raw HTML file, visible-text derivative and exact metadata sidecar.

The jobs and news pages both say **“Content coming soon.”** The studio describes venture-building and links its already identified platform family. The finance route advertises brokerage and DeFi services focused on Sub-Saharan Africa. No case names, UK company numbers, supplied treasury domains, named customer transactions or completed-deal dates appeared in these reviewed text derivatives.

This supports a description of what the site advertises. It does not establish actual delivery, revenue, a customer relationship, absence of trading, common ownership or succession from GTS. Generic overlap with payments or treasury vocabulary remains insufficient.

The homepage’s actual public links exposed jobs/news and industry routes. Its `robots.txt` was retrieved; `sitemap.xml` returned 404. No public PDF or named-team link was discovered through those checked routes. The password-protected venture route remains unaccessed.

### IC2-05 Current Swiss record and regulatory checks

**Status:** Documented availability/search observations, with unresolved regulatory scope.

The exact cantonal link supplied by the official register was retried using direct HTTP and a normal browser: [Swiss extract endpoint](https://prestations.vd.ch/pub/101266/extract?lang=FR&companyOfsUid=CHE-464.300.033). Direct HTTP returned a small application shell; the browser displayed **“Internal Server Error”** and a request to try later. `swiss-extract-browser.json` preserves the final URL, visible text, timestamp and console error. The fresh Swiss UID request timed out. The previously retrieved official UID and populated Zefix records are retained with their original provenance; neither failure replaces them with a claim of current deregistration or current ownership.

The Swiss browser failure was recorded at **11:50:16.119 UTC** on 5 November 2026. Its final URL was the registry application root after the extract navigation; it was not a populated extract.

The [FINMA public authorisation search](https://www.finma.ch/en/finma-public/authorised-institutions-individuals-and-products/) was used normally with `IMPACT CAPITAL MANAGEMENT` and returned **0 results**. The query, visible result and capture time are preserved in `finma-name-search.json` and its screenshot. FINMA warns that list inclusion can lag authorisation changes. Its separate [SRO membership search](https://www.finma.ch/en/authorisation/self-regulatory-organisations-sros/sro-member-search/) returned no populated result after normal search and Enter; no definitive zero count was displayed, so that route remains inconclusive.

The authorisation-search response was captured at **11:52:22.092 UTC**, and the SRO-search state at **11:52:57.279 UTC**, both on 5 November 2026. These are query observation times, not authorisation-event dates.

These observations do not establish that the company needs a particular licence, lacks SRO membership or acted unlawfully. The reviewed website material does not establish precisely which regulated activity was actually carried on. No regulator or subject was contacted.

## Research queue and dispositions

| Lead ID | Origin and research question | Priority | Approaches and findings | Disposition and next action |
| --- | --- | --- | --- | --- |
| IC2-L01 | Supplied GTS website and reported January launch. When was the domain registered? | High | Registry redirect discovery and primary RDAP succeeded;22 January 2026 registration. | Supported registry finding IC2-01. Domain attribution and launch/trading remain open. |
| IC2-L02 | Requester-reported GTS→Impact path. Can it be independently reproduced? | High | Root/www and HTTP/HTTPS alternatives; first-hop headers; exact-domain web searches; independent Bing RSS. GTS TLS expiry persists. | Documented live-fetch blocker. Seek an attributable preserved redirect/page or a functioning independent historical capture. Do not bypass expiry. |
| IC2-L03 | Impact legal page’s exact Swiss UID. Who owns the domain and operates the business? | High | Registry and registrar RDAP; redacted CH/Vaud registrant; legal-page refresh; prior official UID/Zefix retained. | Website operator attribution and geography supported separately. Named domain registrant/current beneficial ownership unresolved; cantonal extract unavailable. |
| IC2-L04 | Public homepage links. Are there staff, recruitment, partner or dated deal disclosures? | Medium | New jobs/news/studio/industry routes; jobs/news placeholders; generic marketing without named case customers or subjects. | Bounded pages reviewed. No attributable trading or case connection found; not evidence of no trading. |
| IC2-L05 | Swiss finance/brokerage marketing. Is an applicable public regulatory record identifiable? | Medium | Exact-name FINMA authorisation search 0; separate SRO search inconclusive; indexed exact UID/name checks yielded no attributed record. | Regulatory status remains unresolved; no classification of actual services or unlawful-activity conclusion. |
| IC2-L06 | Historic Swiss manager/former name discovered earlier. Does a professional, court or notice source bridge the case? | Medium | Exact full-name/company/UID searches; prior primary 2016 notices retained. Unrelated entities and name-only matches discarded. | No case-specific bridge identified in reviewed results. Do not attribute another entity’s proceedings to Impact or the UK subjects. |
| IC2-L07 | Need for a materially different search route after prior archive failures. | Medium | Bing RSS exact-domain and pair queries both returned 200 but supplied irrelevant results unrelated to the query; XML preserved. | This route did not produce usable evidence. It cannot establish that the exact terms have no indexed results. Prior archive 429/504 remain recorded blockers. |

Detailed query batches and their outcomes are in `sources/pass-2-impact/web-search-log.json`. Query-log write times are distinguished from exact source retrieval timestamps. The independent search route produced unusable results; it is not counted as a comprehensive absence finding.

## Implications for the case record

1. Add **22 January 2026 domain registration** to the timeline before the 23 January certificate event. Keep the requester’s month-only launch claim separate.
2. Keep GTS→Impact as reported/unverified. Only Impact→studio is an observed redirect.
3. Keep the Swiss company, Impact domain and website operator attribution distinct. Do not draw an ownership edge from redacted country/region data.
4. The new public-route review does not supply named trading evidence, customer overlap or a successor relationship. Keep those research tasks open with their specific evidence needs.
5. Current Swiss ownership and regulatory status should not be inferred from unavailable extracts or no-hit searches.

All collected files are under `research/sources/pass-2-impact/`. Its `manifest.json` records byte counts and SHA-256 hashes; metadata files give actual request/capture times. Hashes detect changes to saved files and do not independently establish authenticity or admissibility. No contacts, authentication, forms, new scans, paid searches or certificate bypass occurred.