Paid foursigtics.com? How to ask your bank for your money back
foursigtics.com was a documented lookalike storefront copying Four Sigmatic. We published what it served on 17 August 2026. On 6 October 2026 the observed state was “resolves but not serving — HTTP 522”. If you paid it while it was up, the route to your money runs through your card issuer or bank — not through the store, and not through us.
foursigtics.com — resolves but not serving — HTTP 522.
Read this before you buy anything on this page. The $19 pack is a dated record of what this address served on 17 August 2026 — the day we checked it, and near the day you were most likely charged. That record does not become less true because the address stopped answering afterwards. What it is not: a claim that the site is up today, and not a takedown — a server answering that status is not enforcement, which would mean a registry status code (clientHold or serverHold) read back off the record, and we have read none for this hostname. We do not recover funds and we make no promise about your dispute.
We are not your bank, not a law firm and not a fund-recovery service. We cannot tell you whether a dispute will succeed, how long one takes, or what your issuer's rules are — only your issuer can. What we hold is a dated record of what this web address served on the day we checked it.
Get proof for your bank — $19
We hold a dated record of what foursigtics.com served — it copies Four Sigmatic, recorded 17 August 2026. The Dispute Evidence Pack turns that into a document you can attach to a chargeback or dispute with your bank or card issuer.
When we last checked, on 6 October 2026: resolves but not serving — HTTP 522. The pack is the dated record of what that address served on 17 August 2026 — it does not claim the site is up today, and buying it does not take any site down.
- The dated record above in full: what foursigtics.com served, the date we checked it, and the real brand it copies (Four Sigmatic) — quoted from our own published research, never rewritten to suit a dispute.
- 10 numbered exhibits (E1–E10), each quoting one artefact we documented at this address, dated, with what it supports written beside it.
- A ready-to-attach written statement addressed to a bank or card-issuer dispute team — 29 lines, 16 of them blacked out in the sample below — with bracketed spaces for your own name, card, dates and description of what happened.
- The disclaimer reproduced on the document itself, so whoever reads it can see exactly what this record is and what it is not.
- Delivered to your order page within moments, with the link emailed to you. No new research runs — this evidence is already on file, so there is no wait.
- One-time $19. No subscription, no account, nothing recurring, and no further charge of any kind.
When it arrives, and in what form: the moment your payment goes through, the pack appears on your own order page — a web page you can read, copy from, print or save from your browser, with the written statement in a copy-to-clipboard block so it can be pasted straight into an online dispute form. Nothing is researched or generated first; the evidence is already on file. We email you the link as well, so you can open it again from your phone when your issuer asks for it.
One-time $19 — no account, no subscription, nothing recurring.
Nothing to fill in on this page — it already knows which web address the pack is for. The button goes straight to the card form, handled by Stripe, and the only details asked for there are the ones needed to take the payment.
On the price: $19 once — the only payment on this page, no subscription, no account, nothing recurring. Weigh it against the amount you have already paid foursigtics.com, because that is the number this decision is really against. And if you would rather spend nothing at all, the dated record it is built from is published free on this page and you are welcome to quote it to your issuer yourself.
Why pay when free scanners are free: on 2 September 2026 ScamAdviser's page for one hostname in this index, nomaticstore.com, read “Likely Safe - we think nomaticstore.com is legit” — on an analysis it described as 3 days old — while our own cache-bypassed check that same day recorded it serving a Nomatic lookalike storefront with around 40 of its images loading from nomatic.com, the genuine brand's own domain. Free scores are worth running and cost nothing; what they are not is a dated, itemised record of what an address served, which is what this pack is. Both readings, side by side, with their dates.
On timing: our record of 6 October 2026 does not expire, but a dispute is not something to sit on. Your bank or card issuer sets its own process and its own deadlines, and only they can tell you what applies to your payment — so ask them that question early rather than late. We cannot tell you how long you have, and nothing here promises a dispute will succeed.
What we do not promise: we cannot say whether your bank or card issuer will refund the payment, how long they take, or whether they will accept a claim at all — that decision is theirs alone. This pack is a dated factual record, not legal advice, and no money passes through us.
Never heard of us? Who we are, how each copy is verified, and what we don't promise — including exactly what is in this pack and how fast it arrives.
This pack is a dated factual record for you to attach to your own dispute. It makes no promise about whether your bank or card issuer will side with you, gives no legal advice, and does not name any registrar or hosting provider for this domain.
Not out of pocket — just checking a link? Read the full dated record for foursigtics.com, or check a different address free there.
What we documented at foursigtics.com
- The web address
foursigtics.com- The real brand it copies
- Four Sigmatic
- Evidence class
- Lookalike storefront — asset-level evidence
- Date we checked it
- 6 October 2026 — observed state: resolves but not serving — HTTP 522
- Date we last saw it serving
- 17 August 2026
This is our published record, quoted exactly as we published it. Nothing here was written for your dispute, and nothing was added to it:
- Four images on its homepage load from us.foursigmatic.com — the genuine Four Sigmatic store’s own domain. The page serves the genuine brand’s own hosted files, which is asset-level evidence.
- us.foursigmatic.com/cdn/shop/files/Group_46562_1.png?v=1757339492
- us.foursigmatic.com/cdn/shop/files/coffee-beans-background-free-png_c7f5d7fb-f33a-407e-ad68-1ba42cdb33ab.png?v=1743097849 — used twice on the page.
- us.foursigmatic.com/cdn/shop/files/816897020195_Think_Organic_Coffee_with_Lions_Mane_Chaga_Mushrooms_Ground_Render_Front_19a5977f-9ebc-464e-9631-1cb358aecb0f.png?v=1743097854
- The /cdn/shop/files/ path and the ?v= cache-busting stamps are a Shopify asset path, and the version stamps are the ones the genuine store generated.
- On the same page the product photographs load from foursigtics.com/wp-content/uploads/2026/02/… — the suspect’s own server. The four images pointing back at the real brand were decorative: background artwork in one marketing section.
- Its footer reads “Copyright © 2026 Four Sigmatic”.
- Discounts in the 65–70% band: ground coffee marked $20 down to $6, and protein marked $50 down to $15 — both exactly 70% off.
- A mushroom-coffee storefront carrying a slide for “JBuds Open Wireless Open-Ear Headphones” — a product the brand does not sell.
- The support address published on the page is support@ its own domain — writing to it reaches whoever runs the page, not the brand being copied.
We describe what each page serves; we make no assertion about any registrant’s intent or criminality, and nothing here is legal advice. The full record, including how this hostname was found and what it has in common with the other lookalikes we have documented, is on its own page.
Every time we checked foursigtics.com, and what we saw
We hold 7 dated readings of this address, the first published 17 August 2026 and the most recent 50 days later. Each one is printed below exactly as we recorded it on the day. A dispute team can weigh a record that was re-checked on named dates differently from a single screenshot, which is the only reason this list is here.
17 August 2026live, HTTP 200
On 17 August 2026 it resolved and returned HTTP 200 with cache bypassed — it was serving a live storefront when we looked.
Its build is WordPress and WooCommerce (WoodMart), distinct from the .shop Next.js clone kit, so the own-CDN artefact is not a quirk of one kit. The ten-second check is written up on /cdn-image-check. A domain’s state can change any day — re-check before relying on it.
HTTP 200
2 September 2026resolves but not serving — HTTP 403
On 2 September 2026 the observed state of foursigtics.com was “resolves but not serving — HTTP 403” — it still resolves, and it did not serve the storefront. It was last observed live, HTTP 200 on 17 August 2026.
A server answering 403 or 404 is not a takedown: enforcement means a registry status code (clientHold or serverHold) read back off the domain’s record, and we have read none for this hostname. We record only the state we observed, on the day we observed it. The findings below are the dated record from when it was serving, and they are unchanged. Confirmed twice, over two separate egress paths, so this is a state of the hostname rather than a state of our own connection.
HTTP 403
8 September 2026resolves but not serving — HTTP 403
On 8 September 2026 the observed state of foursigtics.com was “resolves but not serving — HTTP 403” — it still resolves, and it did not serve the storefront. Its observed state is unchanged from our 2 September 2026 check. It was last observed live, HTTP 200 on 17 August 2026.
A server answering 403 or 404 is not a takedown: enforcement means a registry status code (clientHold or serverHold) read back off the domain’s record, and we have read none for this hostname. We record only the state we observed, on the day we observed it. The findings below are the dated record from when it was serving, and they are unchanged. Unchanged from our previous check: it still resolves, and it still answered 403 rather than serving the storefront.
HTTP 403
15 September 2026resolves but not serving — HTTP 403
On 15 September 2026 the observed state of foursigtics.com was “resolves but not serving — HTTP 403” — it still resolves, and it did not serve the storefront. Its observed state is unchanged from our 8 September 2026 check. It was last observed live, HTTP 200 on 17 August 2026.
A server answering 403 or 404 is not a takedown: enforcement means a registry status code (clientHold or serverHold) read back off the domain’s record, and we have read none for this hostname. We record only the state we observed, on the day we observed it. The findings below are the dated record from when it was serving, and they are unchanged. Unchanged from our previous check: it still resolves, and it still answered 403 rather than serving the storefront.
HTTP 403
22 September 2026resolves but not serving — HTTP 403
On 22 September 2026 the observed state of foursigtics.com was “resolves but not serving — HTTP 403” — it still resolves, and it did not serve the storefront. Its observed state is unchanged from our 15 September 2026 check. It was last observed live, HTTP 200 on 17 August 2026.
A server answering 403 or 404 is not a takedown: enforcement means a registry status code (clientHold or serverHold) read back off the domain’s record, and we have read none for this hostname. We record only the state we observed, on the day we observed it. The findings below are the dated record from when it was serving, and they are unchanged. Unchanged for the fourth consecutive sweep: it still resolves, and it still answered 403 rather than serving the storefront.
HTTP 403
29 September 2026resolves but not serving — HTTP 403
On 29 September 2026 the observed state of foursigtics.com was “resolves but not serving — HTTP 403” — it still resolves, and it did not serve the storefront. Its observed state is unchanged from our 22 September 2026 check. It was last observed live, HTTP 200 on 17 August 2026.
A server answering 403 or 404 is not a takedown: enforcement means a registry status code (clientHold or serverHold) read back off the domain’s record, and we have read none for this hostname. We record only the state we observed, on the day we observed it. The findings below are the dated record from when it was serving, and they are unchanged. Unchanged for the fifth consecutive sweep: it still resolves, and it still answered 403 rather than serving the storefront.
HTTP 403
6 October 2026resolves but not serving — HTTP 522
On 6 October 2026 the observed state of foursigtics.com was “resolves but not serving — HTTP 522” — it still resolves, and it did not serve the storefront. It was last observed live, HTTP 200 on 17 August 2026.
A server answering 403 or 404 is not a takedown: enforcement means a registry status code (clientHold or serverHold) read back off the domain’s record, and we have read none for this hostname. We record only the state we observed, on the day we observed it. The findings below are the dated record from when it was serving, and they are unchanged. It still resolves, and it answered 522 rather than serving the storefront. Our previous completed reads of this hostname recorded an affirmative HTTP 403; those readings are unchanged and kept on the record with their own dates. The status it answers with has changed and nothing else has: this is not enforcement, there is no registry hold on this hostname and we have read none, and a hostname that resolves is not a hostname that left the zone.
HTTP 522
The check you can run on foursigtics.com yourself
Do this: Right-click an image on a suspected copy, choose “Copy image address,” and read the hostname. If it is the real brand’s own domain or CDN, the copy is not hosting that picture at all — it is loading it from the brand’s own server.
What we found running it: That is what we found here, on four homepage images. Check five or six, and include the decoration — backgrounds, the favicon, logos and press strips — not just the product photos.
It is here because nothing about a dispute should rest on taking our word for it — and because an address can change what it serves at any time, so a check you run yourself is dated to the day you run it, not to ours.
What to do about the money
The route itself — what to save, who to contact, what to ask them and in what order — is the same whichever address you paid, so it is written once on our dispute guide rather than repeated here. This page holds the part that is specific to this address: what we found at it, and when.
Read the bank dispute route, step by step — what to save, who to contact, what to ask — six steps, in plain language, with what we do not do stated on the same page. Everything on this page is a point-in-time record. We do not monitor this domain, we are not watching it for changes, and a website's status can change any day.
The part we can help with is the evidence. The Dispute Evidence Pack is $19, one-time, and turns the dated readings above into one document written to sit in front of a dispute team — with a real, redacted sample of the document for foursigtics.com beside the buy button at the top of this page, so you can read it before paying anything.
- Searches this page answers
- “foursigtics.com refund” · “how to get money back from foursigtics.com” · “foursigtics.com chargeback” · “foursigtics.com scam refund” · “Four Sigmatic fake site refund”
Paid a different store?
Every address we have documented and dated is listed in one place, each with its own evidence and the date we checked it: all 60 of them, on the dispute guide. A few others with records as detailed as this one:
See the same list grouped by the brand each one copies — 60 hostnames across 56 brands. If the address you paid is not on that list we hold no dated record for it, and we will not sell you evidence we do not have; you can still run a free check on it and take the result to your issuer yourself.
Scam Detective — pay-per-use scam intelligence. One-off checks, no subscription, no account.
This page is a factual record and a description of the ordinary dispute route, not legal advice and not a promise about any outcome. We do not recover funds, do not contact the site's operator on your behalf, and name no registrar or hosting provider here.
Every finding here is an assessment of publicly available information at the time of the check, and is not legal advice. We produce the evidence and the correctly addressed request; on a Takedown Engagement we submit it to the abuse desks as the customer’s authorized agent, which is an administrative act and not legal representation. We do not monitor continuously and never contact the registrant on a customer’s behalf, and no outcome or timeline is guaranteed. Confirm your own trademark position before sending anything adversarial. This hostname's status was captured on 6 October 2026 and may have changed since.
Questions about the pack? scam-detective8@mail.acoco.ai