domain/sharespace.africa
- 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 archivesharespace.africa was registered in September 2026 with Afriregister, and is due to expire in September 2027. Its website was online at the last check, served from OVH's network. Email for sharespace.africa is handled by sharespace.africa. The website presents it as ShareSpace (rental marketplace).
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 sharespace.africa |
| NS | ns1.cloudoon.com |
| NS | ns2.cloudoon.net |
| TXT | v=spf1 +a +mx include:_spf.truehostcloud.com ~all |
| DMARC | v=DMARC1;p=quarantine;sp=quarantine;adkim=r;aspf=s;pct=100;fo=0;rf=afrf;ri=86400;rua=mailto:[email protected];ruf=mailto:[email protected] |
| SOA | ns1.cloudoon.com root.sbg108.truehost.cloud 2026110601 |
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.
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. sharespace.africa is registered through Afriregister. The website presents itself as ShareSpace; that is the site's own claim, not a verified owner.
sharespace.africa was registered on 4 Sept 2026, making it 2 months old.
The registry lists 4 Sept 2027 as the expiry date, 287 days from now. Most domains renew automatically before then.
sharespace.africa's website is served from OVH's network.
Email for sharespace.africa is handled by sharespace.africa, according to its MX records.
It was up when we last checked, 5 hours ago (21 Nov 2026), answering with HTTP 200. That shows how it was then, not a guarantee of right now.