domain/wehaafrica.org
- 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 archivewehaafrica.org was registered in June 2026 with Registrar.eu, and is due to expire in June 2027. Its website was online at the last check, served from Truehost Cloud's network. Email for wehaafrica.org is handled by wehaafrica.org. The website presents it as Water & Environmental Hygiene Awareness in Africa (WEHA Africa) (water, environmental hygiene, and sustainability organization).
Based on what we observed, it was registered within the last year and it publishes no email authentication records.
| Type | Value |
|---|---|
| A | 102.212.246.123 AS329278 · Truehost Cloud Limited · KE |
| MX | 0 wehaafrica.org |
| NS | ns1.cloudoon.com |
| NS | ns2.cloudoon.net |
| NS | ns3.cloudoon.org |
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 1 page.
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. wehaafrica.org is registered through Registrar.eu. The website presents itself as Water & Environmental Hygiene Awareness in Africa (WEHA Africa); that is the site's own claim, not a verified owner.
wehaafrica.org was registered on 19 Jun 2026, making it 5 months old.
The registry lists 19 Jun 2027 as the expiry date, 210 days from now. Most domains renew automatically before then.
wehaafrica.org's website is served from Truehost Cloud's network.
Email for wehaafrica.org is handled by wehaafrica.org, 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.