domain/hangoverkaakwachadelivery.co.ke
- 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 archivehangoverkaakwachadelivery.co.ke was registered in September 2026 with Truehost AI, and is due to expire in September 2027. Its website was online at the last check, served from OVH's network. Email for hangoverkaakwachadelivery.co.ke is handled by hangoverkaakwachadelivery.co.ke. The website presents it as Hangover Kaakwacha Traditional Kitchen (traditional food delivery).
Based on what we observed, it was registered within the last year.
| Type | Value |
|---|---|
| A | 188.165.52.14 AS16276 · OVH SAS · FR |
| MX | 0 hangoverkaakwachadelivery.co.ke |
| NS | ns1.cloudoon.com |
| NS | ns2.cloudoon.net |
| TXT | v=spf1 +a +mx +ip4:51.91.29.218 ~all |
| DMARC | v=DMARC1; p=none; |
| SOA | ns1.cloudoon.com root.sbg108.truehost.cloud 2026092608 |
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.
We didn't recognise any technology on the homepage.
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. hangoverkaakwachadelivery.co.ke is registered through Truehost AI. The website presents itself as Hangover Kaakwacha Traditional Kitchen; that is the site's own claim, not a verified owner.
hangoverkaakwachadelivery.co.ke was registered on 26 Sept 2026, making it 1 month old.
The registry lists 26 Sept 2027 as the expiry date, 309 days from now. Most domains renew automatically before then.
hangoverkaakwachadelivery.co.ke's website is served from OVH's network.
Email for hangoverkaakwachadelivery.co.ke is handled by hangoverkaakwachadelivery.co.ke, according to its MX records.
It was up when we last checked, 2 hours ago (21 Nov 2026), answering with HTTP 200. That shows how it was then, not a guarantee of right now.