domain/xtoken.network
- Registration data
RDAP - DNS records
A, AAAA, MX, NS, TXT, CAA, SOA - Email policy
_dmarc - TLS certificate
port 443 - Website snapshot
HTTP - Comparing with history
whois.is archive
RDAPA, AAAA, MX, NS, TXT, CAA, SOA_dmarcport 443HTTPwhois.is archivextoken.network was registered in October 2026 with NameCheap, and is due to expire in October 2027. Its website was online at the last check, served from Amazon.com's network. Email for xtoken.network is handled by jellyfish.systems. The website presents it as XTOKEN (multi-chain wallet).
Based on what we observed, it was registered within the last year.
| Type | Value |
|---|---|
| A | 75.2.60.5 AS16509 · Amazon.com, Inc. · US |
| MX | 10 mx2-hosting.jellyfish.systems |
| MX | 20 mx3-hosting.jellyfish.systems |
| MX | 5 mx1-hosting.jellyfish.systems |
| NS | gwen.ns.cloudflare.com |
| NS | yoxall.ns.cloudflare.com |
| TXT | v=spf1 +a +mx +ip4:162.213.253.105 +ip4:162.213.253.112 include:spf.web-hosting.com ~all |
| DMARC | v=DMARC1; p=none; |
| SOA | gwen.ns.cloudflare.com dns.cloudflare.com 2419013558 |
A network is whoever runs the servers behind the address. With a CDN such as Cloudflare in front, that is the CDN, not the company hosting the site behind it.
Read from the homepage's code and server headers. Sites can hide what they use, so this list may be incomplete.
No public prices on the pages we read.
Every value is quoted from the page linked beside it. Read from 1 page.
Most registries now keep the registrant's details private, and whois.is doesn't show them. xtoken.network is registered through NameCheap. The website presents itself as XTOKEN; that is the site's own claim, not a verified owner.
xtoken.network was registered on 25 Oct 2026, making it 27 days old.
The registry lists 25 Oct 2027 as the expiry date, 338 days from now. Most domains renew automatically before then.
xtoken.network's website is served from Amazon.com's network.
Email for xtoken.network is handled by jellyfish.systems, according to its MX records.
It was up when we last checked, 3 hours ago (21 Nov 2026), answering with HTTP 200. That shows how it was then, not a guarantee of right now.