Jaxxon lookalike storefronts: the dated record
We hold 1 documented hostname reproducing Jaxxon, first documented 13 August 2026 and carried through every re-verification round since, most recently on 27 October 2026. At each row's own last completed check: 1 was “does not resolve”. Every superseded observation is kept below the current one, with its own date. This is one brand's slice of a corpus of 61 hostnames across 57 brands — a record of what we have checked, never a claim that nothing else exists.
Is your brand in this corpus? Check the name.
This research is free. 61 documented lookalike storefront hostnames across 57 brands, carrying 653 dated observations between them, all re-checked in our re-verification round of 27 October 2026. Type a brand name or a domain below: if we have documented it, that brand's own rows and every dated reading on them come back here, and you can act on them. If we have not, the free pass on your own domain is one click away.
A brand name (“Kyte Baby”), your own domain, or a lookalike hostname you were sent — any of the three resolves to the brand it reproduces.
Jaxxon — 1 documented hostname, with every dated observation
12 dated observations on this brand’s rows, the earliest documented 13 August 2026, the most recent completed reading 27 October 2026. Of that hostname: 0 live, HTTP 200 at their last check; 1 do not resolve; 0 resolve but did not serve the page; 0 we could not re-check, because our own check failed.
Every row below is already published free on its own page, and each one links to it. The state is the most recent completed observation and the day it was taken; the chain under it is every dated reading on that row, oldest first, including the ones later rounds superseded. Nothing here says what any hostname is serving today.
The whole free record for Jaxxon — the registry read-backs we hold, the rows that changed on the most recent round, and the method — is on its own page. The full record for Jaxxon→
Run the same checks on a domain you own
The rows above are what we have already published. The actions below run the same checks on a domain YOU own — never on a hostname from this corpus, and never on a domain we guessed for you.
Pre-filled with jaxxon.com — the domain Jaxxon publishes as its own, read off a page it publishes itself on 21 August 2026. Change it if the domain you want audited is a different one.
Same engine, same method, same claims — run deeper. The Brand Impersonation Audit documents up to 15 confirmed hostnames and reports the rest of what resolved as a count; the Documented Evidence Dossier documents up to 30 of them row by row, from a candidate list of up to 320 names rather than 180. Nothing is added to a row and no caveat is softened. If a capped pass over your own domain answers your question, buy the $29 audit instead — this tier is for a file complete enough to hand to someone else.
The card form opens on this page, and nothing is charged until you complete it. Both are single charges — no account, no subscription, nothing kept on file. See a real report before you buy — one complete Brand Impersonation Audit, published in full.
This is not a different or deeper method. One domain is the $29 Brand Impersonation Audit and you should buy that instead; the $249 buys the same audit across a portfolio in one checkout and one combined dated report.
No card? Buy it on an invoice instead
Request an invoice for the Documented Evidence Dossier — $149
Most brand-protection, trademark and legal teams cannot put a company card through a supplier's web form — spend leaves as an invoice, often against a purchase order. If that is you, ask for one here instead.
Tell us who to invoice and which domains the audit covers. We email you a confirmation immediately and send the invoice to the same address. The report is produced once the invoice is paid.
Free, and staying free
- Every row of this corpus is published under CC BY 4.0 — all 61 hostnames across 57 brands, with all 653 dated observations, including every superseded reading.
- You may copy, re-publish, chart and adapt it, including commercially. Attribution is the single condition, and it is defined rather than implied.
- The same records are downloadable as a CSV, a JSON release and a plain-text release from /lookalike-domain-dataset, plus one free page per hostname and one per brand. Nothing is held back from them.
- No email, no account and no card is needed for any of that, and none of it expires.
CSV · JSON · Plain text · the records themselves
Licensed under the Creative Commons Attribution 4.0 International (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.
$499 one-time — the same corpus, delivered as a file
- A CSV of the whole corpus, one row per documented hostname — all 61 of them across 57 brands — in the evidence-class shape, with the artefacts we published quoted verbatim.
- The full dated observation history: all 653 observations we hold, every superseded reading kept with its own date on the row it belongs to, oldest first.
- The same table as a paginated PDF, with the dated summary and the limits on the front of it.
- Delivered by email the moment the payment verifies: the link to your order page is emailed to you and both files sit on that page. No account to create, nothing kept on file.
- An invoice or PO route beside the card form, for a procurement team that cannot put a company card through a supplier's form — the export is produced once that invoice is paid. $499 is a single charge either way.
$499 does not buy permission, access or exclusivity, and nobody loses anything because you bought it: the rows stay free under CC BY 4.0 at /lookalike-domain-dataset, including for commercial use. What it buys is the delivered artefact — the whole corpus as one dated file, fixed to the day you pay — and its delivery.
Not included, in plain words
- No monitoring. We do not watch these hostnames for you after delivery, and nothing in the file is re-checked on your behalf.
- No feed and no API. There is no endpoint, no webhook, no push and no alerting — this is one file, bought once.
- No ongoing updates. The export is fixed to the day it was produced. A later re-verification round does not update your copy, and buying this does not entitle you to the next one.
- No registrar, hosting provider, network, name server or IP, for any hostname. That attribution is withheld here exactly as it is on every free page of this site.
- No takedown, no filing, no outcome and no timing of any kind — this is a record of what we observed, not an action taken against anyone.
These are not sentences written for this page. They are the scope limits from our own claims register, reproduced word for word, and they bind every surface of this site — including the one you are reading.
- Every report is a point-in-time audit of publicly observable information, dated to the day the reads were taken. A hostname's state can change at any time after that date.
- No continuous monitoring, on any tier. There is no real-time feed, no API and no alerting, and nothing is re-checked after the report is delivered.
- No takedown execution, on any tier: we never file. We assemble the evidence and draft the request; the buyer sends it.
- We never contact the registrant, and we do not contact a registrar, host or platform on a customer's behalf.
- No outcome and no timeline is promised. Whether anything is suspended is the registrar's, host's or platform's decision alone.
- No legal representation, ever. This is the boundary that did NOT move and must never be softened. We are not a law firm.
- No fund recovery.
- No legal proceedings, and no advice on the merits of a trademark position.
- We make no assertion about any registrant's intent or criminality
Quoted from growth/approved-claims.md §13b, with no word added, removed or softened — it binds the free rows above and every price on this page alike, at $29, at $149, at $249 and at $499: 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.
And the same boundary on the $149 tier, in its own words: This is point-in-time documentation of publicly observable information, not monitoring and not legal advice. We document what our own code read on the day it read it, and we draft the request; on this tier you send it. We do not file on your behalf, we do not contact the registrant, we execute no takedown, and no outcome or timeline is promised — that decision belongs to each registrar, host and platform. We make no assertion about anyone's identity or intent, and a hostname's state can change at any time after the date on the file.
Questions before you pay, or a figure you want to check against the record: scam-detective8@mail.acoco.ai.
1 documented hostname reproducing Jaxxon, with every dated observation
State is the most recent completed observation and the day it was taken; observations is every dated reading on that row, oldest first, including the ones later rounds superseded. Nothing is deleted from a row and nothing is written into one that was not read. Each hostname links to its own dated page.
| Hostname | State at last completed check | Dated observations, oldest first | Registry record |
|---|---|---|---|
| jaxxonshop.com Lookalike storefront — catalogue evidence · first documented 13 August 2026 | does not resolve checked 27 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 resolve2026-10-13 does not resolve2026-10-18 does not resolve2026-10-19 does not resolve2026-10-20 does not resolve2026-10-27 does not resolve last observed serving 15 September 2026 · 1 state change | Registry record read back — 19 October 2026 client hold + client transfer prohibited |
Every state above belongs to the date printed beside it and to nothing else. The most recent completed reading on this page was taken on 27 October 2026; a hostname's state can change on any day, in either direction, and nothing here is a statement about what any of these addresses is serving right now.
We did not observe why it stopped resolving, we make no claim that it was removed, suspended or taken down, and a hostname that stops resolving can be re-pointed at any time — one in this corpus already has.
The 1 registry record we read for Jaxxon
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 is one hostname whose observed state at its own last completed check was “does not resolve”, beside the TLD registry's own record for the same name as we read it, carrying the date we read it. The state column above does not change because of this reading: a status code is an additional dated observation and never a state. 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 |
|---|---|---|---|---|
| jaxxonshop.com read 19 October 2026 · Verisign, the .com registry The reading, in fullReading Verisign, the .com registry’s own RDAP record for jaxxonshop.com on 19 October 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 27 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 |
How these readings were taken, and what they do not say
This page is one brand's slice of a single published dataset, rendered from the same records as the full re-verification dataset — the method as run, all 61 hostnames, the licence and the citation. The same rows are downloadable as CSV, JSON and plain text, under CC BY 4.0 (Creative Commons Attribution 4.0 International (CC BY 4.0)), so every figure here can be re-computed rather than taken on trust.
- (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.
What this page 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.
Jaxxon is the party being copied here, not the party being accused: a brand appears in this index because a hostname we documented was reproducing its branding without being its own website.
Is Jaxxon your brand? Start with the free count — $149 for the documented file
The hostname above was found by the same checks you can run now on a domain you own: lookalike and typosquat candidates generated from it, every candidate resolved, everything that answers fetched live with caching bypassed, and each finding stamped with the date it was read. The free pass returns the count confirmed resolving and two of those rows in full. One complete Brand Impersonation Audit is published in full, so you can read the whole artefact before paying for one.
Jaxxon publishes jaxxon.com as its own domain — read off a page the brand publishes itself on 21 August 2026. That is the address prefilled above, and it is editable. None of the hostnames documented on this page is ever the subject of an audit.
The subject of every audit is a domain the buyer owns. We generate the lookalikes from it — we never run a report against a hostname documented on this page, which would be a report about somebody else's name.
This is the ask we lead with: it is the one file complete enough to hand to a registrar, a platform desk or your own counsel without anybody redoing the reads. The $29 Brand Impersonation Audit is the same method under tighter caps and stays one click away, below.
Same engine, same method, same claims — run deeper. The Brand Impersonation Audit documents up to 15 confirmed hostnames and reports the rest of what resolved as a count; the Documented Evidence Dossier documents up to 30 of them row by row, from a candidate list of up to 320 names rather than 180. Nothing is added to a row and no caveat is softened. If a capped pass over your own domain answers your question, buy the $29 audit instead — this tier is for a file complete enough to hand to someone else.
The subject is a domain you own, never a lookalike you are worried about: we generate names resembling whatever is in that field, so somebody else's address would produce a file about somebody else's name.
Read what the $149 dossier is, in full →
Both are one-time payments — no account and no subscription. The card form opens on this page; the audit runs when the payment clears and is delivered the moment the reads finish.
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.
And the same boundary on the $149 tier, in its own words: This is point-in-time documentation of publicly observable information, not monitoring and not legal advice. We document what our own code read on the day it read it, and we draft the request; on this tier you send it. We do not file on your behalf, we do not contact the registrant, we execute no takedown, and no outcome or timeline is promised — that decision belongs to each registrar, host and platform. We make no assertion about anyone's identity or intent, and a hostname's state can change at any time after the date on the file.
Questions before you pay, or a record on this page you can show is wrong: scam-detective8@mail.acoco.ai.
What we do and do not do — quoted from our own claims register
These are not sentences written for this page. They are the scope limits from our own claims register, reproduced word for word, and they bind every surface of this site — including the one you are reading.
- Every report is a point-in-time audit of publicly observable information, dated to the day the reads were taken. A hostname's state can change at any time after that date.
- No continuous monitoring, on any tier. There is no real-time feed, no API and no alerting, and nothing is re-checked after the report is delivered.
- No takedown execution, on any tier: we never file. We assemble the evidence and draft the request; the buyer sends it.
- We never contact the registrant, and we do not contact a registrar, host or platform on a customer's behalf.
- No outcome and no timeline is promised. Whether anything is suspended is the registrar's, host's or platform's decision alone.
- No legal representation, ever. This is the boundary that did NOT move and must never be softened. We are not a law firm.
- No fund recovery.
- No legal proceedings, and no advice on the merits of a trademark position.
- We make no assertion about any registrant's intent or criminality
Quoted from growth/approved-claims.md §13b, with no word added, removed or softened — and it binds this page as much as any other surface here.
The rest of the record
- Jaxxon on the documented index — the brand's own entry, with the artefacts and the dispute route beside it.
- The full dataset — all 61 hostnames across 57 brands, 653 dated observations, with the method, the licence and the downloads.
- The whole corpus as one dated file — all 61 rows exported together, each with its evidence class, its full observation history and its artefacts quoted verbatim, as a CSV and a paginated PDF. $499 one-time; the rows on this page stay free either way, and no monitoring, feed, API or ongoing update is included.
- The decay study — the same rows counted across the whole window: every state change, its direction, and the gap between the two checks.
- Every documented brand — the index hub, grouped by the brand each hostname reproduces.
- A record on this page you can show is wrong: scam-detective8@mail.acoco.ai. We re-check it and publish what the re-check found alongside the original entry, never in place of it.