domain/kei.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 archivekei.ng was registered in March 2025 with TRUEHOST CLOUD, and is due to expire in March 2027. Its website was online at the last check, served from Namecheap's network. Email for kei.ng is handled by jellyfish.systems.
Registered 2 years ago. The website responds, SPF is published, though DMARC is not and the certificate is trusted.
The last check failed. The operation was aborted due to timeout. What follows is the most recent evidence we hold.
| Type | Value |
|---|---|
| A | 198.187.29.187 AS22612 · Namecheap, Inc. · US |
| MX | 10 mx2-hosting.jellyfish.systems |
| MX | 20 mx3-hosting.jellyfish.systems |
| MX | 5 mx1-hosting.jellyfish.systems |
| NS | dns1.namecheaphosting.com |
| NS | dns2.namecheaphosting.com |
| TXT | v=spf1 +a +mx +ip4:198.187.29.183 include:spf.web-hosting.com ~all |
| SOA | dns1.namecheaphosting.com cpanel.tech.namecheap.com 1741925091 |
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 business details yet. They are read from the site's own pages, such as pricing, about and contact.
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. kei.ng is registered through TRUEHOST CLOUD.
kei.ng was registered on 14 Mar 2025, making it 1 year old.
The registry lists 14 Mar 2027 as the expiry date, 113 days from now. Most domains renew automatically before then.
kei.ng's website is served from Namecheap's network.
Email for kei.ng is handled by jellyfish.systems, according to its MX records.
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.