domain/xevron.com.ng
- 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 archivexevron.com.ng was registered in January 2026 with TRUEHOST CLOUD, and is due to expire in January 2027. Its website was online at the last check, served from Cloudflare's network. xevron.com.ng doesn't receive email: it publishes no mail servers.
Based on what we observed, it publishes no email authentication records.
The last check failed. RDAP returned 502 for xevron.com.ng. What follows is the most recent evidence we hold.
| Type | Value |
|---|---|
| A | 104.21.8.244 AS13335 · Cloudflare, Inc. · US |
| A | 172.67.130.198 AS13335 · Cloudflare, Inc. · US |
| AAAA | 2606:4700:3030::ac43:82c6 AS13335 · Cloudflare, Inc. · US |
| AAAA | 2606:4700:3031::6815:8f4 AS13335 · Cloudflare, Inc. · US |
| NS | carioca.ns.cloudflare.com |
| NS | stan.ns.cloudflare.com |
| SOA | carioca.ns.cloudflare.com dns.cloudflare.com 2419085379 |
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. xevron.com.ng is registered through TRUEHOST CLOUD.
xevron.com.ng was registered on 25 Jan 2026, making it 9 months old.
The registry lists 25 Jan 2027 as the expiry date, 65 days from now. Most domains renew automatically before then.
xevron.com.ng 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: xevron.com.ng 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.