domain/kiefonline.com
- 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 archivekiefonline.com was registered in January 2026 with OwnRegistrar, and is due to expire in January 2027. Its website was online at the last check, served from Unified Layer's network. Email for kiefonline.com is handled by kiefonline.com. The website presents it as Kief Online Shop (medical cannabis dispensary).
Registered 1 year ago. The website responds, SPF is published, though DMARC is not and the certificate is trusted.
| Type | Value |
|---|---|
| A | 199.79.62.14 AS46606 · Unified Layer · US |
| MX | 0 mail.kiefonline.com |
| NS | ns1.md-36.webhostbox.net |
| NS | ns2.md-36.webhostbox.net |
| TXT | v=spf1 ip4:199.79.62.14 a mx include:websitewelcome.com ~all |
| SOA | ns1.md-36.webhostbox.net root.md-36.webhostbox.net 2026112001 |
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 5 pages.
Most registries now keep the registrant's details private, and whois.is doesn't show them. kiefonline.com is registered through OwnRegistrar. The website presents itself as Kief Online Shop; that is the site's own claim, not a verified owner.
kiefonline.com was registered on 19 Jan 2026, making it 10 months old.
The registry lists 19 Jan 2027 as the expiry date, 59 days from now. Most domains renew automatically before then.
kiefonline.com's website is served from Unified Layer's network.
Email for kiefonline.com is handled by kiefonline.com, 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.