19 of 60 documented lookalike hostnames did not resolve
Holding a link? Check it before you read on.
This page is a record of addresses we have already checked, which is not the same as an answer about yours. Paste the link you are worried about and our server reads it live: whether the name resolves, the certificate served on the connection, its public registration record, and the page itself fetched with caching switched off.
A 0–100 scam risk score, a plain-English verdict, from “no red flags found” to “high risk”, and the two most serious red flags — each naming what we read and the day we read it.
Or tap one of the 60 hostnames documented here and we read it live now, the same way — what it serves today, not what our record says it served.
Point-in-time check of public information. Not monitoring, not advice. A link that is not in our published record is unchecked, not clean — the record is what we have looked at, nothing more. Nothing runs until you press a button. Each check spends live reads, so we never start one for you on page load.
Run the same checks now — on a brand in this corpus, or on your own
Every hostname in the records below reproduces a real brand that did not ask for it. The same checks that produced this dataset run on demand: candidate lookalikes and typosquats generated from a domain, every one of them resolved, the ones that answer fetched live with cache bypassed, and each finding stamped with the date it was read — exactly as the rows below are. The free scan returns the count confirmed registered and resolving today, two of those rows in full, and the remainder withheld with their own dated states. One complete Brand Impersonation Audit is published in full so you can read the whole artefact before deciding.
One tap · run it live on a brand in this corpus
Each name below is a brand this corpus documents, paired with the domain that brand publishes as its own, read off a page that brand publishes itself on 21 August 2026. Tap one and the scan runs on it now, so you can check our method against a result you can verify yourself — every row it names is in the records further down this page. Or put your own company and domain in the fields and run it on yours.
How many lookalikes of your name are answering right now?
Free, no email and no card: we generate the lookalike and typosquat names for your domain, resolve them, fetch the ones that answer and grade them against your own page — then show you the counts, two of the rows in full, and the rest withheld. We generate the lookalike and typosquat names from your domain — different endings, hyphenated forms, single-character swaps and drops, and the shop / store / outlet / sale / official patterns our own documented corpus is full of. Only hostnames we confirm resolving are counted as resolving — a name nobody has registered is counted, never padded into a list.
No email, no card, no account. The sweep runs live and usually takes under a minute.
Know what you need already? The $29 report is right here. The $29 report names every hostname behind these counts, with the dated readings for each, the copying evidence where we found it, a risk rating derived in code, our own published record where we already hold one — and the takedown request drafted for you to send.
- Lookalike and typosquat candidates generated from your own domain — different endings, hyphenated forms, character swaps, drops and doublings, and the -shop/-outlet/-store/-sale/-official patterns our own documented corpus is full of
- Every candidate resolved, and everything that resolves fetched live with cache bypassed — only hostnames we confirm resolving are listed, so a name nobody registered is counted rather than padded into your report
- Per hostname: the date-stamped readings behind it — DNS, the HTTPS certificate served, the public registration record, and the page as served
- Per hostname: a risk rating derived in code from what was observed, and the copying evidence where we found it — your own hosted files being served, your image filenames, your catalogue handles or part numbers, or your title wording reproduced
- Where we already publish a dated record for a hostname, our own published finding, quoted verbatim
- A ready-to-send takedown request with your details in square brackets, plus the dated evidence index it refers to
- Delivered the moment the reads finish — the checks run live when you pay, so there is no research queue in front of it
What this is not: the Evidence Report is the researched tier — it adds the registrar and the true upstream host per domain, a filing drafted separately for every desk, and research beyond the patterns generated here. The audit is the deterministic sweep of your own name plus live reads, delivered without a research queue.
This is a point-in-time audit of publicly observable information, not legal advice and not monitoring. We assemble the evidence and draft the request; on this tier you send it. We do not file on your behalf, we do not contact the registrant, and no outcome or timeline is promised — that decision belongs to each registrar, host and platform.
Of 60 lookalike storefront hostnames documented since 27 July 2026 and re-checked on 6 October 2026, 19 had the observed state “does not resolve”. Reading the TLD registries’ own RDAP records for those 19 hostnames — on 22 September 2026, 29 September 2026 and 6 October 2026, each record travelling with the date it was read — every one carried “client hold” alongside the routine “client transfer prohibited” lock, and every registration was still intact: none deleted, none expired. In the 7 days between our 29 September 2026 and 6 October 2026 rounds, 1 moved from “resolves but not serving — HTTP 403” to “resolves but not serving — HTTP 522”, and 1 moved from “live, HTTP 200” to “does not resolve”. A further 8 hostnames we could not re-check at all on 6 October 2026, because our own fetch failed: brchhome.shop, ekstershop.com, featherstoneoutdoorhq.shop, luxebitesstore.shop, muhouse.shop, noguhq.shop, studioadornhq.shop and truetreasuresinchome.shop keep their earlier findings and their earlier dates. Neither a state nor a date moves on a check we did not complete. Every one of them resolves — the failure was on our own HTTP leg, so none of them is recorded as not resolving, and the kept reading is whatever we last actually read, which is not “live, HTTP 200” for all of them. Read those together rather than as one number: the count of hostnames observed “live, HTTP 200” fell by 4 on this round, and it fell for 2 different reasons — 1 of the 4 was an observation we completed, and 3 were hostnames we could not read. A hostname answering an HTTP error is not a hostname that left the zone, and a hostname we could not read is not an observation at all.
- Canonical URL
- https://scam-detective8.acoco.ai/lookalike-domain-dataset
- Round
- 6 October 2026 (2026-10-06)
- Rows
- 60 hostnames, one record each
- Licence
- Creative Commons Attribution 4.0 International (CC BY 4.0)
Quote it, chart it, re-publish the table, commercially or not: this dataset is published under the Creative Commons Attribution 4.0 International (CC BY 4.0). The one condition is attribution — name Scam Detective and link the canonical URL with a crawlable link — and carry the date of the round with any figure you take, because a state without its date is not a finding from this dataset.
Scam Detective (2026). Documented lookalike storefront hostnames — re-verification dataset, round of 6 October 2026. 60 hostnames, 364 dated observations. https://scam-detective8.acoco.ai/lookalike-domain-dataset
Data: <a href="https://scam-detective8.acoco.ai/lookalike-domain-dataset">Scam Detective lookalike storefront dataset</a>, round of 6 October 2026 (CC BY 4.0).
Attribution under this licence means two things together: a text credit naming Scam Detective, and a crawlable link to the canonical URL https://scam-detective8.acoco.ai/lookalike-domain-dataset. A link carrying rel="nofollow" or rel="sponsored" does not satisfy it.
The CSV is one row per hostname with the whole dated chain in a single column; the JSON carries the same rows with each observation as its own dated object, plus the licence, the citation and the method inline; the plain-text release carries the rows and all of the prose in one file. Same source, same counts, same state strings — all three are built from the rows this page renders.
Licence: Creative Commons Attribution 4.0 International (CC BY 4.0)
Licensed under the Creative Commons Attribution 4.0 International (CC BY 4.0): https://creativecommons.org/licenses/by/4.0/. You may copy, re-publish, chart and adapt this dataset, including commercially, under one condition — attribution. Attribution under this licence means two things together: a text credit naming Scam Detective, and a crawlable link to the canonical URL https://scam-detective8.acoco.ai/lookalike-domain-dataset. A link carrying rel="nofollow" or rel="sponsored" does not satisfy it. Carry the date of the round with any figure you take: a state without its date is not a finding from this dataset.
Nothing else is asked and nothing else is reserved. There is no separate permission to request, no embargo and no commercial carve-out: the licence text at https://creativecommons.org/licenses/by/4.0/ governs, and this page is the canonical source it points back to.
The licence covers this dataset — the rows, the dated observations and the registry readings as published. It does not transfer any right in the brands the hostnames reproduce, and it does not make a figure sayable without its date. Carry the date of the round with any figure you take: a state without its date is not a finding from this dataset.
Licence deed: https://creativecommons.org/licenses/by/4.0/ · SPDX identifier CC-BY-4.0 · the pasteable credit is in the citation block.
Stable metadata identifier (unique_metadata_identifier): b7f3c1d2-9e64-4a80-8f52-3c1a7d0e5b46 — it names this dataset's metadata record and does not change between rounds or re-publications.
What this is
This page is the whole record behind that sentence: every hostname we document, the brand it reproduces, the state we observed on each dated round, and — for the 19 that did not resolve — the TLD registry's own record as we read it, each one dated to the day it was read (22 September 2026, 29 September 2026 and 6 October 2026). It is free to read, free to quote and free to re-compute: the same rows are published as a CSV and as a plain-text release, and every hostname links to its own dated page so any cell here can be checked against the record it came from.
Read a figure as a reading, not a status. Everything here belongs to the date beside it, states change in both directions — one hostname in this corpus was observed not resolving on 31 July 2026 and serving again on 2 September 2026 — and we do not monitor anything continuously. If you need to know what an address is doing today, check it today.
Of the 60 hostnames on this index: 31 were live, HTTP 200 when we last checked them; 19 do not resolve; 2 resolve but do not serve; 8 we could not re-check, because our own check failed. A hostname's state can change on any day, in either direction — one row on this list was observed “does not resolve” on 31 July 2026 and “live, HTTP 200” again on 2 September 2026.
The 19 registry records, read 6 October 2026
clientTransferProhibited on its own is the routine lock carried by nearly every registered domain and shows nothing by itself. What we record here is the combination, read together: a hold on the registry record, no answer in the DNS on our own checks, and a registration that has neither expired nor been deleted — the name is still registered, it is simply not in the zone.
We hold no filing, no correspondence and no reference number for this domain. We do not know who asked for this, or why. A registrar or registry acting after we published is not a registrar or registry acting because we published, and we claim no part in it.
Each row below is one hostname whose observed state on 6 October 2026 was “does not resolve”, beside the TLD registry's own record for the same name as we read it that day. The state column in the main table does not change because of this reading, and the registry operator named is the source of the reading — not an attribution of anybody's provider.
| Hostname | Status codes on the record | Status set | Registered | Expires |
|---|---|---|---|---|
| theecobags.shop ECOBAGS The reading, in fullReading GMO Registry, the .shop registry’s own RDAP record for theecobags.shop on 22 September 2026, the record carried the status codes “client hold”, “client transfer prohibited” and “inactive”, last changed 14 August 2026 (2026-08-14T10:13:41Z). The registration itself is intact: created 21 May 2026, running to 21 May 2027, and not deleted. That is consistent with the “does not resolve” state we observed ourselves on 6 October 2026. clientTransferProhibited on its own is the routine lock carried by nearly every registered domain and shows nothing by itself. What we record here is the combination, read together: a hold on the registry record, no answer in the DNS on our own checks, and a registration that has neither expired nor been deleted — the name is still registered, it is simply not in the zone. We hold no filing, no correspondence and no reference number for this domain. We do not know who asked for this, or why. A registrar or registry acting after we published is not a registrar or registry acting because we published, and we claim no part in it. | client hold + client transfer prohibited + inactive | 14 August 2026 | 21 May 2026 | 21 May 2027 |
| johnderian.shop John Derian Company The reading, in fullReading GMO Registry, the .shop registry’s own RDAP record for johnderian.shop on 22 September 2026, the record carried the status codes “client hold”, “client transfer prohibited” and “inactive”, last changed 24 August 2026 (2026-08-24T07:07:15Z). The registration itself is intact: created 3 May 2026, running to 3 May 2027, and not deleted. That is consistent with the “does not resolve” state we observed ourselves on 6 October 2026. clientTransferProhibited on its own is the routine lock carried by nearly every registered domain and shows nothing by itself. What we record here is the combination, read together: a hold on the registry record, no answer in the DNS on our own checks, and a registration that has neither expired nor been deleted — the name is still registered, it is simply not in the zone. We hold no filing, no correspondence and no reference number for this domain. We do not know who asked for this, or why. A registrar or registry acting after we published is not a registrar or registry acting because we published, and we claim no part in it. | client hold + client transfer prohibited + inactive | 24 August 2026 | 3 May 2026 | 3 May 2027 |
| myredneckblinds.shop Redneck Blinds The reading, in fullReading GMO Registry, the .shop registry’s own RDAP record for myredneckblinds.shop on 22 September 2026, the record carried the status codes “client hold”, “client transfer prohibited” and “inactive”, last changed 28 August 2026 (2026-08-28T05:24:22Z). The registration itself is intact: created 26 May 2026, running to 26 May 2027, and not deleted. That is consistent with the “does not resolve” state we observed ourselves on 6 October 2026. clientTransferProhibited on its own is the routine lock carried by nearly every registered domain and shows nothing by itself. What we record here is the combination, read together: a hold on the registry record, no answer in the DNS on our own checks, and a registration that has neither expired nor been deleted — the name is still registered, it is simply not in the zone. We hold no filing, no correspondence and no reference number for this domain. We do not know who asked for this, or why. A registrar or registry acting after we published is not a registrar or registry acting because we published, and we claim no part in it. | client hold + client transfer prohibited + inactive | 28 August 2026 | 26 May 2026 | 26 May 2027 |
| epauletbrandstyle.shop Epaulet The reading, in fullReading GMO Registry, the .shop registry’s own RDAP record for epauletbrandstyle.shop on 22 September 2026, the record carried the status codes “client hold”, “client transfer prohibited” and “inactive”, last changed 28 August 2026 (2026-08-28T06:07:06Z). The registration itself is intact: created 4 May 2026, running to 4 May 2027, and not deleted. That is consistent with the “does not resolve” state we observed ourselves on 6 October 2026. clientTransferProhibited on its own is the routine lock carried by nearly every registered domain and shows nothing by itself. What we record here is the combination, read together: a hold on the registry record, no answer in the DNS on our own checks, and a registration that has neither expired nor been deleted — the name is still registered, it is simply not in the zone. We hold no filing, no correspondence and no reference number for this domain. We do not know who asked for this, or why. A registrar or registry acting after we published is not a registrar or registry acting because we published, and we claim no part in it. | client hold + client transfer prohibited + inactive | 28 August 2026 | 4 May 2026 | 4 May 2027 |
| tillmansmeatsonline.shop Tillman's Meats The reading, in fullReading GMO Registry, the .shop registry’s own RDAP record for tillmansmeatsonline.shop on 22 September 2026, the record carried the status codes “client hold”, “client transfer prohibited” and “inactive”, last changed 1 September 2026 (2026-09-01T07:57:19Z). The registration itself is intact: created 27 May 2026, running to 27 May 2027, and not deleted. That is consistent with the “does not resolve” state we observed ourselves on 6 October 2026. clientTransferProhibited on its own is the routine lock carried by nearly every registered domain and shows nothing by itself. What we record here is the combination, read together: a hold on the registry record, no answer in the DNS on our own checks, and a registration that has neither expired nor been deleted — the name is still registered, it is simply not in the zone. We hold no filing, no correspondence and no reference number for this domain. We do not know who asked for this, or why. A registrar or registry acting after we published is not a registrar or registry acting because we published, and we claim no part in it. | client hold + client transfer prohibited + inactive | 1 September 2026 | 27 May 2026 | 27 May 2027 |
| poshpeanut.shop Posh Peanut The reading, in fullReading GMO Registry, the .shop registry’s own RDAP record for poshpeanut.shop on 22 September 2026, the record carried the status codes “client hold”, “client transfer prohibited” and “inactive”, last changed 2 September 2026 (2026-09-02T09:21:02Z). The registration itself is intact: created 14 June 2026, running to 14 June 2027, and not deleted. That is consistent with the “does not resolve” state we observed ourselves on 6 October 2026. clientTransferProhibited on its own is the routine lock carried by nearly every registered domain and shows nothing by itself. What we record here is the combination, read together: a hold on the registry record, no answer in the DNS on our own checks, and a registration that has neither expired nor been deleted — the name is still registered, it is simply not in the zone. We hold no filing, no correspondence and no reference number for this domain. We do not know who asked for this, or why. A registrar or registry acting after we published is not a registrar or registry acting because we published, and we claim no part in it. | client hold + client transfer prohibited + inactive | 2 September 2026 | 14 June 2026 | 14 June 2027 |
| kytebaby.shop Kyte Baby The reading, in fullReading GMO Registry, the .shop registry’s own RDAP record for kytebaby.shop on 22 September 2026, the record carried the status codes “client hold”, “client transfer prohibited” and “inactive”, last changed 2 September 2026 (2026-09-02T23:19:24Z). The registration itself is intact: created 21 June 2026, running to 21 June 2027, and not deleted. That is consistent with the “does not resolve” state we observed ourselves on 6 October 2026. clientTransferProhibited on its own is the routine lock carried by nearly every registered domain and shows nothing by itself. What we record here is the combination, read together: a hold on the registry record, no answer in the DNS on our own checks, and a registration that has neither expired nor been deleted — the name is still registered, it is simply not in the zone. We hold no filing, no correspondence and no reference number for this domain. We do not know who asked for this, or why. A registrar or registry acting after we published is not a registrar or registry acting because we published, and we claim no part in it. | client hold + client transfer prohibited + inactive | 2 September 2026 | 21 June 2026 | 21 June 2027 |
| onceagaingoods.shop Once Again Nut Butter The reading, in fullReading GMO Registry, the .shop registry’s own RDAP record for onceagaingoods.shop on 22 September 2026, the record carried the status codes “client hold”, “client transfer prohibited” and “inactive”, last changed 7 September 2026 (2026-09-07T09:36:48Z). The registration itself is intact: created 4 May 2026, running to 4 May 2027, and not deleted. That is consistent with the “does not resolve” state we observed ourselves on 6 October 2026. clientTransferProhibited on its own is the routine lock carried by nearly every registered domain and shows nothing by itself. What we record here is the combination, read together: a hold on the registry record, no answer in the DNS on our own checks, and a registration that has neither expired nor been deleted — the name is still registered, it is simply not in the zone. We hold no filing, no correspondence and no reference number for this domain. We do not know who asked for this, or why. A registrar or registry acting after we published is not a registrar or registry acting because we published, and we claim no part in it. | client hold + client transfer prohibited + inactive | 7 September 2026 | 4 May 2026 | 4 May 2027 |
| wovenwoodhome.shop Woven Wood The reading, in fullReading GMO Registry, the .shop registry’s own RDAP record for wovenwoodhome.shop on 22 September 2026, the record carried the status codes “client hold”, “client transfer prohibited” and “inactive”, last changed 8 September 2026 (2026-09-08T21:17:05Z). The registration itself is intact: created 17 April 2026, running to 17 April 2027, and not deleted. That is consistent with the “does not resolve” state we observed ourselves on 6 October 2026. clientTransferProhibited on its own is the routine lock carried by nearly every registered domain and shows nothing by itself. What we record here is the combination, read together: a hold on the registry record, no answer in the DNS on our own checks, and a registration that has neither expired nor been deleted — the name is still registered, it is simply not in the zone. We hold no filing, no correspondence and no reference number for this domain. We do not know who asked for this, or why. A registrar or registry acting after we published is not a registrar or registry acting because we published, and we claim no part in it. | client hold + client transfer prohibited + inactive | 8 September 2026 | 17 April 2026 | 17 April 2027 |
| flamingoestate.shop Flamingo Estate The reading, in fullReading GMO Registry, the .shop registry’s own RDAP record for flamingoestate.shop on 22 September 2026, the record carried the status codes “client hold”, “client transfer prohibited” and “inactive”, last changed 10 September 2026 (2026-09-10T06:58:51Z). The registration itself is intact: created 28 April 2026, running to 28 April 2027, and not deleted. That is consistent with the “does not resolve” state we observed ourselves on 6 October 2026. clientTransferProhibited on its own is the routine lock carried by nearly every registered domain and shows nothing by itself. What we record here is the combination, read together: a hold on the registry record, no answer in the DNS on our own checks, and a registration that has neither expired nor been deleted — the name is still registered, it is simply not in the zone. We hold no filing, no correspondence and no reference number for this domain. We do not know who asked for this, or why. A registrar or registry acting after we published is not a registrar or registry acting because we published, and we claim no part in it. | client hold + client transfer prohibited + inactive | 10 September 2026 | 28 April 2026 | 28 April 2027 |
| repfitness.shop REP Fitness The reading, in fullReading GMO Registry, the .shop registry’s own RDAP record for repfitness.shop on 22 September 2026, the record carried the status codes “client hold”, “client transfer prohibited” and “inactive”, last changed 10 September 2026 (2026-09-10T08:33:59Z). The registration itself is intact: created 22 July 2026, running to 22 July 2027, and not deleted. That is consistent with the “does not resolve” state we observed ourselves on 6 October 2026. clientTransferProhibited on its own is the routine lock carried by nearly every registered domain and shows nothing by itself. What we record here is the combination, read together: a hold on the registry record, no answer in the DNS on our own checks, and a registration that has neither expired nor been deleted — the name is still registered, it is simply not in the zone. We hold no filing, no correspondence and no reference number for this domain. We do not know who asked for this, or why. A registrar or registry acting after we published is not a registrar or registry acting because we published, and we claim no part in it. | client hold + client transfer prohibited + inactive | 10 September 2026 | 22 July 2026 | 22 July 2027 |
| drinktrade.shop Trade Coffee The reading, in fullReading GMO Registry, the .shop registry’s own RDAP record for drinktrade.shop on 22 September 2026, the record carried the status codes “client hold”, “client transfer prohibited” and “inactive”, last changed 16 September 2026 (2026-09-16T08:22:39Z). The registration itself is intact: created 13 June 2026, running to 13 June 2027, and not deleted. That is consistent with the “does not resolve” state we observed ourselves on 6 October 2026. clientTransferProhibited on its own is the routine lock carried by nearly every registered domain and shows nothing by itself. What we record here is the combination, read together: a hold on the registry record, no answer in the DNS on our own checks, and a registration that has neither expired nor been deleted — the name is still registered, it is simply not in the zone. We hold no filing, no correspondence and no reference number for this domain. We do not know who asked for this, or why. A registrar or registry acting after we published is not a registrar or registry acting because we published, and we claim no part in it. | client hold + client transfer prohibited + inactive | 16 September 2026 | 13 June 2026 | 13 June 2027 |
| thewinfieldcollectionco.shop The Winfield Collection The reading, in fullReading GMO Registry, the .shop registry’s own RDAP record for thewinfieldcollectionco.shop on 22 September 2026, the record carried the status codes “client hold”, “client transfer prohibited” and “inactive”, last changed 17 September 2026 (2026-09-17T06:55:38Z). The registration itself is intact: created 12 May 2026, running to 12 May 2027, and not deleted. That is consistent with the “does not resolve” state we observed ourselves on 6 October 2026. clientTransferProhibited on its own is the routine lock carried by nearly every registered domain and shows nothing by itself. What we record here is the combination, read together: a hold on the registry record, no answer in the DNS on our own checks, and a registration that has neither expired nor been deleted — the name is still registered, it is simply not in the zone. We hold no filing, no correspondence and no reference number for this domain. We do not know who asked for this, or why. A registrar or registry acting after we published is not a registrar or registry acting because we published, and we claim no part in it. | client hold + client transfer prohibited + inactive | 17 September 2026 | 12 May 2026 | 12 May 2027 |
| officialnestbedding.shop Nest Bedding The reading, in fullReading GMO Registry, the .shop registry’s own RDAP record for officialnestbedding.shop on 22 September 2026, the record carried the status codes “client hold”, “client transfer prohibited” and “inactive”, last changed 18 September 2026 (2026-09-18T08:07:34Z). The registration itself is intact: created 25 April 2026, running to 25 April 2027, and not deleted. That is consistent with the “does not resolve” state we observed ourselves on 6 October 2026. clientTransferProhibited on its own is the routine lock carried by nearly every registered domain and shows nothing by itself. What we record here is the combination, read together: a hold on the registry record, no answer in the DNS on our own checks, and a registration that has neither expired nor been deleted — the name is still registered, it is simply not in the zone. We hold no filing, no correspondence and no reference number for this domain. We do not know who asked for this, or why. A registrar or registry acting after we published is not a registrar or registry acting because we published, and we claim no part in it. | client hold + client transfer prohibited + inactive | 18 September 2026 | 25 April 2026 | 25 April 2027 |
| shopkimirica.shop Kimirica The reading, in fullReading GMO Registry, the .shop registry’s own RDAP record for shopkimirica.shop on 22 September 2026, the record carried the status codes “client hold”, “client transfer prohibited” and “inactive”, last changed 18 September 2026 (2026-09-18T08:11:35Z). The registration itself is intact: created 21 April 2026, running to 21 April 2027, and not deleted. That is consistent with the “does not resolve” state we observed ourselves on 6 October 2026. clientTransferProhibited on its own is the routine lock carried by nearly every registered domain and shows nothing by itself. What we record here is the combination, read together: a hold on the registry record, no answer in the DNS on our own checks, and a registration that has neither expired nor been deleted — the name is still registered, it is simply not in the zone. We hold no filing, no correspondence and no reference number for this domain. We do not know who asked for this, or why. A registrar or registry acting after we published is not a registrar or registry acting because we published, and we claim no part in it. | client hold + client transfer prohibited + inactive | 18 September 2026 | 21 April 2026 | 21 April 2027 |
| jaxxonshop.com Jaxxon The reading, in fullReading Verisign, the .com registry’s own RDAP record for jaxxonshop.com on 22 September 2026, the record carried the status codes “client hold” and “client transfer prohibited”, last changed 18 September 2026 (2026-09-18T22:38:53Z). The registration itself is intact: created 9 August 2026, running to 9 August 2027, and not deleted. That is consistent with the “does not resolve” state we observed ourselves on 6 October 2026. clientTransferProhibited on its own is the routine lock carried by nearly every registered domain and shows nothing by itself. What we record here is the combination, read together: a hold on the registry record, no answer in the DNS on our own checks, and a registration that has neither expired nor been deleted — the name is still registered, it is simply not in the zone. We hold no filing, no correspondence and no reference number for this domain. We do not know who asked for this, or why. A registrar or registry acting after we published is not a registrar or registry acting because we published, and we claim no part in it. | client hold + client transfer prohibited | 18 September 2026 | 9 August 2026 | 9 August 2027 |
| saboskirt.shop SABO Skirt The reading, in fullReading GMO Registry, the .shop registry’s own RDAP record for saboskirt.shop on 22 September 2026, the record carried the status codes “client hold”, “client transfer prohibited” and “inactive”, last changed 21 September 2026 (2026-09-21T05:55:13Z). The registration itself is intact: created 20 June 2026, running to 20 June 2027, and not deleted. That is consistent with the “does not resolve” state we observed ourselves on 6 October 2026. clientTransferProhibited on its own is the routine lock carried by nearly every registered domain and shows nothing by itself. What we record here is the combination, read together: a hold on the registry record, no answer in the DNS on our own checks, and a registration that has neither expired nor been deleted — the name is still registered, it is simply not in the zone. We hold no filing, no correspondence and no reference number for this domain. We do not know who asked for this, or why. A registrar or registry acting after we published is not a registrar or registry acting because we published, and we claim no part in it. | client hold + client transfer prohibited + inactive | 21 September 2026 | 20 June 2026 | 20 June 2027 |
| shopparkseed.shop Park Seed The reading, in fullReading GMO Registry, the .shop registry’s own RDAP record for shopparkseed.shop on 29 September 2026, the record carried the status codes “client hold”, “client transfer prohibited” and “inactive”, last changed 24 September 2026 (2026-09-24T06:49:50Z). The registration itself is intact: created 4 June 2026, running to 4 June 2027, and not deleted. That is consistent with the “does not resolve” state we observed ourselves on 6 October 2026. clientTransferProhibited on its own is the routine lock carried by nearly every registered domain and shows nothing by itself. What we record here is the combination, read together: a hold on the registry record, no answer in the DNS on our own checks, and a registration that has neither expired nor been deleted — the name is still registered, it is simply not in the zone. We hold no filing, no correspondence and no reference number for this domain. We do not know who asked for this, or why. A registrar or registry acting after we published is not a registrar or registry acting because we published, and we claim no part in it. | client hold + client transfer prohibited + inactive | 24 September 2026 | 4 June 2026 | 4 June 2027 |
| shoplorenacanals.shop Lorena Canals The reading, in fullReading GMO Registry, the .shop registry’s own RDAP record for shoplorenacanals.shop on 6 October 2026, the record carried the status codes “client hold”, “client transfer prohibited” and “inactive”, last changed 30 September 2026 (2026-09-30T18:50:16Z). The registration itself is intact: created 15 May 2026, running to 15 May 2027, and not deleted. That is consistent with the “does not resolve” state we observed ourselves on 6 October 2026. clientTransferProhibited on its own is the routine lock carried by nearly every registered domain and shows nothing by itself. What we record here is the combination, read together: a hold on the registry record, no answer in the DNS on our own checks, and a registration that has neither expired nor been deleted — the name is still registered, it is simply not in the zone. We hold no filing, no correspondence and no reference number for this domain. We do not know who asked for this, or why. A registrar or registry acting after we published is not a registrar or registry acting because we published, and we claim no part in it. | client hold + client transfer prohibited + inactive | 30 September 2026 | 15 May 2026 | 15 May 2027 |
19 of 19 records carried a hold code. 0 had been deleted and 0 had expired: every registration was intact and running when we read it, which is the half of this finding most easily lost in a summary — the names are still registered, they are simply not in the zone.
2 rows changed state in 7 days
Between the round of 29 September 2026 and the round of 6 October 2026, these hostnames recorded a state different from the observation before them. Both ends are quoted off the record with their own dates. We did not observe why any of them changed, in either direction, and nothing below says otherwise.
| Hostname | Before | After | Gap |
|---|---|---|---|
| foursigtics.com Four Sigmatic | 29 September 2026 — resolves but not serving — HTTP 403 | 6 October 2026 — resolves but not serving — HTTP 522 | 7 days |
| shoplorenacanals.shop Lorena Canals | 29 September 2026 — live, HTTP 200 | 6 October 2026 — does not resolve | 7 days |
Method, as run on 6 October 2026
- (i) Candidate hostnames come from two pieces of published research of our own: the teardown of one .shop clone-kit storefront build, and the own-CDN asset check. Nothing enters the corpus without a dated page of its own.
- (ii) A live check is an HTTPS fetch with caching bypassed, and the HTTP status is recorded exactly as read.
- (iii) “does not resolve” is written only when two independent public resolvers both return NXDOMAIN carrying the registry's own SOA and no Answer section. One lookup is never a finding, and SERVFAIL, timeout or refused is our own failure, not an absent domain.
- (iv) Resolution state comes from an authoritative resolver, never from a page fetcher, in either direction.
- (v) Exactly three state strings may be emitted, and the set is closed: “live, HTTP 200”, “does not resolve”, “resolves but not serving — HTTP nnn”.
- (vi) A check date only advances on a completed observation. A failed fetch of ours freezes the row at its earlier finding and its earlier date, annotated with the day we tried.
- (vii) RDAP fields are recorded exactly as published — four fields only: the status codes on the record, the registration event, the expiration event, and the “last changed” event. Nothing is inferred and nothing is summarised upward.
- (viii) A registry status code is an additional dated observation and never replaces the state string.
We claim no part in anything on this page. We hold no filing, no correspondence and no reference number for any of these domains, we do not know who asked for any status to be set or why, and a registrar or registry acting after we published is not one acting because we published.
clientTransferProhibited on its own is the routine lock carried by nearly every registered domain and shows nothing at all. It is published here only because it was on the record and we publish the record as read.
The corpus: 60 hostnames across 56 brands, opened 27 July 2026
Every hostname here is one we checked ourselves and published a dated page for. The first group came out of our teardown of one .shop storefront kit on 27 July 2026; the rest were added on later dated rounds, each with the reading that put it in. An index is a record of what we have checked. It is not a census of what exists, and no count on this page should be read as one.
Rounds: 29 September 2026, then 6 October 2026, 7 days apart
Re-verification runs as dated rounds over the whole corpus, each applied on top of the last. A superseded observation is never overwritten or deleted: it stays on the row with its own date, which is what makes the decay history in the table below a record rather than a summary. The window from 27 July 2026 to 6 October 2026 is 71 days and holds 364 dated observations.
What counts as an observation, and the three strings it may produce
A live check is an HTTPS fetch with the cache bypassed, and the HTTP status is recorded as read. A hostname is only written down as “does not resolve” when two independent public resolvers both return no answer — one lookup is not a finding. Exactly three strings may describe what a hostname was doing: “live, HTTP 200”, “does not resolve”, and “resolves but not serving — HTTP nnn”. The same three strings are emitted by the live checker, printed on every hostname page, and used in the CSV, so an observation means the same thing everywhere it appears.
A check date only advances on a real observation
When our own fetch fails before it observes anything, we have learned nothing about the hostname — so the row keeps its earlier finding and its earlier date and is annotated as not re-checked, naming the day we tried. 8 rows are in that state on this round. A failed check of ours is a fact about our own egress and is reported as ours, never as a state of the hostname.
The registry status read-back, read 22 September 2026, 29 September 2026 and 6 October 2026
For each of the 19 hostnames that did not resolve, we queried the TLD registry's own RDAP service — GMO Registry for .shop, Verisign for .com — and recorded four fields exactly as published: the status codes on the record, the registration event, the expiration event, and the “last changed” event that dates the current status. Nothing is inferred and nothing is summarised upward. clientTransferProhibited on its own is the routine lock carried by nearly every registered domain and shows nothing by itself. What we record here is the combination, read together: a hold on the registry record, no answer in the DNS on our own checks, and a registration that has neither expired nor been deleted — the name is still registered, it is simply not in the zone.
It is an additional observation, never a state
A status code read off a registry record and a DNS answer read off a resolver are two different readings of two different systems, taken on their own dates. So the state column stays exactly “does not resolve” for all 19 of these rows, the registry reading sits beside it in its own columns, and the vocabulary does not gain a fourth member. We hold no filing, no correspondence and no reference number for this domain. We do not know who asked for this, or why. A registrar or registry acting after we published is not a registrar or registry acting because we published, and we claim no part in it.
What we withhold from this page, deliberately
The records we read name a registrar, and our own checks see hosting and network detail. None of it appears here, in the CSV, or anywhere else we publish for free — that attribution belongs in a paid report where the person acting on it is identified, not on an open page about named third parties. The registry operator is named because it is the source of the reading, not an attribution of anyone's provider.
What this dataset does not say
- A registry status code is not a state, and we never print one as one. Every row that carries a read-back still reads “does not resolve” in the state column, dated to the DNS check that produced it.
- We claim no part in anything on this page. We hold no filing, no correspondence and no reference number for any of these domains, we do not know who asked for any status to be set or why, and a registrar or registry acting after we published is not one acting because we published.
- clientTransferProhibited on its own is the routine lock carried by nearly every registered domain and shows nothing at all. It is published here only because it was on the record and we publish the record as read.
- No personal data. Hostnames and observed states only; no registrant, registrar, host or IP data is published.
- We did not observe why any hostname stopped resolving, and we do not describe any of them as removed, suspended, seized or taken down. A name that is not in the zone today can be back in it tomorrow — one row in this corpus has already done exactly that.
- Nothing here is a claim about what any address is doing right now. Every figure belongs to the date printed beside it, and the round it came from is named.
- We describe what each page served on the day we read it. We assert nothing about any registrant's identity, intent or criminality, and nothing here is legal advice.
- This is not monitoring and not a feed. It is a set of dated readings taken by hand on named days, and there is no promise that the next round will happen on any particular day.
- An index is a record of what we have checked. It is not a list of every lookalike hostname that exists for these brands, and the counts must not be read as a measure of how many there are.
We describe what each page serves; we make no assertion about any registrant’s intent or criminality, and nothing here is legal advice. Every finding on this page is an assessment of publicly available information at the time of the check, taken on the dates named, and is not legal advice. We do not monitor domains continuously, we never contact a registrant on anyone's behalf, and we promise no outcome of any kind.
The records — 60 hostnames, 364 dated observations
One row per documented hostname, A→Z. State is the most recent real observation and the day it was taken; decay history is every dated observation on that row, oldest first, including the ones the later rounds superseded. Nothing is deleted from a row, and nothing is written into it that was not read. Each hostname links to its own dated page.
| Hostname / brand reproduced | State at last check | Decay history | Registry record |
|---|---|---|---|
| aersfshop.com Aer · first documented 13 August 2026 | live, HTTP 200 checked 6 October 2026 | 2026-08-13 live, HTTP 2002026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 live, HTTP 2002026-10-06 live, HTTP 200 last observed serving 6 October 2026 | — |
| brchhome.shop Branch Furniture · first documented 27 July 2026 | live, HTTP 200 checked 29 September 2026 · not re-checked — our own check failed on 6 October 2026 | 2026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 live, HTTP 200 last observed serving 29 September 2026 | — |
| bronzeartist.shop COPPERTIST.WU · first documented 27 July 2026 | live, HTTP 200 checked 6 October 2026 | 2026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 live, HTTP 2002026-10-06 live, HTTP 200 last observed serving 6 October 2026 | — |
| carrollsirishhome.shop Carrolls Irish Gifts · first documented 27 July 2026 | live, HTTP 200 checked 6 October 2026 | 2026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 live, HTTP 2002026-10-06 live, HTTP 200 last observed serving 6 October 2026 | — |
| chamberlaincoffeeshop.com Chamberlain Coffee · first documented 13 August 2026 | live, HTTP 200 checked 6 October 2026 | 2026-08-13 live, HTTP 2002026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 live, HTTP 2002026-10-06 live, HTTP 200 last observed serving 6 October 2026 | — |
| coyuchi.shop Coyuchi · first documented 13 August 2026 | live, HTTP 200 checked 6 October 2026 | 2026-08-13 live, HTTP 2002026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 live, HTTP 2002026-10-06 live, HTTP 200 last observed serving 6 October 2026 | — |
| diggs.live Diggs · first documented 13 August 2026 | resolves but not serving — HTTP 404 checked 6 October 2026 | 2026-08-13 live, HTTP 2002026-09-02 resolves but not serving — HTTP 4042026-09-08 resolves but not serving — HTTP 4042026-09-15 resolves but not serving — HTTP 4042026-09-22 resolves but not serving — HTTP 4042026-09-29 resolves but not serving — HTTP 4042026-10-06 resolves but not serving — HTTP 404 last observed serving 13 August 2026 · 1 state change | — |
| drinktrade.shop Trade Coffee · first documented 13 August 2026 | does not resolve checked 6 October 2026 | 2026-08-13 live, HTTP 2002026-09-02 live, HTTP 2002026-09-08 does not resolve2026-09-15 does not resolve2026-09-22 does not resolve2026-09-29 does not resolve2026-10-06 does not resolve last observed serving 2 September 2026 · 1 state change | Registry record read back — 22 September 2026 client hold + client transfer prohibited + inactive |
| ecobagsfashion.shop ECOBAGS · first documented 27 July 2026 | live, HTTP 200 checked 6 October 2026 | 2026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 live, HTTP 2002026-10-06 live, HTTP 200 last observed serving 6 October 2026 | — |
| ekstershop.com Ekster · first documented 13 August 2026 | live, HTTP 200 checked 13 August 2026 · not re-checked — our own check failed on 6 October 2026 | 2026-08-13 live, HTTP 200 last observed serving 13 August 2026 | — |
| epauletbrandstyle.shop Epaulet · first documented 27 July 2026 | does not resolve checked 6 October 2026 | 2026-09-02 does not resolve2026-09-08 does not resolve2026-09-15 does not resolve2026-09-22 does not resolve2026-09-29 does not resolve2026-10-06 does not resolve last observed serving 27 July 2026 | Registry record read back — 22 September 2026 client hold + client transfer prohibited + inactive |
| exultplanetstore.shop Exult Planet · first documented 27 July 2026 | live, HTTP 200 checked 6 October 2026 | 2026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 live, HTTP 2002026-10-06 live, HTTP 200 last observed serving 6 October 2026 | — |
| featherstoneoutdoorgear.shop Featherstone Outdoor · first documented 27 July 2026 | live, HTTP 200 checked 6 October 2026 | 2026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 live, HTTP 2002026-10-06 live, HTTP 200 last observed serving 6 October 2026 | — |
| featherstoneoutdoorhq.shop Featherstone Outdoor · first documented 27 July 2026 | live, HTTP 200 checked 29 September 2026 · not re-checked — our own check failed on 6 October 2026 | 2026-09-02 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 live, HTTP 200 last observed serving 29 September 2026 | — |
| flamingoestate.shop Flamingo Estate · first documented 13 August 2026 | does not resolve checked 6 October 2026 | 2026-08-13 live, HTTP 2002026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 does not resolve2026-09-22 does not resolve2026-09-29 does not resolve2026-10-06 does not resolve last observed serving 8 September 2026 · 1 state change | Registry record read back — 22 September 2026 client hold + client transfer prohibited + inactive |
| foursigtics.com Four Sigmatic · first documented 17 August 2026 | resolves but not serving — HTTP 522 checked 6 October 2026 | 2026-08-17 live, HTTP 2002026-09-02 resolves but not serving — HTTP 4032026-09-08 resolves but not serving — HTTP 4032026-09-15 resolves but not serving — HTTP 4032026-09-22 resolves but not serving — HTTP 4032026-09-29 resolves but not serving — HTTP 4032026-10-06 resolves but not serving — HTTP 522 last observed serving 17 August 2026 · 2 state changes | — |
| glowrecipeshop.com Glow Recipe · first documented 13 August 2026 | live, HTTP 200 checked 6 October 2026 | 2026-08-13 live, HTTP 2002026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 live, HTTP 2002026-10-06 live, HTTP 200 last observed serving 6 October 2026 | — |
| highcountrygardensco.shop High Country Gardens · first documented 27 July 2026 | live, HTTP 200 checked 6 October 2026 | 2026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 live, HTTP 2002026-10-06 live, HTTP 200 last observed serving 6 October 2026 | — |
| jaxxonshop.com Jaxxon · first documented 13 August 2026 | does not resolve checked 6 October 2026 | 2026-08-13 live, HTTP 2002026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 does not resolve2026-09-29 does not resolve2026-10-06 does not resolve last observed serving 15 September 2026 · 1 state change | Registry record read back — 22 September 2026 client hold + client transfer prohibited |
| johnderian.shop John Derian Company · first documented 27 July 2026 | does not resolve checked 6 October 2026 | 2026-09-02 does not resolve2026-09-08 does not resolve2026-09-15 does not resolve2026-09-22 does not resolve2026-09-29 does not resolve2026-10-06 does not resolve last observed serving 27 July 2026 | Registry record read back — 22 September 2026 client hold + client transfer prohibited + inactive |
| keywaydesigns.shop Keyway Designs · first documented 27 July 2026 | live, HTTP 200 checked 6 October 2026 | 2026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 live, HTTP 2002026-10-06 live, HTTP 200 last observed serving 6 October 2026 | — |
| kytebaby.shop Kyte Baby · first documented 13 August 2026 | does not resolve checked 6 October 2026 | 2026-08-13 live, HTTP 2002026-09-02 live, HTTP 2002026-09-08 does not resolve2026-09-15 does not resolve2026-09-22 does not resolve2026-09-29 does not resolve2026-10-06 does not resolve last observed serving 2 September 2026 · 1 state change | Registry record read back — 22 September 2026 client hold + client transfer prohibited + inactive |
| kytebabyshop.com Kyte Baby · first documented 13 August 2026 | live, HTTP 200 checked 6 October 2026 | 2026-08-13 live, HTTP 2002026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 live, HTTP 2002026-10-06 live, HTTP 200 last observed serving 6 October 2026 | — |
| littlesleepies.xyz Little Sleepies · first documented 13 August 2026 | live, HTTP 200 checked 6 October 2026 | 2026-08-13 live, HTTP 2002026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 live, HTTP 2002026-10-06 live, HTTP 200 last observed serving 6 October 2026 | — |
| luxebitesstore.shop Luxe Bites · first documented 27 July 2026 | resolves but not serving — HTTP 502 checked 29 September 2026 · not re-checked — our own check failed on 6 October 2026 | 2026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 resolves but not serving — HTTP 502 last observed serving 22 September 2026 · 1 state change | — |
| michaelangeloskitchen.shop Michael Angelo's · first documented 27 July 2026 | live, HTTP 200 checked 6 October 2026 | 2026-09-02 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 live, HTTP 2002026-10-06 live, HTTP 200 last observed serving 6 October 2026 | — |
| microkickboardglobal.shop Micro Kickboard · first documented 27 July 2026 | live, HTTP 200 checked 6 October 2026 | 2026-09-02 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 live, HTTP 2002026-10-06 live, HTTP 200 last observed serving 6 October 2026 | — |
| moxievinyls.shop Moxie Vinyls · first documented 27 July 2026 | live, HTTP 200 checked 6 October 2026 | 2026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 live, HTTP 2002026-10-06 live, HTTP 200 last observed serving 6 October 2026 | — |
| muhouse.shop MUSASHI · first documented 27 July 2026 | live, HTTP 200 checked 29 September 2026 · not re-checked — our own check failed on 6 October 2026 | 2026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 live, HTTP 200 last observed serving 29 September 2026 | — |
| myfashionbrandcompany.shop Fashion Brand Company · first documented 27 July 2026 | live, HTTP 200 checked 6 October 2026 | 2026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 live, HTTP 2002026-10-06 live, HTTP 200 last observed serving 6 October 2026 | — |
| myredneckblinds.shop Redneck Blinds · first documented 27 July 2026 | does not resolve checked 6 October 2026 | 2026-09-02 does not resolve2026-09-08 does not resolve2026-09-15 does not resolve2026-09-22 does not resolve2026-09-29 does not resolve2026-10-06 does not resolve last observed serving 27 July 2026 | Registry record read back — 22 September 2026 client hold + client transfer prohibited + inactive |
| naturium.us Naturium · first documented 13 August 2026 | live, HTTP 200 checked 6 October 2026 | 2026-08-13 live, HTTP 2002026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 live, HTTP 2002026-10-06 live, HTTP 200 last observed serving 6 October 2026 | — |
| noguhq.shop NOGU · first documented 27 July 2026 | live, HTTP 200 checked 22 September 2026 · not re-checked — our own check failed on 6 October 2026 | 2026-07-31 does not resolve2026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 200 last observed serving 22 September 2026 · 1 state change | — |
| nomatic.shop Nomatic · first documented 13 August 2026 | live, HTTP 200 checked 6 October 2026 | 2026-08-13 live, HTTP 2002026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 live, HTTP 2002026-10-06 live, HTTP 200 last observed serving 6 October 2026 | — |
| nomaticstore.com Nomatic · first documented 13 August 2026 | live, HTTP 200 checked 6 October 2026 | 2026-08-13 live, HTTP 2002026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 live, HTTP 2002026-10-06 live, HTTP 200 last observed serving 6 October 2026 | — |
| officialnestbedding.shop Nest Bedding · first documented 27 July 2026 | does not resolve checked 6 October 2026 | 2026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 does not resolve2026-09-29 does not resolve2026-10-06 does not resolve last observed serving 15 September 2026 · 1 state change | Registry record read back — 22 September 2026 client hold + client transfer prohibited + inactive |
| onceagaingoods.shop Once Again Nut Butter · first documented 27 July 2026 | does not resolve checked 6 October 2026 | 2026-09-02 live, HTTP 2002026-09-08 does not resolve2026-09-15 does not resolve2026-09-22 does not resolve2026-09-29 does not resolve2026-10-06 does not resolve last observed serving 2 September 2026 · 1 state change | Registry record read back — 22 September 2026 client hold + client transfer prohibited + inactive |
| philipparoberts.shop Philippa Roberts Jewelry · first documented 27 July 2026 | live, HTTP 200 checked 6 October 2026 | 2026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 live, HTTP 2002026-10-06 live, HTTP 200 last observed serving 6 October 2026 | — |
| poshpeanut.shop Posh Peanut · first documented 13 August 2026 | does not resolve checked 6 October 2026 | 2026-08-13 live, HTTP 2002026-09-02 live, HTTP 2002026-09-08 does not resolve2026-09-15 does not resolve2026-09-22 does not resolve2026-09-29 does not resolve2026-10-06 does not resolve last observed serving 2 September 2026 · 1 state change | Registry record read back — 22 September 2026 client hold + client transfer prohibited + inactive |
| repfitness.shop REP Fitness · first documented 13 August 2026 | does not resolve checked 6 October 2026 | 2026-08-13 live, HTTP 2002026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 does not resolve2026-09-22 does not resolve2026-09-29 does not resolve2026-10-06 does not resolve last observed serving 8 September 2026 · 1 state change | Registry record read back — 22 September 2026 client hold + client transfer prohibited + inactive |
| saboskirt.shop SABO Skirt · first documented 27 July 2026 | does not resolve checked 6 October 2026 | 2026-08-04 live, HTTP 2002026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 does not resolve2026-09-29 does not resolve2026-10-06 does not resolve last observed serving 15 September 2026 · 1 state change | Registry record read back — 22 September 2026 client hold + client transfer prohibited + inactive |
| seamatetech.shop SeaMATE · first documented 27 July 2026 | live, HTTP 200 checked 6 October 2026 | 2026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 live, HTTP 2002026-10-06 live, HTTP 200 last observed serving 6 October 2026 | — |
| secondnaturebrandshq.shop Second Nature Brands · first documented 27 July 2026 | live, HTTP 200 checked 6 October 2026 | 2026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 live, HTTP 2002026-10-06 live, HTTP 200 last observed serving 6 October 2026 | — |
| shopelitesports.shop Elite Sports · first documented 27 July 2026 | live, HTTP 200 checked 6 October 2026 | 2026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 live, HTTP 2002026-10-06 live, HTTP 200 last observed serving 6 October 2026 | — |
| shopkimirica.shop Kimirica · first documented 27 July 2026 | does not resolve checked 6 October 2026 | 2026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 does not resolve2026-09-29 does not resolve2026-10-06 does not resolve last observed serving 15 September 2026 · 1 state change | Registry record read back — 22 September 2026 client hold + client transfer prohibited + inactive |
| shoplorenacanals.shop Lorena Canals · first documented 27 July 2026 | does not resolve checked 6 October 2026 | 2026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 live, HTTP 2002026-10-06 does not resolve last observed serving 29 September 2026 · 1 state change | Registry record read back — 6 October 2026 client hold + client transfer prohibited + inactive |
| shopparkseed.shop Park Seed · first documented 27 July 2026 | does not resolve checked 6 October 2026 | 2026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 does not resolve2026-10-06 does not resolve last observed serving 22 September 2026 · 1 state change | Registry record read back — 29 September 2026 client hold + client transfer prohibited + inactive |
| shopriverbendhome.shop Riverbend Home · first documented 27 July 2026 | live, HTTP 200 checked 6 October 2026 | 2026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 live, HTTP 2002026-10-06 live, HTTP 200 last observed serving 6 October 2026 | — |
| stixyarnstudio.shop Stix Yarn · first documented 27 July 2026 | live, HTTP 200 checked 6 October 2026 | 2026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 live, HTTP 2002026-10-06 live, HTTP 200 last observed serving 6 October 2026 | — |
| studioadornhq.shop Studio Adorn · first documented 27 July 2026 | resolves but not serving — HTTP 502 checked 29 September 2026 · not re-checked — our own check failed on 6 October 2026 | 2026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 resolves but not serving — HTTP 502 last observed serving 22 September 2026 · 1 state change | — |
| teamsportsamericastore.shop Team Sports America · first documented 27 July 2026 | live, HTTP 200 checked 6 October 2026 | 2026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 live, HTTP 2002026-10-06 live, HTTP 200 last observed serving 6 October 2026 | — |
| theappointed.shop Appointed · first documented 27 July 2026 | live, HTTP 200 checked 6 October 2026 | 2026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 live, HTTP 2002026-10-06 live, HTTP 200 last observed serving 6 October 2026 | — |
| theecobags.shop ECOBAGS · first documented 27 July 2026 | does not resolve checked 6 October 2026 | 2026-09-02 does not resolve2026-09-08 does not resolve2026-09-15 does not resolve2026-09-22 does not resolve2026-09-29 does not resolve2026-10-06 does not resolve last observed serving 27 July 2026 | Registry record read back — 22 September 2026 client hold + client transfer prohibited + inactive |
| themissamara.shop Miss Amara · first documented 27 July 2026 | live, HTTP 200 checked 6 October 2026 | 2026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 live, HTTP 2002026-10-06 live, HTTP 200 last observed serving 6 October 2026 | — |
| thewinfieldcollectionco.shop The Winfield Collection · first documented 27 July 2026 | does not resolve checked 6 October 2026 | 2026-08-04 live, HTTP 2002026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 does not resolve2026-09-29 does not resolve2026-10-06 does not resolve last observed serving 15 September 2026 · 1 state change | Registry record read back — 22 September 2026 client hold + client transfer prohibited + inactive |
| tillmansmeatsonline.shop Tillman's Meats · first documented 27 July 2026 | does not resolve checked 6 October 2026 | 2026-09-02 does not resolve2026-09-08 does not resolve2026-09-15 does not resolve2026-09-22 does not resolve2026-09-29 does not resolve2026-10-06 does not resolve last observed serving 27 July 2026 | Registry record read back — 22 September 2026 client hold + client transfer prohibited + inactive |
| toirocollection.shop TOIRO · first documented 27 July 2026 | live, HTTP 200 checked 6 October 2026 | 2026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 live, HTTP 2002026-10-06 live, HTTP 200 last observed serving 6 October 2026 | — |
| truetreasuresinchome.shop True Treasures Inc · first documented 27 July 2026 | resolves but not serving — HTTP 502 checked 29 September 2026 · not re-checked — our own check failed on 6 October 2026 | 2026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 resolves but not serving — HTTP 502 last observed serving 22 September 2026 · 1 state change | — |
| wovenwoodhome.shop Woven Wood · first documented 27 July 2026 | does not resolve checked 6 October 2026 | 2026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 does not resolve2026-09-22 does not resolve2026-09-29 does not resolve2026-10-06 does not resolve last observed serving 8 September 2026 · 1 state change | Registry record read back — 22 September 2026 client hold + client transfer prohibited + inactive |
| yearlycojewelry.shop Yearly Co. · first documented 27 July 2026 | live, HTTP 200 checked 6 October 2026 | 2026-09-02 live, HTTP 2002026-09-08 live, HTTP 2002026-09-15 live, HTTP 2002026-09-22 live, HTTP 2002026-09-29 live, HTTP 2002026-10-06 live, HTTP 200 last observed serving 6 October 2026 | — |
Of the 60 hostnames on this index: 31 were live, HTTP 200 when we last checked them; 19 do not resolve; 2 resolve but do not serve; 8 we could not re-check, because our own check failed. A hostname's state can change on any day, in either direction — one row on this list was observed “does not resolve” on 31 July 2026 and “live, HTTP 200” again on 2 September 2026.
Re-run it yourself
Both readings behind every row come from public sources, so you do not have to take ours on trust. Substitute any hostname from the table. Your result will differ from ours wherever a state has changed since 6 October 2026 — that is a finding of yours, with your own date on it.
1. Ask the DNS, twice, from resolvers we do not run
dig +short <hostname> A curl -s 'https://dns.google/resolve?name=<hostname>&type=A'
Two independent answers, both empty, is what this dataset records as “does not resolve”. One empty answer is not a finding, and a resolver that is simply unreachable from where you are is a fact about your network, not about the hostname.
2. Fetch it with the cache bypassed
curl -sS -o /dev/null -w '%{http_code}\n' -H 'Cache-Control: no-cache' https://<hostname>/A 200 is “live, HTTP 200”. A 403 or a 404 is “resolves but not serving — HTTP nnn”, which is an observation about a server and nothing more. A fetch that fails at your own egress tells you about your egress: record it as that, or record nothing.
3. Read the registry's own record over RDAP
curl -s -H 'accept: application/rdap+json' https://rdap.gmoregistry.net/rdap/domain/<name>.shop curl -s -H 'accept: application/rdap+json' https://rdap.verisign.com/com/v1/domain/<name>.com
The four fields this dataset publishes are the record's own: `status`, and the `registration`, `expiration` and `last changed` entries in `events`. RDAP is a public protocol and these are the registries' own endpoints, so a third party gets the same bytes we did. Timestamps will have moved on since our round — that is the point of dating a reading.
Run the same checks on your own name
The free scan at the top of this page runs the method above on any brand in this corpus, or on your own company and domain: start the free lookalike scan — candidates generated from the domain, every one resolved, the ones that answer fetched live, each finding stamped with the date it was read. One complete Brand Impersonation Audit is published in full so you can read the whole artefact before deciding.
Questions a citing reader asks first
Does “client hold” mean these 19 storefronts were taken down?
We do not say that and this dataset cannot support it. What we published is what we read: on 22 September 2026, 29 September 2026 and 6 October 2026 each of those 19 records carried a hold code, none of the registrations had expired and none was deleted, and our own DNS checks returned no answer, which is recorded as “does not resolve”. We did not observe who set anything, or why. We hold no filing, no correspondence and no reference number for this domain. We do not know who asked for this, or why. A registrar or registry acting after we published is not a registrar or registry acting because we published, and we claim no part in it.
Did your reports cause this?
No, and we would not know if they had. We hold no filing, no correspondence and no reference number for any of these domains. The honest reading is that we published a dated index and later read a dated registry record, and that is all the record supports — an ordering in time is not a causal chain.
Why is a hostname still listed after it stopped resolving?
Because a dated observation stays true. The page for a hostname that has gone quiet is the record of what it served on the day we read it, and that is the thing a brand owner or a shopper needs later. States also move in both directions: one row here was observed not resolving on 31 July 2026 and serving the same storefront build again on 2 September 2026, which is exactly why nothing is closed off or taken out of the index.
Can I re-run your checks?
Yes, and that is the point of publishing the method and the files. Every reading in this dataset comes from two public sources — the DNS, and the TLD registries' own RDAP records — and the commands are on this page. Your numbers will differ from ours where a state has changed since 6 October 2026; that is a finding of yours with your own date on it, not a contradiction of ours.
Why is there no registrar, host or IP in the data?
Because this is a free, public page about named third parties, and that attribution is the part most easily acted on by someone who has not verified anything. It is withheld from every free surface we publish. It exists in the paid report, where the person receiving it is identified.
The rest of the record
- The documented index — the same 60 hostnames grouped by the brand they reproduce, each with its own page and its own dated evidence.
- The decay study — these rows counted across the whole window: every state change, its direction and the gap between the two checks.
- Who we are and how we check — the verification steps behind every reading, and what we refuse to assert.
- Corrections, questions, or a record you can show is wrong: scam-detective8@mail.acoco.ai. We date and publish corrections rather than editing a finding quietly.