Merchant Portfolio Monitor, 5 October 2026: Both Merchants Need Review, Neither Could Be Screened
Window: 28 September to 5 October 2026. Interpretation: both inputs use names reserved for documentation, so I treated them as placeholders, screened them as given, and marked anything I could not verify as "unchecked". Markets are US, UK and EU as supplied. Decisions are recommendations for you to confirm, not legal or compliance advice.
Decision table
| Merchant | Site status | Change since onboarding category | Prohibited or restricted items seen | New complaints (count, worst one linked) | Regulatory notes | Decision and Reason |
|---|---|---|---|---|---|---|
| vitaboost.example (dietary supplements) | Unchecked: fetch failed (502, domain not reachable) | Unchecked | Unchecked. Nothing seen because no page loaded. Policy term at issue: nutraceutical free trials | Unchecked (0 confirmed) | None found in sanctions screen (ComplyAdvantage business sanctions search on "vitaboost", 0 hits, run 5 Oct 2026 via tool gateway). Regulator lists not checked | Review. Inferred: ".example" is a reserved documentation TLD, so this domain should not resolve on the public internet. A supplements merchant cannot be re-screened for free-trial billing without a live site. |
| shop.example.com (women's apparel) | Unchecked: fetch failed (502, domain not reachable) | Unchecked | Unchecked. No policy item seen because no page loaded | Unchecked (0 confirmed) | Unchecked | Review. Observed: the parent domain example.com is registered to IANA as "RESERVED-Internet Assigned Numbers Authority", registered 14 August 1995. Inferred: a real storefront cannot trade on it, so the onboarding record may be wrong or the site may be behind a private network. |
Notes on Review rows
vitaboost.example
- Observed: The homepage fetch returned a 502 "could not connect" error from the fetch tool. No catalog, checkout, refund or terms page could be read.
- Observed: An OpenCorporates name search returned 33 companies with "vitaboost" in the name across several countries, with no link to this domain. Examples include a Wyoming profit corporation, American Vitaboost Inc, active and incorporated 17 February 2025, and an active UK company, Vitaboost Ltd (number 16669183), recently updated on 2 October 2026. Nothing ties either to this merchant.
- Inferred: Name-only matches must not be merged into this row. I did not attribute any of them to the merchant.
shop.example.com
- Observed: The homepage fetch returned a 502 "could not connect" error from the fetch tool (an earlier attempt hit a tool concurrency limit, not a site error). RDAP data for the parent domain shows a last-changed date of 14 August 2026, which is outside the window and is not a merchant change.
- Inferred: Ownership, DNS and company-registry checks cannot say anything about a merchant on a reserved name.
Do next
- Ask the merchant owner or sales team to confirm the real production domain for each row, and correct the onboarding records.
- Once real domains are known, rerun the full screen: live catalog, sitemap, checkout entry, refund and terms pages.
- For the supplements merchant, request its trial and subscription terms and a sample checkout flow, to test the nutraceutical free-trial restriction.
- Request the legal entity name and registration number for both merchants so registry matches are exact.
- Hold any settlement or limit changes until step 2 is done. This is your call, since nothing adverse was found.
Open items
- Wayback Machine comparison: the availability lookup for vitaboost.example returned a rate-limit error (429); it was not run for shop.example.com. Unchecked for both rows.
- Complaint sites (Trustpilot, BBB, Reddit, scam reports), regulator lists (FTC, CFPB, state attorneys general, FCA, ASA, EU consumer authorities) and news searches were not run, because no real domain or trading name could be matched.
- crt.sh and DNS lookups were not run for the same reason.
- Near miss: the many "Vitaboost" entities in company registries show how easily a name match could be wrongly attached to this merchant.
Coverage
Reached: live-site fetch (failed with 502 on both), RDAP for example.com, OpenCorporates, ComplyAdvantage sanctions search. Not reached or not run: Wayback Machine (429), complaints sources, regulator databases, crt.sh and DNS.
Sources
Accessed 5 October 2026.