domain/pesacrash.or.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 archivepesacrash.or.ke was registered in June 2024 with Truehost AI, and is due to expire in June 2027. Its website was online at the last check, served from Cloudflare's network. pesacrash.or.ke doesn't receive email: it publishes no mail servers.
Based on what we observed, it publishes no email authentication records.
| Type | Value |
|---|---|
| A | 104.21.87.43 AS13335 · Cloudflare, Inc. · US |
| A | 172.67.141.80 AS13335 · Cloudflare, Inc. · US |
| AAAA | 2606:4700:3034::ac43:8d50 AS13335 · Cloudflare, Inc. · US |
| AAAA | 2606:4700:3035::6815:572b AS13335 · Cloudflare, Inc. · US |
| NS | phoenix.ns.cloudflare.com |
| NS | yew.ns.cloudflare.com |
| TXT | google-site-verification=2Lci2ZhU0dN-j4Yaa4TQWHVm7AohqjM5yyph-aHbvQ8 |
| SOA | phoenix.ns.cloudflare.com dns.cloudflare.com 2420128033 |
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.
The site blocks automated reading (HTTP 403), so we can't read its business details.
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. pesacrash.or.ke is registered through Truehost AI.
pesacrash.or.ke was registered on 10 Jun 2024, making it 2 years old.
The registry lists 10 Jun 2027 as the expiry date, 201 days from now. Most domains renew automatically before then.
pesacrash.or.ke 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: pesacrash.or.ke publishes no MX records, so it can't receive email.
It was up when we last checked, 3 hours ago (21 Nov 2026), answering with HTTP 403. That shows how it was then, not a guarantee of right now.