domain/aiwaanzilishi.co.tz
- 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 archiveaiwaanzilishi.co.tz was registered in August 2026, and is due to expire in August 2027. Its website was online at the last check, served from OVH's network. Email for aiwaanzilishi.co.tz is handled by aiwaanzilishi.co.tz. The website names My Blog as the business behind it.
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 aiwaanzilishi.co.tz |
| 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 2026102901 |
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.
None stated on the pages we read.
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. The website presents itself as My Blog; that is the site's own claim, not a verified owner.
aiwaanzilishi.co.tz was registered on 27 Aug 2026, making it 2 months old.
The registry lists 26 Aug 2027 as the expiry date, 279 days from now. Most domains renew automatically before then.
aiwaanzilishi.co.tz's website is served from OVH's network.
Email for aiwaanzilishi.co.tz is handled by aiwaanzilishi.co.tz, 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.