domain/finovec.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 archivefinovec.co.ke was registered in August 2025 with Truehost AI, and is due to expire in August 2027. Its website was online at the last check, served from OVH's network. Email for finovec.co.ke is handled by finovec.co.ke. The website presents it as FINOVEC SYSTEMS LTD (enterprise software and technology solutions provider).
Registered 1 year ago. The website responds, SPF and DMARC are published and the certificate is trusted.
| Type | Value |
|---|---|
| A | 54.36.110.109 AS16276 · OVH SAS · FR |
| MX | 10 mail.finovec.co.ke |
| NS | ns1.finovec.co.ke |
| NS | ns2.finovec.co.ke |
| TXT | v=spf1 +a +mx include:_spf.truehostcloud.com ~all |
| DMARC | v=DMARC1; p=quarantine; adkim=s; aspf=s |
| SOA | ns1.finovec.co.ke omaribrahim17.gmail.com 2026102502 |
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. finovec.co.ke is registered through Truehost AI. The website presents itself as FINOVEC SYSTEMS LTD; that is the site's own claim, not a verified owner.
finovec.co.ke was registered on 13 Aug 2025, making it 1 year old.
The registry lists 13 Aug 2027 as the expiry date, 265 days from now. Most domains renew automatically before then.
finovec.co.ke's website is served from OVH's network.
Email for finovec.co.ke is handled by finovec.co.ke, according to its MX records.
It was up when we last checked, 23 hours ago (20 Nov 2026), answering with HTTP 200. That shows how it was then, not a guarantee of right now.