domain/joint-relivex.us
- 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 archivejoint-relivex.us was registered in October 2026 with NameSilo, and is due to expire in October 2027. Its website was online at the last check, served from Cloudflare's network. joint-relivex.us doesn't receive email: it publishes no mail servers. The website presents it as JointReliveX (dietary supplement).
Based on what we observed, it was registered within the last year and it publishes no email authentication records.
| Type | Value |
|---|---|
| A | 188.114.96.3 AS13335 · Cloudflare, Inc. · US |
| A | 188.114.97.3 AS13335 · Cloudflare, Inc. · US |
| AAAA | 2a06:98c1:3120::3 AS13335 · Cloudflare, Inc. · US |
| AAAA | 2a06:98c1:3121::3 AS13335 · Cloudflare, Inc. · US |
| NS | ligia.ns.cloudflare.com |
| NS | tim.ns.cloudflare.com |
| SOA | ligia.ns.cloudflare.com dns.cloudflare.com 2419029670 |
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.
First observation recorded. Every change from here on is preserved and shown here.
Most registries now keep the registrant's details private, and whois.is doesn't show them. joint-relivex.us is registered through NameSilo. The website presents itself as JointReliveX; that is the site's own claim, not a verified owner.
joint-relivex.us was registered on 8 Oct 2026, making it 1 month old.
The registry lists 8 Oct 2027 as the expiry date, 321 days from now. Most domains renew automatically before then.
joint-relivex.us is served through Cloudflare, which sits in front of the site. The company hosting the site behind it isn't visible from outside.
No one: joint-relivex.us publishes no MX records, so it can't receive email.
It was up when we last checked, 6 hours ago (21 Nov 2026), answering with HTTP 200. That shows how it was then, not a guarantee of right now.
Every value is quoted from the page linked beside it. Read from 1 page.